Mobile App Development Release and Operations Syllabus

Release and Operations syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Release and Operations in Mobile App Development, not a summary of it.

1. 1

   Build and Signing

   3 topics

   • iOS Provisioning and Certificates
   • Android Keystores and Signing
   • Build Variants and Flavors
2. 2

   CI/CD for Mobile

   3 topics

   • Automated Builds
   • Automated Testing Pipelines
   • Beta Distribution
3. 3

   App Store Deployment

   4 topics

   • App Store Connect Submission
   • Google Play Console Submission
   • App Review Guidelines
   • Store Listing and ASO
4. 4

   Monitoring and Maintenance

   4 topics

   • Crash Reporting
   • Analytics and User Behavior
   • Feature Flags and Remote Config
   • Over-the-Air Updates
5. 5

   Monetization and Growth

   3 topics

   • Subscription and IAP Models
   • In-App Advertising
   • Push Engagement and Retention

Release and Operations flashcards for Mobile App Development

19 of 51 cards from the Release and Operations deck — real questions with worked answers.

1. In iOS code signing, what is the difference between a Development and a Distribution certificate?

   A Development certificate lets you run and debug apps on registered test devices; a Distribution certificate is used to sign apps for release to the App Store or for enterprise/ad-hoc distribution. Both are issued by Apple and tie the build to your team identity.

2. What are the four components required to build an iOS provisioning profile?

   (1) An App ID (bundle identifier), (2) a signing certificate (development or distribution), (3) a list of registered device UDIDs (for development/ad-hoc), and (4) the entitlements/capabilities. Apple bundles these into a .mobileprovision file.

3. What is the purpose of an Apple provisioning profile?

   It links a specific App ID, signing certificate, and set of authorized devices so that iOS can verify an app is authorized to run and which entitlements it may use. It is embedded in the app bundle at build time.

4. Distinguish the three iOS distribution provisioning profile types.

   App Store (submit to App Store, no device list), Ad Hoc (install on up to 100 registered devices per type without the store), and Enterprise/In-House (internal distribution via Apple Developer Enterprise Program, no store).

5. What is an Apple App ID's difference between an Explicit and a Wildcard App ID?

   An Explicit App ID matches exactly one bundle identifier (e.g. com.acme.app) and is required for capabilities like Push Notifications or In-App Purchase. A Wildcard App ID (com.acme.*) matches many bundle IDs but cannot use most entitlements.

6. In Android app signing, what is a keystore and what does it contain?

   A keystore is a binary file (typically .jks or .keystore) that securely stores one or more cryptographic key pairs (private key + certificate). Each key is protected by the keystore password and its own key alias/password, and is used to sign APKs/AABs.

7. What is the difference between the upload key and the app signing key under Google Play App Signing?

   The upload key is what you use to sign the artifact you upload to Play; Google verifies it, strips it, and re-signs the app with the app signing key it holds. If your upload key is lost you can reset it, but the app signing key stays constant so users can always update.

8. Compare Android's APK signing scheme v1, v2, and v3.

   v1 (JAR signing) signs individual files, is slow and vulnerable to some tampering; v2 signs the whole APK as a block for integrity and faster verification (Android 7.0+); v3 adds key rotation support (Android 9.0+). v4 (Android 11+) adds incremental/streaming install signatures.

9. What is a build flavor (Android) or scheme/configuration (iOS), and give a typical use.

   A build variant mechanism that produces different versions of an app from one codebase, e.g. free vs paid, or dev/staging/prod, each with its own application ID, resources, API endpoints, and signing config.

10. In Android Gradle, how does a build variant relate to build types and product flavors?

    A build variant is the cross-product of a build type (e.g. debug, release) and a product flavor (e.g. free, paid). Flavors × types = variants, so 2 flavors × 2 types yields 4 variants (freeDebug, freeRelease, paidDebug, paidRelease).

11. Why should debug and release build types typically use different application IDs or suffixes?

    Using an applicationIdSuffix (e.g. .debug) lets debug and release builds be installed side-by-side on one device and keeps analytics, crash reports, and backend data for test builds separate from production.

12. What is Continuous Integration (CI) in the context of mobile automated builds?

    CI is the practice of automatically building and testing every code change pushed to the repository, giving fast feedback that the code compiles and passes tests. Common tools: GitHub Actions, GitLab CI, Bitrise, Codemagic, Jenkins, Fastlane.

13. What does Fastlane's `gym` (build_app) and `match` do?

    `gym`/`build_app` compiles and packages an iOS app into a signed .ipa; `match` centrally stores and syncs signing certificates and provisioning profiles in an encrypted git repo so a whole team shares consistent credentials.

14. Define the test pyramid and its typical proportions in a mobile testing pipeline.

    A model recommending many fast unit tests at the base, fewer integration tests in the middle, and few slow, brittle end-to-end/UI tests at the top. A common heuristic is roughly $70\%$ unit, $20\%$ integration, $10\%$ UI tests.

15. Differentiate unit, integration, and UI (end-to-end) tests for mobile apps.

    Unit tests verify a single function/class in isolation (fast, no device); integration tests verify modules working together (e.g. repository + network); UI/end-to-end tests drive the full app on a device/emulator (e.g. XCUITest, Espresso) simulating user flows.

16. What is beta distribution and name two common services for it.

    Beta distribution delivers pre-release builds to a limited group of testers before public launch to gather feedback and catch bugs. Common services: TestFlight (iOS), Google Play Internal/Closed testing, and Firebase App Distribution (both platforms).

17. On TestFlight, what are the limits and review rules for internal vs external testers?

    Internal testers: up to 100 users who are members of your App Store Connect team, no Apple review, immediate access. External testers: up to 10,000 users invited by email or public link, and the first build requires a Beta App Review.

18. List the tiers of Google Play testing tracks in order of audience size.

    Internal testing (up to 100 testers, fastest), Closed testing (specific email lists or Google Groups), Open testing (public opt-in beta), then Production. Builds promote up the tracks toward full release.

19. What is a staged (phased) rollout on the app stores?

    Releasing a new version to a growing percentage of users over time (e.g. $1\% \to 5\% \to 20\% \to 100\%$) so you can monitor crashes and metrics and halt the rollout before it reaches everyone if problems appear.

See more Release and Operations flashcards →

Planning Release and Operations for Mobile App Development

Release and Operations (Mobile App Development) FAQ