Create Signed Ordered with airSlate SignNow

Generate phone release

what's up everybody this is Ryan here and in this video I'm going to walk you through the steps necessary to prepare upload and publish an android application to the Google Play Store here's what you'll need in order to follow along with this tutorial a developer account with Google Play an Android application with a unique package name and I'll be using android studio ide version 3.5 point 2 here I do strongly recommend you use version 3 or higher also please note that I will be focusing on the technical process of preparing signing uploading and publishing an alpha test version of the application as well as a full release in other words I won't be going into much detail on store presence SEO and that kind of thing which really warrants its own tutorial now there's a lot of different steps so if you want a list of topics and timestamps check the description box down below and hit that like button while you're down there in the first part of this tutorial we'll look at preparing an app for upload to Google Play this involves enabling our 8 or ProGuard on earlier versions of Android studio 4 code minification then we'll create a key store and a signing key and finally we will create a signed app bundle or apk more on that later every Android application has a package ID located in its Android manifest file the purpose of this package ID is to allow platforms like Google Play to uniquely identify your app this ID must be unique and every apk that you upload to update a given application on the Google Play Store must have the same package ID otherwise you will have to re-upload a completely new application and you will lose all of your ratings and installs until quite recently we used a tool called ProGuard to shrink and obfuscate our code before uploading it to the Play Store obfuscation means to change the names of the classes fields and functions of the application into shorter obscure versions this will help to make your application smaller and it will also make it more difficult to reverse engineer your code but by no means does it make that process impossible alright we'll do lots of other kinds of optimation x' like removing unused code which will result in a smaller apk file which makes everybody happy now this is slightly confusing but assuming you're using a recent version of Android studio it now uses r8 instead of ProGuard to enable r8 or ProGuard in older versions of the Android Gradle plugin admin if I enabled equals true to your build configuration note that while r8 is different from ProGuard it is still capable of interpreting any ProGuard rules that you add to the ProGuard rules dot profile which sits in your module level app directory I don't have time to go into detail on adding specific rules to this file here but...