How to Add Your App Inventor App to the Google Play App Store
Last fall, I created a tutorial on adding App Inventor apps to the Google Play Store. That tutorial is still worth reading and is available here.
But I heard from readers that they would like more information about the process of adding an App Inventor app to the Google Play Store. I have created this new tutorial to help with that!
Also – I will soon add videos to accompany these tutorials. Was hoping to have a couple posted today but I have run out of time until next week to get those done.
Sign Up for a Google Play Developer Account
To add apps to the Google Play store, you need a Google Developer Account. Sign up is easy but it does involve a one time (good for life) application fee of US $25.
Go to play.google.com/apps/publish to get started:
Follow the Google directions to set up your account.
Preparing Your App for the Google Play Store
Set the VersionNumber of Your App
In the Designer View, select the Screen1 component. At the bottom of Properties for Screen1, find the VersionCode and the VersionName items.
Every new version of your app must have a new VersionCode. Your first app version is 1, but if you make changes, fix defects/bug, and so on, you must increment the VersionCode value. If your first upload was 1, then your second version with the new changes must be 2, and so on. The VersionCode is always an integer number.
You know how each day Google Play alerts you that it has updated, oh, 25 apps overnight? Google Play noticsd that the VersionCode value of your apps changed in the store, and the version on your phone is now out of date, so it updates the app to the new version.
VersionName is actually a text string (unlike VersionCode which is an actual number). The VersionName can be anything you wish to use – for example, “Version A”, “1.0”, “1.1”, “1A” and so forth. This is the version field that is visible to the user of your app.
Let’s say you currently have VersionName “1.0” of your app in the store. But you have learned of some defects so you fix the problems and release a new version. You will update the VersionCode from 1 to 2, but may choose to leave the VersionName as “1.0”.
Later, you add a new, but minor feature to your app. Now, you update the VersionName to “1.1” and the VersionCode to 3.
Still later, you make major updates and add many new features. You decide to call this version 2.0. You’ll set VersionName to “2.0” and update VersionCode to 4.
Build the .apk File
Once your app has been created and tested (see below for hints on testing) its time to “Build” a “.apk” file. If you have only been developing apps using the MIT App Inventor 2 Companion or the emulator, or even if using the “Build | App (provide QR code for .apk)” menu item, you may not have done much with the .apk files.
.apk files are the “package” that gets installed on to the Android device. Think of the .apk as being similar to a Windows “.exe” file – the .apk contains the executable code and other information needed for an app to run on the Android device.
Use the Build menu option “App (save .apk to my computer)” to create the .apk file that you will submit to the Google Play apps store:
The Keystore File and Digitally Signing Your App
MIT App Inventor automatically creates a digital signature, known as a “keystore file”, that is attached to your .apk file. All apps released for Android devices must be identified with a digital signature which identifies the creator of the app. As long as you create and build your .apk files on the same Google account logged into App Inventor, you need not pay attention to the keystore file.
BUT! Each time you upload a new version, you must use the exact same keystore that was previously used for your app. Again, as long as you build your apps using the same Google account, this will not be a problem – MIT App Inventor stores the keyfile for you, automatically.
There are two situations where you may need to manually track the keystore file.
One, it is a great idea to backup the file from the MIT App Inventor servers – just in case!
Two, suppose you download the source .aia file, and then re-upload to a different Google account connected to MIT App Inventor. In your new account, MT App Inventor no longer knows anything about the original digital signature keystore file. While you can build the .apk file, and App Inventor will create a new digital signature, this new .apk file cannot be used to replace and update a previously updated app! To update an app, the new code version must include the original digital signature!
You can download a copy of the keystore file using the Projects | Export keystore menu item.
Additionally, if have created Android apps written in Java and have previously created a unique digital signature for your Java-written apps, you can re-use that keystore in App Inventor (I did!) Just import your keystore file using Import keystore.
Be sure to test your app in as many configurations and devices as you can, especially including devices with different size screens to ensure that the user interface displays properly.
Go through all of your applications features and verify that each works as intended.
Enlist friends to test your app too.
Depending on the complexity of your app, a full test may be difficult to complete. Enter text books are written about the topic of software testing; entire graduate courses are taught about software testing. Software testing is hard! Which is my way of saying that no matter how much testing you do, your app may still have some problems (officially called “defects”). Do the best you can and plan to submit revised and fixed apps later!
Once your apps is uploaded to the Google Play store you can also register to use Google’s remote Cloud testing lab to run your app remotely on test devices.
Add Your Application to the Store
In the Google Play Developer Console, click on the turquoise “+ Add new application” button at far right:
Prepare Text Descriptions for the Google Play Store
- Determine the “Title” for your app as it will appear in the Google Play store.
- Create a “short description” up to 80 characters to briefly explain what your app does.
- Then, write a “Full description” – up to 4000 characters in length.
Enter this information in the Product Details form at Google Play Developers Console:
Prepare Graphic Images for the Google Play Store
One of tougher steps is creating all the graphic images required by the Google Play store listings.
Sample Screen Shot Images
First, create a group of screen snapshots from your Android device. Depending on the version of Android you have, you’ll press a combination of buttons on the device to have Android make a “snapshot” of whatever is on the screen. On my phone, I must press the Volume- (volume down or lower) button simultaneously with press the Power On/Off button. After about one second, Android beeps and shows that it has saved a copy of what appears on the screen.
Go to the Google Photos app and look for the “Screenshots” category. Display your saved screenshot, look for the “share icon” at lower left, touch that, and then select GMail and email a copy of the screenshot to yourself.
Login to your email account on your computer and download the screenshot image to your computer.
This is the simplest way to get screenshots from your Android device over to your computer.
If you can do so, create sample screen shot images on both an Android phone and (at least) the Nexus 7 7-inch screen device. In this way, your screen shots will display their best on both phones and tablets.
To create your graphic icons, you need to use a paint or drawing program, paying special attention to the required sizes. The Hi-res icon must be exactly 512×512 pixels in size, the “Feature Graphic” must be 1024×500 pixels in size. The latter is shown in the Store listing and should say something about your app:
The Hi-res icon and the Feature Graphic are both required; the Promo Graphic and the TV Banner are optional.
Category and Content Safety
Specify the Application type, the Category and Content Rating of the apps. You will also need to fill out an online survey to obtain a content rating certificate.
Earn Money – Or Maybe Not!
You can earn money by setting a sales price for your app, or by adding features in to your app to display advertising or to sell “product add ons” for in-app purchasing. This tutorial does not address how to do any of those functions.
If your pursue this, you will also need to set up a way for Google to pay you any revenue you have earned.
Note: If you initially set your app to “Free”, it will always be free and cannot later be changed to a paid app. Note also that most Google Android apps are free and it can be difficult to get buyers to purchase a paid app on the Google Play store.
Be realistic – the overwhelming majority of Android apps do not make money nor break even for their creator. About 18 months ago, to be successful with an app basically required your app be in the top 1/2% of units downloaded in at least one of the roughly two dozen categories. I assume this is still true today. Relatively few apps outside of the top 1/2% of units downloaded make much money; most make only a little and do not break even in terms of the time it took to create the app.
E-Books and Printed Books
If you find these tutorials helpful (I hope you do!) please take a look at my books on App Inventor. To learn more about the books and where to get them (they are inexpensive) please see my App Inventor Books page.
- App Inventor 2 Introduction (Volume 1 e-book)
Step-by-step guide to easy Android programming
- App Inventor 2 Advanced Concepts (Volume 2 e-book)
Step-by-step guide to Advanced features including TinyDB
- App Inventor 2 Databases and Files (Volume 3 e-book)
Step-by-step TinyDB, TinyWebDB, Fusion Tables and Files
- App Inventor 2 Graphics, Animation and Charts (Volume 4 e-book)
Step-by-step guide to graphics, animation and charts
Thank you for visiting! — Ed