<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bazaar Ledger</title>
    <description>The latest articles on DEV Community by Bazaar Ledger (@bazaarledger).</description>
    <link>https://dev.to/bazaarledger</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4256915%2Fbcbdd079-9b11-48b1-868f-000feb752ebf.png</url>
      <title>DEV Community: Bazaar Ledger</title>
      <link>https://dev.to/bazaarledger</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bazaarledger"/>
    <language>en</language>
    <item>
      <title>Building an offline-first Flutter ledger for shops: what "no internet" really costs</title>
      <dc:creator>Bazaar Ledger</dc:creator>
      <pubDate>Sat, 21 Nov 2026 07:44:17 +0000</pubDate>
      <link>https://dev.to/bazaarledger/building-an-offline-first-flutter-ledger-for-shops-what-no-internet-really-costs-3epo</link>
      <guid>https://dev.to/bazaarledger/building-an-offline-first-flutter-ledger-for-shops-what-no-internet-really-costs-3epo</guid>
      <description>&lt;p&gt;I built Bazaar Ledger, a shop bookkeeping app for Android with a Windows companion, and I want to share what offline-first did to the design.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The rule.&lt;/strong&gt; Every bill, payment and stock movement is written to the phone first. The network is optional, so there is no loading spinner between a customer and a receipt.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The ledger underneath.&lt;/strong&gt; Billing screens are friendly, but every sale, payment, purchase and expense posts to double-entry accounts. That is why the 100+ reports agree with each other: they are different views of one ledger.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A server that cannot read.&lt;/strong&gt; If a shop turns on the optional cloud, the books are sealed on the phone before upload, with keys the server never receives. The cost is real: the server cannot search, repair or analyse a shop's data, so every feature that needs reading has to be opt-in and done on the device.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Posted bills are never edited in place.&lt;/strong&gt; A correction is a cancelled bill plus a new corrected one, both kept, behind a PIN. It is more work to build and far easier to audit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The AI assistant is optional and narrow.&lt;/strong&gt; Simple commands are parsed on the phone. When the phone is unsure, the assistant (Anthropic's Claude, through our server) gets only what that one request needs, never the whole book. You review and save by default.&lt;/p&gt;

&lt;p&gt;The app is free for one whole shop. I would like feedback from other Flutter developers on two things: testing sync conflicts when two counters sell the last unit offline, and how you handle thousands of ledger rows on low-end phones.&lt;/p&gt;

&lt;p&gt;Play: &lt;a href="https://play.google.com/store/apps/details?id=pk.bazaarledger" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=pk.bazaarledger&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>flutter</category>
      <category>offline</category>
      <category>mobile</category>
    </item>
  </channel>
</rss>
