A mobile app is the right build when the work happens away from a desk: a customer requesting something, a driver or operator accepting it, a status that has to be current. The app is one part of that system. The accounts, the rules, and the record of what happened stay in the software behind it.
What we build
- Customer apps The screen a customer uses to request, pay, and follow a job.
- Operator apps The screen staff use to accept work, update status, and finish it.
- Android and iOS Both stores, from one Flutter build, so the two apps do not drift apart.
- Live status Push notifications and updates when the operation cannot wait for someone to refresh a page.
- The system behind the app Accounts, APIs, and the business rules. That is custom software, scoped with the app when they are one project.
How a build is decided
The first conversation is who holds the phone, and what has to be true before the app is allowed into a store. You receive a written scope before build starts. There is no package on this page, because a customer app and an operator app are not the same piece of work.
You review working software while it is being built. Release covers both stores, and the line back to Capital Design stays open after the app is live.