1)Pre-Deployment Checklist
Before starting the deployment, I make sure I have:
- A React Native project tested and working properly on Android
- Node.js, JDK, and Android Studio configured
- A Google Play Developer Account
- App icon
- 2–3 feature screenshots
- Required privacy policy and app information
2) Generate & Secure the Keystore
The first important step is generating the Android keystore used to digitally sign the application.The keystore and its password are extremely important because they are required for future app updates.
To publish an application on the Google Play Store, Google requires every Android app to be digitally signed with a private certificate. This keystore acts as your digital identity.
3) Configure the Application ID
I verify the applicationId in
android/app/build.gradle
For example:
applicationId “com.yourcompany.yourappname”
This uniquely identifies the application on Google Play.
4) Complete Development & Testing
Before creating the production build, I make sure the required features, UI, permissions, API integrations, and other configurations are completed.
I also test the application properly on Android before moving towards production.
5) Generate the Release Build
For development or QA testing, we can generally share an .apk build.
For Google Play production releases, Android apps are submitted using the Android App Bundle (.aab) format.
The .aab allows Google Play to generate optimized APKs for different devices.
6) Create the App in Play Console
Then I create the application in Google Play Console and configure:
- App name
- Default language
- App/Game type
- Free/Paid selection
- Required declarations and policies
7) Complete App Content & Policies
This is one area where deployment can take some time.
Get koti’s stories in your inbox
Join Medium for free to get updates from this writer.
Depending on the application, Play Console may require:
- Privacy Policy
- Ads declaration
- App Access
- Content Rating
- Target Audience
- Data Safety
These details need to accurately represent how the application works and handles user data.
8) Prepare the Store Listing
Next comes the information users see on the Play Store:
- Short description
- Full description
- App icon
- Feature graphic
- Phone screenshots
I make sure the store listing is complete before creating the production release.
9️) Create the Production Release
Go to:
Testing & release → Production → Create new release
Then upload the .aab, add the release name and release notes, and save the release.
10) Review, Testing & Production Rollout
Before going live, I carefully review everything in the Play Console.
For applications that require login, I provide the required test credentials so the Google review team can access and test the complete application.
Sometimes Google may also request a video recording or YouTube link demonstrating specific features or functionality.
After resolving any issues and completing the review requirements, the release can be rolled out to production.
11) The Real Challenge: Android & Play Console Issues
One thing I learned from deployment is:
Generating the build is only one part of the job.
Sometimes Android or Google Play introduces new requirements, security changes, or build compatibility issues.
For example, Android recently introduced requirements around 4 KB vs 16 KB memory page sizes, which can require checking native dependencies and updating the project accordingly.
So, when a deployment issue appears, I don’t treat it as just a “build error.”
I identify:
Why the google changed 4kb to 16kb
What changed → Why it is happening → Which dependency/configuration is affected → How to fix it → How to test it again.
That troubleshooting experience has become an important part of my deployment knowledge.
