Deploying a Unity game to Android involves more steps than just clicking “Build”. This checklist covers everything from Player Settings to the Google Play submission process, helping you avoid the most common release pitfalls.
1. Player Settings Configuration
- Set Company Name and Product Name (cannot change post-submission)
- Configure Bundle Identifier (com.yourcompany.gamename)
- Set minimum API level (Android 5.0 / API 21 recommended minimum)
- Choose Scripting Backend: IL2CPP for release builds
- Enable ARM64 architecture target for Google Play compliance
2. Graphics and Performance
- Enable GPU Skinning for character animations
- Use Texture Compression: ASTC for modern devices, ETC2 for older
- Configure Quality Settings per device tier
- Enable Adaptive Performance if targeting Samsung Galaxy devices
- Profile with Android Profiler before final build
3. Keystore and Signing
Create and securely store your keystore file — losing it means you can never update your app on Google Play. Use Android Keystore in Unity’s Publishing Settings, and store the keystore password in a secure password manager.
4. Build Output
- Build as AAB (Android App Bundle) for Google Play — required since August 2021
- Use APK only for direct testing/sideloading
- Enable “Split APKs by target architecture” for smaller download sizes
- Run a test build on a real device before submission
5. Google Play Console Checklist
- Complete store listing (screenshots, feature graphic, description in English)
- Fill out Content Rating questionnaire honestly
- Set up Data Safety section (required)
- Test with Internal Testing track before promoting to production
- Ensure your app complies with the target audience policies
Ozlin Info develops polished mobile games for Android and iOS. Contact us to bring your game idea to life.