Offline-first Architecture - How to survive without the internet?

on YouTube ↗43m

" summary

An Android ticketing app (MT) uses an offline‑first design: local database as source of truth, lazy writes via service workers, and a backend-for-frontend called offers cache that prepackages every possible offer; worst‑case caching drops from ~20 minutes to under one minute. Sales are persisted to an order import service that publishes to Kafka, reducing each sale to one app→backend call and enabling retries. Libraries carry validation logic offline; the system works but adds substantial complexity, storage (multiple GBs) and operational burden.

AI-written summary · about

" chapters (7)

1. 0:00Offline-first architecture intro
2. 2:19Offline-first in public transport
3. 7:39Offline-first principles
4. 14:42Implementing offline-first systems
5. 24:40Caching and sync challenges
6. 39:28Solutions and architecture overview
7. 40:52Key takeaways and adoption

" related talks

• 45mOffline First (Web) AppsAlex Feyerke · ColdFront Conference 2015
• 32mLook, Mum, No Internet - Creating great experiences with offline-first appsAndreas Wenger · droidcon London 2022
• 35mHow Offline-First Architecture Could Save Your AppsCharles Laziosi, Vincent Journel · DevOpsDays Geneva 2022
• 41mOffline FirstAlex Feyerke · Web Directions Code 2014
• 39mSay Hello to Offline FirstOla Gasidlo · GOTO Berlin 2015
• 36mTesting Offline First Mobile ApplicationsJoe Keeley · TestCon Europe 2019
• 23mDesigning for Disconnection- The Mental Model of Offline AppsMatt McKenna · droidcon New York 2023
• 40mOffline Mode, Online ImpactKamal Shree, Akansha Jain · Fluttercon India 2025