The Context
A client needed a mobile app for their field operations team. The requirements were clear: offline capability, real-time sync, and cross-platform deployment (iOS and Android). The timeline: four weeks.
Week 1: Foundation
- State management setup (we used Riverpod)
- Offline-first data layer with local database
- API client with retry logic and queue
- Authentication flow and secure storage
Week 2-3: Core Features
With the foundation solid, features came together quickly. Every feature request went through a simple filter: "Will the app be unusable without this on day one?" If not, it went to the backlog.
Week 4: Polish and Deploy
The final week was about hardening. Edge cases, error handling, loading states, and the dozen small things that separate a prototype from production software.
What Actually Worked
- Offline-first design: Don't bolt it on later
- Feature discipline: Say no to almost everything
- Early device testing: Simulators lie
- Error handling from day one: Things will fail
The Result
The app shipped on time. More importantly, it worked in the field — with poor connectivity, on older devices, in the hands of users who didn't read the manual.