Web as an application platform is amazing: evergreen browsers or some form of webviews exist almost on every device with UI, we have native APIs to access the hardware, we use versatile language with the excellent tooling, we are the huge (the largest ever) developer community after all! But the web historically tightly coupled with the connection state... In my session, we confirm: the modern web APIs and some best practices allow us to build offline-first web apps: always available, caring about data consumption, preserving and sync, providing UX which is comparable (if not better) to the native apps, regardless of the connection. Plus, the current state of the tooling makes it possible to add these features in a fast and reliable way. Let's explore the offline web in a very practical manner - by building the offline-first app!

This session will be useful for web front-end developers who have heard about progressive web apps (who haven't :), maybe even tired of PWA-hype, and thus want to understand some of UX benefits on practice. As this is not another "What is PWA" session, I focus exclusively on the modern APIs making offline-first approach possible, in a form of task+solution sections - to maximize the usefulness.

Backend developers and mobile developers will get a nice overview of what web can do today (they will be impressed).

1. The web as an application platform - 10 min
1.1 Cool parts: browsers, hardware APIs, language, community, etc
1.2 Issues: browsers interop, connection status dependency
1.3 Failed tries to solve the offline issue

2. The new imperative way to cache - 10 min
2.1 Setting the requirements for offline usecases
2.2 Briefly about how Service Worker API helps with offline
2.3 Introducing Workbox as a helper to solve complex scenarios

3. Offlinization in practice - 20 min
3.1 Making available the app itself - app shell
3.2 Caching application runtime data
3.3 Preserving and syncing offline actions and data
3.4 Managing larger resources downloads and uploads

4. Summary - 5 min
4.1 The state of offline web
4.2 More APIs to reduce the gap between native and web