What release and maintenance work includes
Building the app is only part of the job. Getting it through review and keeping it working for years is the rest. I cover:
- CI/CD. Automated builds, tests and signing with Xcode Cloud or GitHub Actions and fastlane, so releases do not depend on one person’s laptop.
- TestFlight. Builds for internal testers and external beta groups, with release notes testers can actually follow.
- App Store Connect setup. App records, in-app purchases and subscriptions, privacy details, age rating, screenshots and metadata.
- Submission and review. Preparing the build and answering App Review questions, and fixing whatever caused a rejection.
- Crash and stability monitoring. Sentry or Firebase Crashlytics, with real crash reports turned into fixes.
- Yearly iOS updates. Testing on each new iOS beta, adopting required SDK changes, and fixing what breaks before your users notice.
- Ongoing improvements. New features, performance work and dependency updates on a steady cadence.
Typical situations
“The app is finished, but we cannot get it into the App Store”
Signing errors, confusing App Store Connect settings, or a rejection you do not understand. This is often a short, focused piece of work. Apple’s own App Review Guidelines are the reference, and knowing how they are applied in practice saves rounds of resubmission.
“Our developer left, and nobody knows how to release”
If the app cannot even be built, that becomes an app rescue. If it builds but the release process lives in someone’s head, I write it down and automate it.
“We want someone on call for the app long term”
A small business or a product team without in-house iOS skills often needs a dependable person who keeps the app current, handles the yearly iOS update cycle and ships improvements when needed.
Proof: an app maintained since 2021
My Disc Golf is my own app, live on the App Store since July 2021 and still actively maintained. It runs on iPhone and iPad, includes a database of thousands of PDGA-approved discs, GPS distance measurement, monthly, yearly and lifetime purchase options, and 18 languages. Version 2.1.0 shipped in July 2026. Keeping an app like that healthy through five years of iOS releases is exactly the work this page describes.
Fokus Zone, my app blocker, has been on the App Store since January 2026 and depends on Apple’s Screen Time framework and location services, two areas where iOS updates can change behavior. Watching for that is part of maintaining it.
As a lead iOS developer I sustained weekly releases for years, and I have shipped a single app in 40 languages. A release train that size only works with solid automation and disciplined review; see app localization for the language side.
| Area | What I set up or handle |
|---|---|
| Build and sign | Xcode Cloud, GitHub Actions, fastlane, XcodeGen |
| Beta testing | TestFlight internal and external groups |
| Store | App Store Connect, submission, review responses |
| Monitoring | Sentry, Firebase |
| Platform updates | New iOS and Xcode versions every year |
Who owns the accounts
Your app should live in your Apple Developer account and your source repository. I work inside them with the access you grant, so if we ever stop working together, everything stays with you. The exact arrangement is agreed in writing before work starts.
How maintenance starts
- Email me at contact@hobbysoft.pro with a link to the app (or a description if it is not live yet) and what you need.
- Short discovery. I look at the codebase, the current release process and any crash data.
- Proposal. What I would set up first, and how ongoing maintenance would work for your app. Terms depend on scope and are agreed up front.
- First release under the new process, so you see it working rather than taking my word for it.
Next step
If your app needs a reliable path to the App Store, or someone to look after it after launch, send a few lines to contact@hobbysoft.pro.
