Services / Mobile
An app people open twice.
Android and iOS apps, from prototype to store. With the interface designed before any code, and analytics in place to learn what people actually use.
What they are usually for
-
Procedures and lookups
So the citizen or customer resolves from their phone what today means queuing.
-
Transactional services
Online payments, bookings and appointments, with the gateway and the receipt where they belong.
-
Fieldwork
For people who work away from a desk: delivery, stocktaking, inspections.
-
Your system's app
When you already run an ERP or a platform and need the part that fits in a pocket.
Before you decide
What we usually get asked.
- Android, iOS or both?
- In Peru most users are on Android, so if budget forces a choice, that is where we start. Both can be built from a single codebase when the project justifies it.
- Do you publish it to the store?
- Yes, and the developer account should be yours, not ours. That is the difference between the app belonging to the company or to the supplier.
- How do I know if it is being used?
- With usage analytics from day one: which screens get opened, where people drop off and how many return. That is what tells you whether the next version is worth building.
From prototype to store
First the interface is drawn and walked through with the client. Changing a screen in the design costs an afternoon; changing it once the app is built costs weeks.
Then development, the release on Google Play or the App Store — with everything that entails in listings, permissions and reviews — and maintenance, which on mobile is not optional: each year brings new OS versions, and an un-updated app eventually leaves the store.
Shall we look at your case?
The first assessment is free and produces a written scope. Message us and we'll set it up. Monday to Friday, 10:00 – 17:00 (GMT-5).
Message us on WhatsApp