Updating and Maintaining Published Apps

# CHAPTER 18

Updating and Maintaining Published Apps #

1. Introduction #

Launching version 1.0 of your app is a massive achievement, but in the software world, software that is not updated is considered dead. User expectations evolve, new OS versions break old code, and competitors release new features. Consistent, high-quality updates signal to both users and store algorithms that your app is healthy and actively maintained. In this chapter, we will learn the professional workflow for pushing app updates, managing changelogs, and maintaining long-term stability.

2. Learning Objectives #

By the end of this chapter, you will be able to:

• Properly increment Version and Build numbers.

• Write effective, user-friendly Release Notes (Changelogs).

• Utilize Staged Rollouts (Phased Releases) effectively.

• Understand Force Update mechanisms.

• Plan for long-term OS maintenance.

3. The Anatomy of an Update #

To update an app on the App Store or Google Play, you cannot simply overwrite the old file. You must:

1. 1. Increment the Version Number (e.g., from 1.0.0 to 1.1.0).

1. 2. Increment the internal Build Number (e.g., from 1 to 2).

1. 3. Archive/Bundle the new build.

1. 4. Upload it to the console.

1. 5. Create a new Release in the console, attach the new build, and provide Release Notes.

1. 6. Submit for review.

4. Semantic Versioning (SemVer) #

Professional teams use a system called Semantic Versioning, formatted as MAJOR.MINOR.PATCH (e.g., 2.1.4).

• PATCH (2.1.4 -> 2.1.5): You fixed a small bug. No new features.

• MINOR (2.1.4 -> 2.2.0): You added a new feature (e.g., Dark Mode) in a backwards-compatible manner.

• MAJOR (2.1.4 -> 3.0.0): You completely redesigned the app, overhauled the UI, or made incompatible API changes.

5. Writing Effective Release Notes #

Release notes (the "What's New" text) are read by power users and tech journalists. Bad Release Note: > "Bug fixes and performance improvements." *(Users hate this. It tells them nothing).*

Good Release Note: > "In this update: > 🚀 Added Dark Mode support! > 🐛 Fixed a crash that occurred when adding a credit card. > ⚡ Optimized image loading speeds by 20%."

6. Staged Rollouts / Phased Releases #

Never release an update to 100% of your users immediately. Even with QA testing, a bug might slip through that only affects specific devices.

• Google Play (Staged Rollout): You can set the rollout to 5%, 10%, 20%, etc.

• Apple App Store (Phased Release): Apple handles this automatically over 7 days (Day 1: 1%, Day 2: 2%, Day 3: 5%, Day 4: 10%, etc.).

*Workflow:* Start the phased release. Monitor Crashlytics for 24 hours. If there is a spike in crashes, Pause the rollout. You just saved 95% of your users from experiencing the bug. Fix the bug, compile a new build, and start a new release.

7. Force Update Mechanisms #

What happens if you discover a critical security flaw in Version 1.0, or your backend API changes entirely? You need to force users to update to Version 1.1, otherwise, their app will break. Neither Apple nor Google provides a built-in "Force Update" button. You must build this logic into your app. How it works:

1. 1. On app launch, the app pings your backend: "I am version 1.0. What is the minimum allowed version?"

1. 2. Backend responds: "Minimum is 1.1."

1. 3. App displays a full-screen, un-dismissible popup: "A critical update is required to continue." with a button linking directly to the App Store.

8. Dealing with OS Updates #

Every September, Apple and Google release new major OS versions (e.g., iOS 18, Android 15). You must proactively test your app on the Beta versions of these operating systems during the summer. Often, deprecated APIs are finally removed, which will cause your app to crash instantly on the new OS.

9. Common Mistakes #

• Forgetting to update Screenshots: If Version 2.0 completely changes the UI, but your App Store screenshots still show Version 1.0, users will be confused and angry. Always update marketing assets alongside major releases.

• Rushing an update to fix a bug: Panic-fixing a bug and skipping the QA process often introduces two new bugs. Use staged rollouts to mitigate panic.

10. Security Recommendations #

• When updating, check if any of your third-party SDKs (like Facebook SDK, Stripe SDK) have released security patches. Keeping dependencies updated is a critical maintenance task.

11. Exercises #

1. 1. Open the App Store or Play Store on your device. Look at the "Recently Updated" apps section. Read the Release Notes of 3 different apps. Which ones are good, and which ones are vague?

1. 2. Formulate a Semantic Versioning number for the following scenario: Your current app is 1.4.2. You just added a new "Export to PDF" button. What is the new version number?

12. Publishing Checklist #

• [ ] Version and Build numbers are incremented in Xcode/Android Studio.

• [ ] Release Notes are written detailing specific fixes and features.

• [ ] Marketing screenshots are updated (if the UI changed).

• [ ] Phased Release / Staged Rollout is enabled in the console.

• [ ] Crashlytics dashboard is open and monitored for 24 hours post-launch.

13. MCQ Quiz with Answers #

14. Interview Questions #

• Q: Describe how you would implement a "Force Update" mechanism in a mobile application.

• Q: What is the purpose of Semantic Versioning, and how is it formatted?

15. FAQs #

Q: Do I have to wait for Apple's review process every time I push a small bug fix? A: Yes. Every single update requires a review. However, if it is a critical hotfix, you can request an "Expedited Review" in App Store Connect, which Apple usually honors and processes within a few hours.

16. Summary #

Maintaining an app requires discipline. By utilizing Semantic Versioning, writing clear release notes, leveraging staged rollouts to protect your user base, and planning for yearly OS updates, you transform from a casual developer into a professional app maintainer.

17. Next Chapter Recommendation #

Despite your best efforts, sometimes Apple or Google will push back and say "No." In Chapter 19: Common App Rejections and How to Avoid Them, we will explore the most frequent reasons apps get rejected during review and how to appeal those decisions.