New iOS every September, a new Android target API every year, store policies that change in between. I keep your app building, compliant and crash-free, and handle releases and store listings. From €290 a month, publishing from €690.
Release weather: the app year
typical year, check current dates on the stores' own pagesEvery month on Care: everything in Keep live, one release, listing changes and up to 2 hours of small fixes, about 4 hours.
Covered on Care, about 1 hour of example work.
Care covers 11 of 12 yearly items. Example year: about 88 hours of work, plus 3 hours outside the plan.
Bars show example hours per month: solid is covered by the plan, dashed is work the plan does not cover, quoted as a one-off job. Release months follow recent years; Apple and Google set the real dates, so check their own pages.
Most store listing problems are a few characters too many. Type your own listing and watch the counters and both previews; every release under a care plan includes this check.
App Store listinggeneric preview, not the real layout
Google Play listinggeneric preview, not the real layout
Order coffee and pastries ahead in Tampere and pick them up without queuing.
Limits used: App Store name 30, subtitle 30, keywords 100; Google Play title 30, short description 80, full description 4,000. Check the current limits in App Store Connect and Play Console. Sample app, not a real listing.
Send the store links of your app. I will tell you which deadlines are coming and what they will take.
Get an app care planMost apps I would care for were started by another developer. The handover is a fixed-price job, and you get a written health check before any monthly fee starts.
Repository, both store consoles and signing keys, added under your accounts. Keys are never sent by email.
The app is built from a fresh checkout. If it will not build, that is the first finding.
Outdated packages, crash baseline, target API, Xcode version and a compliance list in plain language.
A small, low-risk update through both stores, to prove the whole release path works.
The plan starts, and the year on the calendar above becomes your schedule.
The compliance list covers, among others: in-app account deletion when the app lets people create accounts (App Store Review Guideline 5.1.1(v)), a privacy manifest where the app uses the listed APIs, and the Google Play Data safety form. Check the current guidelines; they change during the year.
Monthly prices in euros, excluding VAT 25.5%. One month notice. All prices.
Stay on both stores and meet every deadline.
Deadlines plus a steady release rhythm.
For apps tied to a busy online store.
Cancel with one month notice. When you leave, you keep the repository, both store accounts, the signing keys and a written list of every service the app depends on.
Because the ground moves even when your app does not. Apple and Google ship new OS versions every year, raise the required SDK and target API levels, and change store policies in between. Monthly care turns that into small, tested updates instead of one urgent rebuild when a store blocks your next release.
Usually nothing at first. Then Google Play stops accepting updates that miss the target API level, App Store uploads need the current Xcode, and new OS versions break layouts or permissions. When an urgent fix is finally needed, it waits behind all of that. Skipping a year often costs more than the care saved.
Yes, if the source code and store access can be handed over. I start with a fixed-price health check: a clean build from the repository, outdated packages, crash reports and compliance gaps, written up in plain language. You decide on a plan after reading it. If the code cannot be recovered, I say so first.
A plan should cost less than the trouble it prevents.