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.
The core idea: two databases, not one
Most offline tutorials use a single database. Footings uses two:
A bundled read-only seed DB that ships with the app. This is your starter content.
A writable user DB for everything the user creates, plus favorites.
The split matters when you ship an update. New seed content replaces the bundled DB; the user's data is never touched.β¦