When the browser is the wrong tool
Odoo's web interface is capable and it is the right answer for most users most of the time. It stops being the right answer when the person using it is standing up, moving around, wearing gloves, holding something in the other hand, or working somewhere the signal does not reach.
At that point what is needed is not a smaller version of the desktop screen. It is a different application, built around one job, that happens to talk to the same Odoo.
What we build
- Field service apps that work fully offline and reconcile when they reconnect
- Warehouse and inventory apps built around scanning rather than typing
- Delivery and proof-of-collection apps with signature and photo capture
- Shop-floor apps for recording production steps and consumption
- Customer-facing apps where a portal login is not enough
How we build it
React Native, so one codebase covers Android and iOS and both fleets stay in step. Real native components rather than a web page in a wrapper, which is what makes the difference on modest hardware and poor connections.
The app is designed around the flow, not around the Odoo screens. That is usually the whole point of building one.
On the Odoo side we build a proper API layer rather than bolting onto whatever endpoint happens to exist, so the app survives your next upgrade.
Where it usually starts
Most mobile projects begin as a complaint: the tablets are too slow, the staff write things on paper and type them in later, the system is unusable at the far end of the warehouse. Those are all the same problem, and they are all worth fixing properly.
Our field service app began exactly that way and became a solution we now deploy repeatedly.
Get in touch
Tell us what isn't working
Send a short description of where your processes hurt. You'll get a reply from the person who would do the work, not a sales team.
