Most to-do apps know two states: done and not done. F4Goals, the task manager I build and run, treats partial progress as a first-class value: you slide a task to say how far along it is, and subtasks nest as deep as the work does. It also had to work on a train with patchy signal, so sync could not be an afterthought.
It ships to the web and to Google Play from one Expo and React Native codebase. Here is the design that keeps an offline edit from ever being lost.
1. Local first
All state lives on the device (Zustand with persistence), so every interaction is instant and nothing waits on the network. The server is a replica you sync with, not the source of truth for what the screen shows.
2. A durable outbox
Every write is queued, persisted, and flushed to Supabase when the device is online. The rule that matters most: a rejected write is never deleted. It moves to a persisted dead-letter list and is retried when the connection returns.…