Number Dekho.
On-demand products are two apps: the one people praise and the one that works.
- Client
- Number Dekho
- Sector
- On-demand service
- Scope
- App + web
- Stack
- Next.js, React Native, Node.js
An on-demand service build on app and web, covering discovery, booking, fulfilment and the operations behind it.
What made it hard.
The first version usually contains three products. Deciding which one ships is most of the value.
Content ownership
If routine changes need a developer, the site stops being updated within a quarter.
Performance
Consumer patience is measured in hundreds of milliseconds on a mid-range phone.
Handover
Whoever maintains it next inherits these decisions and should be able to live with them.
What we shipped.
An on-demand service build on app and web, covering discovery, booking, fulfilment and the operations behind it.
How it holds up.
Performance and accessibility budgets are set at the start and enforced in CI, because both are cheap to hold and expensive to retrofit.
The systemMatching runs as its own service, and the provider-facing app gets the same engineering attention as the customer app.
Theirs, from day one.
Repositories, cloud accounts and documentation sat with the client throughout. Senior engineers wrote the production code rather than specifying it.
Ask for the full metrics on a call →More on-demand service work.
All 42 case studies →Building something like Number Dekho?
Tell us what you are building. A senior engineer replies within one business day. NDA on request.