What Our Mobile App Maintenance Includes
- updates for new iOS and Android versions: we test on betas, fix what breaks and upgrade libraries to supported versions;
- stability work: crash report monitoring, root causes on specific phone models and fixes;
- store releases: building new versions, passing App Store and Google Play review and responding to reviewer feedback, with timing agreed with you;
- backend support: APIs and connected services such as payments, push notifications, maps and social login;
- new features: we manage your backlog, estimate tasks and ship updates in increments, so stability is never at risk.
We support native apps built with Swift and Kotlin and cross-platform apps built with Flutter and React Native. For cross-platform projects, we pay special attention to updating the framework and its plugins, where technical debt most often piles up. See our cross-platform app development page for the approach itself.
Who Needs Ongoing Support and Who Can Get By With One-Off Work
Ongoing support is essential if the app generates revenue or your customers or employees rely on it: a store, a delivery service, a loyalty program, a dealer portal. Any outage here costs you orders and reputation.
A one-time update may be enough if the app plays a supporting role and rarely changes, such as a reference guide or an event app. In that case it's worth checking once a year against new store requirements and OS versions. Website support works differently: see our page on website maintenance and support.
Engagement Models
- Hourly, on request. Works for stable apps with occasional tasks. There is no reserved time, so urgent tasks go into the queue.
- Monthly block of hours. A fixed amount of time for updates, fixes and small improvements, with predictable response to incidents.
- Support plus development. On top of technical maintenance, we regularly ship new features according to your product roadmap. Best for apps that are actively growing.
We agree on the specific model, scope and response times for your app and put them in the contract.
If Another Team Built Your App
The most important thing at the start is to make sure you have everything you need: the current source code, access to the Apple and Google developer accounts, the Android signing keys, and access to the server and third-party services. A lost signing key or a developer account registered in the vendor's name can be resolved, but it takes time. That is why our first step is always to audit access, and only then do we start on tasks. We then build the app from the existing code, compare it with the store version, and run a technical audit of outdated libraries, crash reports and compliance with store requirements.
How We Ship Updates Without Risk
Unlike a website, you can't quickly roll back a mobile version, because a fix has to go through store review again. So we distribute builds to your team via TestFlight and Google Play internal testing, test key flows on real devices running older and newer OS versions, use staged rollouts, and watch crash reports during the first hours after release. For critical changes, such as switching payment providers, we add a mechanism in advance that prompts users to update. To keep an eye on the server and uptime, we can set up monitoring.
What We Need From You
- Access to your App Store and Google Play developer accounts with admin rights, or the ability to add us to your team.
- Source code or repository access, signing keys and build configuration.
- Access to the server, database and connected services.
- A list of known issues and feature requests, if you have one.
What Affects the Cost
- Code condition: how outdated the libraries are and how much technical debt has built up.
- Platforms: one cross-platform app or two separate native apps.
- Backend: whether it's included in support and how complex it is.
- Response requirements: how fast incidents need to be handled and whether weekend coverage is needed.
- Development scope: technical maintenance only, or regular new features as well.
Frequently asked questions
Can you take over an app that has no documentation? Yes. We write the documentation ourselves during the audit, although any existing docs help us get started faster.
What if the app was removed from the store? We identify the reason from Apple's or Google's notice, fix the violation and resubmit the app for review.
Does an app need updates if nothing in it has changed? Yes. Even without new features, it has to be rebuilt for current store requirements and tested on new OS versions.
Can support turn into rebuilding the app? Yes. If the audit shows that maintaining the old code costs more than rewriting part of it, we present both options with their pros and cons.
Which developer accounts should the app be registered under? Under your company's name.
Why Promodex
Post-launch support is a standard part of Promodex's work, not an add-on, and we've done it since 2015. Our team of 30+ includes developers, designers and marketers, so alongside technical support we can help refresh your app's design or promote it. All work is done by our in-house team with no outsourcing, and terms are transparent: you know what is being done, why, and what it costs.