The problem
A driver app is a working tool. The driver is in traffic, the screen is in one hand, and anything slow or confusing costs them money on the trip they are currently on.
What we built
Driver-side features
New features designed and shipped with cross-functional product teams, in a codebase used by drivers across North Africa.
Refactors that paid off
Refactoring work that improved performance and maintainability in the parts of the app that changed most often.
Documentation the team could follow
Technical documentation for the iOS codebase, including the model namespacing standard.
Hiring support
Reviewed and scored take-home tests for iOS candidates.
Screens
How we worked
Our founder worked as a senior iOS developer on the driver app, inside product teams rather than on an isolated feature.
Results
New driver features shipped with cross-functional product teams
Performance and maintainability improved in the most-changed parts of the codebase
Technical documentation written, including the model namespacing standard
What's next
The habits from field-tool work, offline tolerance and one-handed screens, go into every operations app we build.
