Services

Mobile app support and maintenance

Store policies, new iOS and Android releases, certificates and push delivery. Apps get delisted over an outdated SDK, not over bugs.

Timelinemonthly

What's included

Target SDK updates for store policy
Testing against new iOS and Android
Certificate and provisioning renewal
Crash monitoring by device
Push delivery diagnostics
Release builds and submissions
Store review support

A mobile app differs from a website in one decisive way: you don't control the environment it lives in. A website can be updated any minute you like. An app update travels through review that takes anywhere from hours to several days. Which means a hotfix stops being instant, and anything that can be verified in advance has to be verified in advance.

The second difference is that your deadlines are set by the stores rather than by your business. Apple and Google raise minimum target SDK requirements every year, and an app that misses them stops being served to new users before eventually being delisted. Technically nothing is wrong: no bugs, existing users are fine — there are simply no new installs. That deadline arrives as an email which is very easy to miss.

How we work

Project onboarding. We review versions, certificate and provisioning status, developer console access, and dependency currency. Then we build a calendar of store deadlines.
Tracking platform requirements. We follow policy changes and target SDK dates and update ahead of time, rather than in the final week before removal.
Testing on new OS releases. New iOS and Android versions ship every autumn. We run the app against betas to catch breakage before your users upgrade.
Crash monitoring. We watch crash reports broken down by device and OS version, so a failure affecting one uncommon handset still gets found — the aggregate average hides it completely.
Certificates and keys. Renewals go on a calendar. An expired signing certificate means you cannot ship an update precisely when you urgently need to.
Releases. We build, sign and submit, then shepherd the review and answer whatever the store raises.

What you get

An app that stays listed and keeps working on current operating systems. Platform deadlines are met on schedule rather than in an emergency. Crashes show up as numbers rather than as one-star reviews.

Almost every app has a server side, and that breaks for entirely different reasons — load, queues, migrations. That's web application support, and it makes sense to keep both halves with one team. Plans and response times are on the technical support page.

Timeline

Onboarding takes about a week: console access, certificates, and getting the project building on our side. Then month to month. One honest caveat: an urgent fix still has to pass store review, so our SLA commits to the time until a build is submitted, not until users see the update. Promising the latter would be dishonest.

A typical scenario

Picture an app released two years ago and untouched since, because it works. An email arrives from the store: from a given date, apps on the old target SDK will no longer be served to new users. The email gets lost in a marketing inbox. Six months later the sales team notices installs have stopped entirely. By then the update needs more than an SDK bump — half the dependencies have aged out too. With ongoing maintenance that deadline lands in a calendar the day it's announced and closes with a routine release.

FAQ

The app works. Why touch it at all?

Because store requirements change independently of you. The minimum target SDK rises every year, and an app that misses it first stops reaching new users and then gets delisted. Whether the app functions has nothing to do with it.

What does mobile app maintenance cost?

Keeping an app current without active feature work sits at the lower end. Regular releases with new functionality are priced by scope and look closer to a product team engagement.

How fast can you ship an urgent fix?

We prepare and submit a build within the response time your plan specifies. After that it's the store's call: review runs from hours to several days and we can't accelerate it. That's why the SLA covers submission rather than publication.

We've lost our certificates and console access. What now?

Developer account access is recoverable through the account owner or store support — bureaucratic but solvable. Signing certificates can often be reissued, though on Android losing the app signing key can mean you're unable to update the existing listing at all. We assess case by case.

Push notifications stopped arriving. Can you fix it?

First we find where the chain breaks: the server isn't sending, the platform isn't accepting, or the device isn't displaying. Common causes are an expired key, changed project settings, or the user revoking permission. Diagnosis usually takes a few hours.

Do you handle store review rejections?

Yes. Rejections are routine and usually about privacy declarations, permissions or metadata rather than code. We respond to the reviewer, adjust what's needed and resubmit.

Will you take on an app you didn't build?

Yes, after onboarding. The non-negotiable requirements are source code and developer console access. Without them maintenance is technically impossible — there would be nothing to build and sign a release with.

Message on Telegram → Message on MAX ← All services