App maintenance

App maintenance services that keep your iPhone and Android app current with each store’s rules

We read your crash data and your store accounts, write down what needs updating, and ship the fixes as releases you approve.

Get your app’s maintenance scoped in writing
Trusted by the world's fastest-growing brands

What maintenance is

Upkeep that follows the platforms your app runs on

App maintenance services keep a live app working as Apple, Google and its own software libraries change around it. The work covers reading the app’s health, updating what has fallen behind, and releasing the result to the stores.

Health checkUpdate planRelease recordSample Brightwater Car Wash · member app51 hours6 itemsRelease 3.14.1 · 38 h3.15 · 13 hBC-31Fix the ANR on wash history12 hBC-32Raise the target API level to 3616 h

A health check first

We read your crash and ANR data, your store listings and your build setup, and write down what is healthy and what is behind, so the first piece of work is a diagnosis.

Updates on a written plan

OS changes, store deadlines and library releases become a list with an hour estimate per item. You see the plan and change it before the work starts.

Releases with a record

Each release carries a test result and a rollout log, so you can see what changed, what was checked and what the stores did with it.

Two ways to maintain

A standing arrangement or a fix when something breaks

The two differ in when the work happens and who is watching in between.

Fix on demandWork ordered when a problem appearsStanding maintenanceWork planned ahead of platform changes
When work startsAfter a user, a review or a store notice reports the problemAhead of a store deadline or an OS release, from a plan you have approved
Who watches the appYour own team looks when time allows, or nobody does until something breaksWe read crash and ANR data and the store consoles for each release
How cost behavesEach job is priced when it arrives, and urgent jobs are priced under pressureScoped and quoted in writing, so planned work has a known size
Knowledge of the codeWhoever has time picks it up, and may read the code for the first timeThe same engineers see the app repeatedly and learn where it is fragile
Best whenThe app is small, internal or close to retirement, and an occasional repair is enoughThe app earns money or serves customers daily and a store removal would hurt
Where standing maintenance fits

A small internal app can sit on the on-demand side for years without trouble. An app customers open every week has deadlines it cannot miss, since Google Play and the App Store both set dates after which an out-of-date app is limited or cannot be updated. If another vendor built your app, the health check also tells you what you inherited.

Rules maintenance works inside

Six facts that set the maintenance calendar

Store policies, build requirements and platform releases. Sources under each.

  1. App Store removalApple

    Apple says an app that no longer functions as intended, or that you are no longer actively supporting, will be removed.

    The guidelines state this in their opening section, and the Design introduction adds that apps that stop working or offer a degraded experience may be removed at any time. Guideline 2.5.1 asks developers to keep apps up to date and phase out deprecated features. Support is therefore a condition of staying listed.

  2. Build toolchainApp Store Connect

    Since April 28, 2026, uploads to App Store Connect must be built with Xcode 26 or later.

    Apple’s requirements page says the build must use an SDK for iOS 26, iPadOS 26 or the matching tvOS, visionOS or watchOS release. It also says that since September 9, 2026, iOS and iPadOS apps uploaded must target iOS 13 or later. An app whose build machine stays on an old Xcode cannot be updated.

  3. Privacy manifestsApp Store Connect

    Since May 1, 2024, uploads must list approved reasons for the required-reason APIs the code and its SDKs use.

    Apple’s SDK page adds that developers answer for all the code a third-party SDK brings in, and that listed SDKs must ship a privacy manifest and a signature. Updating a library can therefore change what an app has to declare. Our health check reads the manifest of each SDK against that list.

  4. Target API levelGoogle Play

    Since August 31, 2026, Google Play has required new apps and updates to target Android 16 (API level 36).

    Existing apps must target Android 15 (API level 35) or higher to stay available to new users on devices running a newer Android. Below that, an app is offered only on devices running the same Android version or lower. Extension requests were allowed until November 1, 2026, a date that has passed.

  5. Android vitalsGoogle Play

    Google Play may reduce the visibility of an app whose crash rate passes 1.09% or ANR rate passes 0.47%.

    The overall bad behavior thresholds are 1.09% for user-perceived crashes and 0.47% for user-perceived ANRs, and 8% for either on a single phone model. Play judges the app on a 28-day window, so a fix takes time to show in the console. Play may also show a warning on the store listing.

  6. Android 17Android Developers

    Apps targeting Android 17 (API level 37) can no longer opt out of resizing on large screens.

    The Android 17 release notes say screen orientation, resizability and aspect ratio attributes are ignored on screens at least 600dp wide for apps targeting API 37, with games exempt.

What we maintain

Six kinds of upkeep, and what each produces

A scope picks the ones your app needs. The health check says which, and in what order.

Platform updatesUpdate planapp/build.gradle.ktsSince Aug 31, 2026defaultConfig {−targetSdk = 35+targetSdk = 36versionName = "3.14.1"AndroidTarget API 35 to 36BC-32 · 16 hiOSXcode 26, iOS 26 SDKMeets

OS and SDK updates

We build the app against each new iOS and Android release as the platform publishes it, change what breaks, and raise the target API level and Xcode version when a store requires it. You receive: an update plan with hours per item and the build notes for each platform release.

iOSAndroidTarget level
Android vitals28 days to Oct 31Google’s bad-behavior threshold0.84%Crash ratelimit 1.09%0.52%ANR ratelimit 0.47%3.1%Worst modellimit 8%BC-31ANR in the wash-history screen12 h

Crash and ANR monitoring

We read Android vitals in Play Console, the crash reports in Xcode Organizer and your crash-reporting tool, group crashes by cause and rank them by how many users each reaches. You receive: a ranked crash list, each entry with the stack trace, the devices affected and a proposed fix.

Dependencies2 need workSample Brightwater app4 SDKsPayments SDKEntry neededBC-33Push SDK2 versions behindBC-34Analytics SDKUp to dateMaps SDKUp to dateupgrade/bc-34-push-sdkUpgrade branch

Libraries and dependencies

Third-party SDKs for payments, analytics, push and maps release new versions and retire old ones. We list what the app depends on, which versions are behind and which have a changed privacy manifest, then upgrade in an order that limits breakage. You receive: the dependency list and the upgrade branch.

Store requirements3 openApp Store ConnectXcode 26 or latersince Apr 28, 2026MeetsRequired-reason APIssince May 1, 2024Entry dueBC-33Play ConsoleAPI 36 for updatessince Aug 31, 2026BehindBC-32ANR under 0.47%28-day windowOverBC-31

Store requirements

We read the notices in App Store Connect and Play Console, check the app against the published requirements, and prepare the changes: privacy manifest entries, data safety answers, listing fields and review notes. You receive: a requirements checklist with the source and date for each item and the status of each.

Bug logFixed and retestedFoundPush check failed on Android 14CauseThe push SDK update in BC-34FixFixed in build 3RetestPassedReleaseShipped in 3.14.1Nov 4

Bug fixes and support

Reports from users, reviews and your own staff go into a tracker you can read. We reproduce each one, find the cause, fix it and add a test where the bug could return. You receive: a bug log with the steps, the cause and the release each fix shipped in.

Release 3.14.1Approved Nov 2Android rolloutiPhone: released Nov 410%50%100%Nov 2Nov 4Nov 6Nov 9Passed first time17 of 18Failed, fixed in build 3, passed on retest1

Releases and rollout

Builds go to TestFlight and Play internal testing first, then to the stores. On Android we use a staged rollout, so a bad release reaches a share of users before all of them. Each build waits for your sign-off before it is released. You receive: the release record with test results and the rollout log.

How it runs

Assess, plan, release, watch

A release goes out after you approve it.

health-check.csv

App health check, 28 days to October 31, 2026

Sample · Sample Brightwater Car Wash membership app, Albuquerque, NM
CheckReadingLimitResultTicket
Android user-perceived crash rate0.84%1.09%Within
Android user-perceived ANR rate0.52%0.47%OverBC-31
Worst phone model, crash rate3.1%8%Within
Android target API level3536 for updates since August 31, 2026BehindBC-32
iOS build toolchainXcode 26, iOS 26 SDKXcode 26 or laterMeets
Privacy manifests, 4 SDKsPayments SDK update adds a required-reason APIApproved reasons listedEntry neededBC-33
Three findings in six checks. The limits are quoted from Google’s Android vitals and target API pages and from Apple’s upcoming requirements, each read November 9, 2026.

Our stack

The tools behind your app’s upkeep

The consoles, build tools and monitors we work in. Pick one for the detail.

App Store Connect
Why App Store Connect

App Store Connect is Apple’s site for uploading builds, answering privacy questions and reading review messages.

How we use it

Your account holds the app, and we read its notices and requirements pages before they turn into a rejected update.

iOS controlMetadataOfficial
App Store ConnectYes
Third-partyRead
NoneNo
GuessworkNo

Questions

App maintenance services, answered

Start here

Get your app’s maintenance scoped in writing

Tell us where the app stands and who built it. We’ll send back a written scope.