Local-first is a product choice, not just an architecture slogan. When the core loop of an app requires a round trip to a server, every commute, spotty campus Wi‑Fi, or airplane mode becomes a failure mode — and users notice.
For LETReady and CLEReady on Android, question banks and progress should work offline after the first content import. Sessions, bookmarks, and results live on the device so a study streak does not depend on API uptime. The CLEReady web client is intentionally online-only — bank in memory, prefs in localStorage — while the Android build keeps the offline-first path.
For Spacio, the opposite problem is trust: a storage cleaner that uploads personal photos to “process in the cloud” is asking for Data safety friction and user skepticism. Spacio indexes and analyzes media on device; nothing is deleted without confirmation, and personal media is not silently sent to Techsider servers for cleaning.
That constraint simplifies privacy disclosures. Play Data safety answers can stay short and truthful because the default path never becomes a silent cloud pipeline. Optional network features — sync, leaderboards, ads consent — stay clearly optional and documented.
Local-first is not anti-cloud. It is a sequencing rule: ship a useful offline core first, then add network value users can opt into without breaking the product when they are offline.