The drivers and their effect
| Driver | Costs more when | How to ease it |
|---|---|---|
| Number of features | You ask for everything in version one | Start with what the app cannot work without |
| Platforms | The app is built twice, separately | One app for both platforms |
| Payments and integrations | Many outside systems | One payment method first |
| Design | Custom artwork and motion on every screen | A simple identity and shared components |
| Who builds it | A large team with many hours | Compare the three routes |
Costs people forget
- Developer accounts with Apple and Google.
- Hosting and the database every month.
- Payment gateway fees on each transaction.
- Verification text messages, if sign-in is by phone number.
- Updates after each new release of the phone systems.
How to get an estimate you can trust
- 1Write the requirements
The list of screens and features on one page. Without it every quote is a guess.
- 2Split them: now and later
What goes into the first version and what waits. This is the biggest decision affecting cost.
- 3Ask for an itemized quote
Build cost, monthly running cost and maintenance, each on its own.
- 4Ask about ownership
Who owns the project, the accounts and the data if you change supplier?