offline-first
Design a useful local workflow that tolerates missing connectivity.
Use this when Users need to keep reading or editing while disconnected.
without the term
“Our app is useless on the subway. Can it keep working without internet, save what people do, and sync when they're back online without losing anything?”
with the term · How do you ask a model for offline-first?
Make this draft workflow work offline. Test restart before sync, reconnection, conflicting edits, and a rejected server write without losing user input.
What is offline-first?
The app reads and writes local data first and syncs with the server when it can, so it stays usable offline. Pending changes, conflicts, and server rejections each need a defined outcome.
Why does offline-first matter when vibe coding?
Caching the last response alone does not preserve offline edits.
How do you do offline-first?
Persist local intent, show pending state, and reconcile with the authoritative service when available.
What goes wrong with offline-first?
Calling local data universally authoritative when the server must still enforce access or business rules.