Launching an app is the start of the costs, not the end. Phones, operating systems and stores change every year, and your app has to keep up.
The ongoing items
- Store fees. Apple’s membership is annual; Google Play’s registration is one-time. Each publishes its current amount.
- Hosting and services. The server, database, backups, email delivery, push notifications and any paid APIs, which grow with usage.
- Operating-system updates. New versions can change behaviour; the app needs testing and often adjustments each year, and stores may require updated build targets.
- Fixes. Bugs found by real users on real devices.
- Security updates for libraries and the server.
- Support. Answering users, and handling requests such as account deletion.
- Further development. New features based on use.
How to plan
- Ask for running costs to be listed separately from the build quote.
- Agree who monitors errors and who responds.
- Reserve time each year for compatibility updates.
- Keep the code and accounts in your ownership so maintenance can move to another developer if needed.
A modest, regular maintenance arrangement is usually cheaper and less risky than emergency work after something breaks.