Preparing, uploading, and publishing an Android App to the Google Play Console is a fairly long and involved process. In this video, I walk you through this process using modern features of Android Studio and Google Play, including code minification with R8 (we used to use Proguard), App Signing By Google Play, and the Upload App Bundle Feature. I also show you how to set up a Keystore, sign your App, publish an Alpha release for testing, and finally to upgrade that Alpha release to a full release.
Timestamps: 0:10 Requirements for following the tutorial 0:52 Overview: Preparing an application for upload to Google Play 1:12 Ensuring a unique Package ID 1:40 Proguard and its replacement R8 for minification and obfuscation 2:31 A note on adding rules to Proguard and/or R8 (this often isn’t necessary though) proguard-rules.pro 3:13 Creating a Keystore in Android Studio and signing Key for an App Bundle or APK 5:24 Exporting encrypted key for Google Play App Signing (definitely do this if you are uploading an App Bundle) 5:56 PRO TIP: When you want to upload a new APK or Bundle to an existing App, be sure to increment the versionCode! 6:12 Overview: Publishing your app in the Google Play Console 6:53 How to set up App Signing by Google Play (strongly recommended) in the Console 7:33 A note on public SHA-1 certificates for use with Firebase and Google Services 7:51 App Release Tracks for Publishing 8:10 Setting up an Alpha release (for closed testing, meaning that only specific users may download and test the App). ALWAYS TEST YOUR DAMN APP BEFORE PUBLISHING IT PUBLICLY 9:09 Accessing the test release (it can take a long time for it to show up, so be patient) 9:37 Upgrading your Alpha Release to a Production Release (i.e. a Public Release)