Over the past 12 years our team has built and maintained mobile apps for payments, delivery, augmented reality and travel. The technologies changed many times. A few lessons did not.
1. The first release is the easy part
Most of an app’s life happens after launch. Plan for analytics, crash monitoring, feature flags and a steady release rhythm from the start, and the second year will be far cheaper than the first.
2. Write requirements down — properly
Every project we run starts with detailed requirements gathered module by module and approved by the client. The biggest risk in any project is a change of requirements after the architecture is set. Clear documentation does not remove that risk, but it makes every change visible and manageable.
3. Native still matters for demanding apps
For payment apps, AR or anything that leans on the camera, sensors or heavy animation, native iOS and Android development continues to give the most reliable result.
4. QA is not a phase, it is a team
A QA team that tests every release in detail catches the problems users would otherwise report in app-store reviews. It is always cheaper to find an issue before release than after.
5. Respect the people using the app
A driver in traffic, a customer paying a bill, an architect presenting to a client — each uses the app in a real situation with limited attention. Designing for that moment matters more than any single feature.
If you are planning a new app or need a team to take an existing one further, tell us what you are building.