<?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: Majician13</title>
    <description>The latest articles on DEV Community by Majician13 (@majician13).</description>
    <link>https://dev.to/majician13</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%2F759272%2F78734a97-bbd6-494e-97b2-02463751b5b1.jpeg</url>
      <title>DEV Community: Majician13</title>
      <link>https://dev.to/majician13</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/majician13"/>
    <language>en</language>
    <item>
      <title>Footings: the offline-first Flutter starter kit I extracted from my own app</title>
      <dc:creator>Majician13</dc:creator>
      <pubDate>Tue, 17 Nov 2026 20:38:48 +0000</pubDate>
      <link>https://dev.to/majician13/footings-the-offline-first-flutter-starter-kit-i-extracted-from-my-own-app-5611</link>
      <guid>https://dev.to/majician13/footings-the-offline-first-flutter-starter-kit-i-extracted-from-my-own-app-5611</guid>
      <description>&lt;p&gt;Every offline app I start rebuilds the same plumbing: a local database, a way to seed it with starter content, search, favorites, and eventually backup. I got tired of rewriting it, so I extracted the working stack from my own app — a magic index app I've been building all year — into a starter kit called Footings.&lt;/p&gt;

&lt;h2&gt;
  
  
  The core idea: two databases, not one
&lt;/h2&gt;

&lt;p&gt;Most offline tutorials use a single database. Footings uses two:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;bundled read-only seed DB&lt;/strong&gt; that ships with the app. This is your starter content.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;writable user DB&lt;/strong&gt; for everything the user creates, plus favorites.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The split matters when you ship an update. New seed content replaces the bundled DB; the user's data is never touched. The user DB migrates itself — v1 to v2 adds an images table and an &lt;code&gt;ocr_text&lt;/code&gt; column — so existing users keep everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in the free lite version
&lt;/h2&gt;

&lt;p&gt;The lite version is MIT-licensed and on GitHub:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Word-start search, category browsing, favorites, full CRUD&lt;/li&gt;
&lt;li&gt;The two-database setup, with a seed DB you replace with your own content&lt;/li&gt;
&lt;li&gt;A clean &lt;code&gt;flutter analyze&lt;/code&gt; and passing tests&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What the full version adds
&lt;/h2&gt;

&lt;p&gt;Three features, and each one taught me something:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Google Drive backup/restore.&lt;/strong&gt; The app's data lives in Drive's app-data folder, with silent auto-backup and change detection, plus export/import through the share sheet. Buyers plug in their own OAuth client ID — nothing of mine ships in the kit. One gotcha: &lt;code&gt;google_sign_in&lt;/code&gt; is pinned at ^6.3.0, because the v7 API changes the auth flow and the &lt;code&gt;extension_google_sign_in_as_googleapis_auth&lt;/code&gt; bridge expects the v6 shape.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On-device OCR scan-to-create.&lt;/strong&gt; Take a photo of a page, and ML Kit reads the text. The text is kept for reference and search — but nothing is ever auto-filled. I learned that the hard way: my first version auto-filled the title from OCR and put a "$20" price sticker in the Title field. Manual entry after the photo, every time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Per-item photos&lt;/strong&gt; from camera or gallery, backed up along with the rest.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pricing
&lt;/h2&gt;

&lt;p&gt;The lite version is free on GitHub. The full version is $49 at launch (going to $99), one-time, unlimited personal and commercial projects.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Free lite: &lt;a href="https://github.com/Majician13/flutter-offline-starter" rel="noopener noreferrer"&gt;https://github.com/Majician13/flutter-offline-starter&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Full version: &lt;a href="https://4308559011616.gumroad.com/l/footings" rel="noopener noreferrer"&gt;https://4308559011616.gumroad.com/l/footings&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you're building an offline-first Flutter app, I'd love to hear what your data layer looks like — and what you'd want a starter kit to do that this one doesn't.&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>dart</category>
      <category>sqlite</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
