App development
How to scope a mobile app MVP without wasting the budget
Most app budgets are not destroyed by the login screen or navigation. They are destroyed by trying to launch every future feature in version one. A strong MVP proves one valuable user journey with enough quality to learn from real use.
01
Start with the job the app must do
An MVP should be described in terms of the user outcome rather than a long feature list. A field-service app may need to let an engineer see assigned jobs, capture evidence and close the job. A customer app may need to let users book, pay and manage an account.
Everything else should be tested against whether it is necessary for that first complete journey.
02
Define the backend before polishing the screens
Mobile apps usually depend on authentication, APIs, databases, notifications, payments or existing business systems. Those dependencies can drive more complexity than the visible interface.
Scoping should identify where the data comes from, what needs to be stored, which systems the app must talk to and what happens when those systems fail or are unavailable.
03
Choose cross-platform or native for a reason
Cross-platform development can reduce duplicated work when iOS and Android experiences are broadly similar. Native development can make sense when the product depends heavily on platform-specific capabilities, performance or deep device integration.
The decision should follow product requirements rather than developer preference alone.
04
Keep version one ruthlessly narrow
Separate features into launch-critical, useful soon and later. If a feature can be handled manually for the first twenty users without damaging the core experience, it may not belong in the first build.
This is especially important for marketplaces, social features, complex admin tooling and advanced analytics, where secondary systems can quickly become projects of their own.
- ✓ Core user journey
- ✓ Account and access
- ✓ Essential integrations
- ✓ Required notifications
- ✓ Minimum admin capability
- ✓ Analytics for key product events
05
Include release and operational work
A mobile project does not end when the app compiles. Store assets, privacy information, signing, testing, release configuration, crash monitoring and post-launch fixes should be part of the delivery plan.
If the app handles sensitive data or payments, security and compliance requirements also need to be identified before development starts.
06
How Virezio scopes mobile apps
Virezio mobile app projects currently start from £12,000 in the UK for defined MVP scopes. Larger products are normally phased so product discovery, core build and later feature expansion can be approved separately.
The objective is not to sell the largest possible first release. It is to create a first product that is commercially useful, technically supportable and narrow enough to validate.