June 30, 2026 · 5 min read
Local-first mobile apps with Flutter
Why we build apps like Cornell Notes and Accentless to keep your data on your device, and how Flutter lets us ship them everywhere.
Two of our mobile products, Cornell Notes and Accentless, share a design principle we care about: they are local-first. Your data lives on your device, works without an account, and does not depend on our servers to function. Here is why we build that way, and how Flutter makes it practical.
What “local-first” means
A local-first app treats the copy of your data on your own device as the source of truth. The app is fully usable offline. There is no login wall between you and your own notes, and nothing you write is sitting on a server by default.
Cornell Notes is a structured note-taking app built around the Cornell method. Everything is stored locally in an on-device SQLite database, with autosave as you type. Because the data is yours and local, we added JSON export, import and backup through the system share sheet, so you can move your notes between devices or keep your own copies, without us being in the middle.
Accentless is a pronunciation-practice app. You record yourself saying a word and compare your waveform against a reference, side by side, with the IPA phonetics shown. Those recordings are personal, so they stay on your device. That is a privacy decision as much as a technical one.
Why Flutter
Both apps are built with Flutter, Google’s cross-platform toolkit. One Dart codebase compiles to Android and iOS (and desktop and web when we want it). For a small studio, that is the difference between shipping on one platform and shipping on all of them without maintaining separate codebases.
Flutter also does not fight the local-first approach. Mature packages for on-device storage, audio recording and playback, and file access mean we can build a genuinely offline-capable app without gluing together a fragile stack.
It still has to pay for itself
Local-first does not mean no business model. Accentless runs in-app purchases through RevenueCat, working end-to-end on Google Play. You can respect a user’s data and still build a sustainable product; the two are not in tension.
If you are thinking about a mobile app and want it done properly, cross-platform, privacy-respecting, and actually shipped to the stores, let’s talk.