Code 2018
Optimistic Offline Experiences
About this presentation
Many things cause connection trouble. Bad reception, flaky Wi-Fi, servers being down, computers resuming from sleep. The standard way to handle this is an App Shell with a "Cannot connect" message. This is a terrible offline experience. We can do better. How can you balance your UI updates between optimistic and honest? Between spamming users with "Now connected!" notifications and not telling them at all? Does it matter if a Like silently fails? You'll learn answers to these, and other ways to make a more fault-tolerant, more fun frontend.