Work / Hilife · 2022
Beat Management
The field-side counterpart to ezsales: officers add outlets to their beat, upload route files and manage coverage from the road.
The problem
Territories drift. Shops open, close and move, and the person who finds out first is the officer standing outside a shuttered storefront — not the planner in the office.
What I built
Add-to-beat from the field, so a newly discovered outlet is captured while the officer is in front of it rather than remembered badly at the end of the day. Route file upload with per-file status, so a partially failed batch shows exactly which file needs attention instead of failing silently as a whole.
Bulk multi-select with clear affordances, because the realistic use is twenty outlets at once, not one. Every action is queued and offline-tolerant — the app assumes signal is a bonus.
What it came to
- Offline-first
- Queued actions, sync when signal returns
- Bulk edit
- Multi-select across outlets and routes
- Per-file status
- Partial batch failures stay visible
- Flutter
- Django
- MySQL
- Offline sync
Screens
Open to senior engineering roles
Tell me what you are building.
Full-time roles, contract work, or a system that needs someone to own it. I read everything and reply within a few hours.