Series · 6 parts

Offline-First KMP

When your mobile app must work without internet as a standard, not an edge case, the sync layer is just the first decision. What comes after — preserving user intent offline, trusting a "success" your server never actually confirmed, resolving conflicts as a human decision — is where offline-first actually gets hard. Field notes from a production KMP winery app.

Cover Image for Offline-First KMP
  1. 1Choosing an offline-first sync layer for KMP
  2. 2Two writes for every tap
  3. 3Minting IDs Before the Server
  4. 4The Write You Never Clean Up
  5. 5HTTP 200 Is Not Success
  6. 6Your Schema Is Not Your Payload