What you get
- iOS and Android from one Flutter codebase, so every feature and fix reaches both at once
- Offline-first data capture for teams that work without signal, syncing on its own when a connection returns
- A back end and an admin dashboard for the office, with an API on Cloudflare Workers and data in Supabase
- App store release, documentation and a clean repository you own
Who it's for
Field crews, operations staff and customers who need an app that does one job reliably: capture, check, approve or track.
How it works
- Discovery. Which screens, who uses them, and what has to keep working without signal.
- Build. Weekly written updates, with working screens to try as they take shape.
- Ship. App store submission, separate staging and production back ends, and monitoring in place.
- Handover. Documentation and the code in a repository you own, with support available after launch.
Technology
FlutteriOS & AndroidSupabaseCloudflare WorkersTypeScript
Related work and writing
An offline-first mobile app for field operations
Data capture that keeps working with no signal. 60% faster data entry, near-zero sync errors.
How do you build an offline-first app that never loses a record?
Why the phone, not the server, is the source of truth until every record is confirmed.
Common questions
Do you build for both iPhone and Android?
Yes. Apps are built in Flutter, which produces iOS and Android apps from one codebase, so features and fixes reach both at the same time.
Can the app work without mobile signal?
Yes. An offline-first app saves everything on the phone and syncs in the background when a connection returns, so nothing is lost. How offline sync works.
Who owns the app once it's built?
You do. Every project ends with a clean handover: documented code in a repository you own.
Start a project
Describe the problem in a few lines and I'll reply with questions, not a quote. I'm based in Auckland and work remote-first, so it doesn't matter where in New Zealand you are.