Scribd
Upload
45 views3 pages

Mobile App Release Process

Release Process

Uploaded by

Harikishan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
45 views3 pages

Mobile App Release Process

Release Process

Uploaded by

Harikishan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Mobile App Release Process Document

1. Overview
This document outlines the process for releasing mobile app builds, covering both iOS and
Android platforms. It ensures a structured approach for building, testing, and deploying
new versions of the app.

2. Pre-Requisites
• Version Control System: Ensure the latest code is committed to the version control system
(e.g., Git).
• Build Tools: Install the necessary development tools (Xcode for iOS, Android Studio for
Android).
• Test Devices: Access to physical devices or emulators to test builds.
• App Store Developer Accounts: Access to App Store (iOS) and Google Play Developer
Console (Android).
• Release Notes: Prepare release notes detailing the new features, bug fixes, and other
updates.

3. Build Preparation

3.1 iOS Build Preparation


• Update App Version: Update the version number and build number in the Xcode project
(Info.plist file).
• Set Build Configuration:
- Choose the appropriate scheme (Debug/Release).
- Ensure the correct provisioning profiles and certificates are selected.
• Dependency Management: Run `pod install` for CocoaPods (if applicable) to ensure all
libraries are updated.
• Run Unit Tests: Ensure all unit tests pass.

3.2 Android Build Preparation


• Update App Version: Update `versionCode` and `versionName` in the `build.gradle` file.
• Set Build Configuration:
- Ensure the correct build variant (Debug/Release) is selected.
- Ensure the correct signing configurations (keystore) are applied.
• Dependency Management: Run `./gradlew clean` and `./gradlew build` to clean and
rebuild the project.
• Run Unit Tests: Ensure all unit tests pass.
4. Building the App

4.1 iOS Build


• Archive the Build: In Xcode, select Product > Archive.
• Validate the Build: Ensure the build passes validation for the App Store.
• Export the IPA: Export the `.ipa` file for testing purposes.

4.2 Android Build


• Generate APK/AAB: In Android Studio, select Build > Generate Signed APK/AAB.
• Export the APK/AAB: Export the signed APK or AAB file.

5. Testing the Build

5.1 Internal Testing


• Distribute to QA Team:
- iOS: Use TestFlight to distribute the build to the internal QA team.
- Android: Use Google Play Internal Testing track or distribute APK for testing.
• Run Manual Tests: QA team should run manual tests across a range of devices and
operating system versions.
• Run Automated Tests: Run any automated UI tests.
• Bug Fixes: Address any issues identified during testing and repeat the build process if
necessary.

5.2 External Testing


• Beta Testers:
- iOS: Use TestFlight to invite external beta testers.
- Android: Use Google Play's Beta Testing feature.
• Gather Feedback: Monitor feedback and crash reports.
• Fix Issues: If needed, fix issues and rebuild the app before the final release.

6. App Store Submission

6.1 iOS Submission to App Store


• App Store Connect:
- Log in to App Store Connect.
- Create a new version in your app listing.
- Upload the IPA using Xcode or the Transporter app.
• Set Metadata: Add release notes, app screenshots, app description, and version number.
• Submit for Review: Submit the app for Apple’s review process.
• Approval: Once approved, the app will be available on the App Store.
6.2 Android Submission to Google Play Store
• Google Play Console:
- Log in to Google Play Console.
- Create a new release in the Production track.
- Upload the signed APK/AAB file.
• Set Metadata: Add release notes, app screenshots, app description, and version number.
• Submit for Review: Submit the app for Google’s review process.
• Approval: Google may automatically release the app, or you can choose to manually
release it after review.

7. Post-Release Steps
• Monitor Crashes and Errors: Use platforms like Firebase Crashlytics or Sentry to monitor
crashes and performance issues.
• Respond to User Feedback: Monitor user reviews and feedback on the App Store/Play
Store.
• Plan for hotfixes if any critical issues arise post-release.
• Update Release Documentation: Record the build version, release date, and any issues
encountered.

8. Versioning Guidelines
• Major Version (X.0.0): Introduces significant new features or changes.
• Minor Version (X.X.0): Adds minor features and improvements.
• Patch Version (X.X.X): Fixes bugs and patches.

9. Checklist
• Update version and build numbers.
• Test build on devices/emulators.
• Pass unit and UI tests.
• Upload build to App Store Connect / Google Play Console.
• Set release metadata.
• Submit for review.
• Monitor post-release performance.

You might also like