01 / Field service / Offline-first systems
FieldyUseful when the connection isn’t.
A field service management and CRM product designed around real work in the field. I worked on offline caching and reconnection sync, live location tracking, and production diagnostics so the app could stay useful outside ideal network conditions.
Flutter application
Flutter · BLoC · Dio · Socket.io · Firebase
01 / Context
The setting.
Field service management and CRM software used by technicians and field teams. Connectivity isn’t always dependable, but workflows still need to continue.
02 / My contribution
Where I worked.
- Built offline-first local caching with synchronization back to backend microservices after connectivity returns.
- Added Firebase Crashlytics with custom diagnostic logging to make production edge cases observable.
- Implemented real-time location tracking over Socket.io.
- Worked on automated dispatching.
- 01Offline work
- 02Local cache
- 03Reconnect
- 04Backend sync
03 / Engineering focus
The interesting part.
The transition back online is part of the experience. This work involved synchronizing data after disconnection and diagnosing failures that are difficult to reproduce locally. Custom logging helped make those production edge cases visible.
04 / Impact
What changed.
Improvement in field operational efficiency following dispatch automation
Reduction in data entry errors following dispatch automation
Of edge-case runtime crashes captured by custom Crashlytics logging
Resume-reported results. These describe product outcomes, not independently audited measurements.
05 / Reflection
What stayed with me.
A good app needs a plan for imperfect conditions, not just a polished connected-state demo.
Have a similar problem to work through? Get in touch ↗