> You have to re-architect things so that the UI is optimistic, commits to a local database and that local database is synced up to the server when you come onl

> You have to re-architect things so that the UI is optimistic, commits to a local database and that local database is synced up to the server when you come online. I'm not sure you got the point. The design guideline that "Offline Is Just Online with Extreme Latency" already reflects very specific architectural requirements, and state transitions in the application life cycle. We're talking event-driven architectures, batching events, flushing events in offline/online transitions or even when minimizing windows, pulling events when going online, etc etc etc. I'd go even further and claim that this whole "pessimistic vs optimistic UI" thing is just "adequate vs broken UI design",regardless whether the app is even expected to go online.