Designing for intermittent connectivity: offline-first choices at Maply

Tech · 6 min read

Maply, a mapping startup serving logistics and field teams in emerging markets, struggled with inconsistent cellular connections that broke editing workflows and caused lost work. The team committed to an offline-first architecture and a UX that made sync behavior transparent and recoverable. Key product decisions included local-first editing, a conflict resolution affordance, and selective layer syncing to conserve storage.

Engineers implemented a lightweight sync engine that prioritized geometry and routing layers for immediate operational needs while deferring large imagery tiles. Designers introduced a visual sync status bar and a ‘last synced’ timestamp on critical assets. When conflicts occurred, Maply presented a contextual merge UI that highlighted changed fields and allowed users to accept server or local edits, with an option to contact teammates directly from the conflict screen.

Field testing in rural sites showed a 52% drop in lost edits and a 34% reduction in support requests related to sync. Users reported higher confidence in working offline knowing that the app would queue changes and notify them when conflicts needed attention. The selective sync strategy also reduced on-device storage use by 40%, enabling smaller devices to operate reliably.

Maply’s approach underscores that offline-first is both a technical and UX challenge: prioritize the most critical data, surface sync state clearly, and design conflict resolution flows that fit the users’ collaboration patterns. For startups targeting low-connectivity contexts, these choices can be a competitive differentiator.