Offline First: Faster, More Robust and More Fun (Web) Apps
Just assume for a minute that the technical side of building offline-capable (web) apps was really simple. Because it’s getting easier every day, and it’s obviously desirable: having a robust, reliable app instead of one that turns into a wonky disappointment when it’s disconnected for a moment. But what does building apps offline first mean in terms of interfaces and experiences, in terms of your application’s structure? What new things can you do? What problems can you solve? What problems does it cause? Is it too much trouble, or is it the future? A talk about patterns for offline UX, persistent local data, confident wording, pre-empting user needs, conflict resolution and ordering things in lists.
