Designing offline-first for classrooms that lose connectivity mid-lesson

The engineering half of offline-first is well understood: local-first data models, conflict resolution, background sync. The harder half is designing an interface that never misrepresents what state the app is actually in.

Our rule became this: any action a teacher takes must show its true sync status within 200 milliseconds, even if that status is saved locally, not yet synced. Hiding that distinction behind a generic loading spinner is what erodes trust in a classroom where connectivity can vanish for an hour.

We also learned to design for the moment connectivity returns, not just the moment it is absent. A sudden flood of forty queued actions syncing at once needs its own calm, legible interface, otherwise the good moment feels as chaotic as the outage did.