The app must be completed. Push notifications must be completed before building the app and you must have image assets ready (see the Google Play section in this article).
Publishing on the Google Play Store will provide your app with more exposure to potential users. However, publishing on the Google Play Store will make your app publicly available, so it should not be used for internal apps.
To launch your app to the Google Play store you will need to:
- Complete the app details section
- Complete the app analytics and push notifications section (optional)
- Request that the app be published
- Set up push notifications
- Complete steps in the Google Play Console
- Complete the store listing section
- Submit your app for review
- Data safety
Watch this short video or read the article below.
Step 1 – Complete the app details section
Note: At any point in the process, you can select the blue “Save Progress” button in the bottom left to save your work.
Go to the Publish section of your app in Fliplet Studio.
Under “Choose a Publishing Channel”, click on the blue “Select” link next to “Publish to Android devices”.
Scroll down and select the “Google Play” Tab.
Underneath where it says “Let us build your app”, click on the first tab that says “App details”.
Type the “App icon name”. This is the name you would like to appear on a device.
Change the “App icon” or “Splash screen” image by clicking on the blue “Change” text underneath them. Both the App icon and Splash screen are required. (Information about requirements for image sizes can be found here.)
To generate screenshots, you can useFliplet’s screenshot generator. Select “App settings”, “launch assets” to do this. In a later step, you will download them from Fliplet and upload them to the Google Play Console.
Return to the publish section. Do not change the App version number and App version code. Also do not change the Bundle ID. It is not recommended to change these values. Fliplet will automatically produce values so you don’t need to do anything.
Step 2 – Complete the app analytics & push notifications section (optional)
Click on the “App analytics & push notifications” tab.
Fliplet Analytics is enabled by default. To learn more about Fliplet Analytics, click the blue text or read the article here.
To add push notifications or enable Google Analytics, click on the blue text that reads “Learn more about Firebase” under the “Google Firebase & Push Notifications” heading or read the article here.
To save your work click the “Save Progress” button in the bottom left.
Step 3 – Request that the app be published
Click the green “Request App” button in the bottom right to request the app to be published.
Then click “OK”.This process can take a few minutes to up to an hour to finish.
Check the progress of the process by scrolling to the top of the “Publish to Android devices” window where you are currently.
- When it’s complete, return to the window, download the app file, and add it to the Google Play Console.
Step 4 – Set up push notifications
For a reference on how to set up push notifications, click here.
Step 5 – Complete steps in the Google Play Console
Move from Fliplet to Google Play Console
Login to Google Play Console with your Google Developer account details. The screen should display all of the apps that you have published. For more information on how to make a Google Developer account click here.
Click the blue “Create App” button.
Provide a title for your app
Select the default language
- Select whether this will be an app or game
- Select free or paid
- Add an email address that Play Store users can use to contact you about this application.
- Confirm that your app meets policies by reading ticking the declarations
- Select “Create app”
Step 6 – Complete the store listing section
After you create your app, you can start setting it up. Your app’s dashboard will guide you through all the most important steps to get your app available on Google Play.
- If parts of your app are restricted based on login credentials, memberships, location, or other forms of authentication, you will need to provide instructions on how to access them. Make sure that this information is kept up to date.
- Select either – All functionality is available without special access or All or some functionality is restricted
- Enter Instructions – enter your test login credentials to allow the reviewer access to your app
Does your app contain ads
- Select yes or no depending on whether your app contains no and save.
- Enter your contact email
- Select the relevant category for your app
Next confirm whether or not your app includes “violence”, “sexuality”, offensive “language” or “controlled substance” references.
After you complete and save the questionnaire Google will populate your rating for different countries.
Target Audience and content
- Choose the target audience for your app
- Select to confirm whether your app appeals to children
- Confirm whether your app is a news app
- If yes – Provide information to help Google verify your credentials as a news publisher. You will be asked to explain how you source the news content that is shown in your app.
- Select the apps category and add any tags
- Add your store listing contact details, note that this information will be shown to users on Google Play
Main store listing
- Select “Main store listing” from the left hand side menu
- Fill out the “App Name”, “Short description”, and “Full description” for your app.
- Click to add a 512×512 pixel image of your app icon.
- Scroll down to add a 1024×500 pixel image as your “Feature graphic”.
- If you have a video to promote your app you can add an optional youtube URL
- Scroll down to add screenshots of your app. If you used Fliplet to generate screenshots for you, find them in the File Manager under the “Screenshots Google” folder.
- Add at least two screenshots for phone and tablet.
Step 7 – Submit your app for review
Once your app is set up you can follow the set of steps under the Release your app section, to submit your app for review.
- Choose countries and regions for release
- Accept the Play app signing terms of service
- Add your app bundle (.AAB file)
- Finally, click “Start roll-out to production”. This will only work if you have completed all the necessary steps. Your app will be submitted to Google for review. This process can take several days.
Check the status of your app by going to the “Dashboard” of Google Play Console. Your app will say “Published” when it is live.
Step 8 – Data Safety
In 2021 Google announced that app developers will be required to tell them about their app’s privacy and security practices by completing a form in the Google Play Console, this section is currently available for developers to declare this information.
The app privacy section will be visible to the end-user from February 2022 and by April 2022 all of the published apps on the Google Play store will need to have declared their data safety.
This information will be shown on the store listing to help Google Play users understand how app developers collect and share user data before they download their app.
More information can be found on the following Google support article.
Before proceeding we would recommend you prepare the following:
- Reading and understanding the requirements for completing the Data safety form in the Google Play console.
- Review how your app collects and shares user data and the app’s security practices.
- Review how any third-party code (such as data libraries and SDKs) is compliant with the Google Play Developer program policies. Fliplet complies with the Google policies.
After publishing your app
- Once the app has been published to the Google Play Store, the Data Safety form can be found on the Google Developer Console, on the left side select Policy > App content > Data safety.
- Under Data safety click Manage.
- Make sure you read the instructions on the Overview screen carefully and ensure you have everything ready to complete the Data safety form.
- If you don’t have all the information available from the start, you can click Save as Draft at the bottom of the page to save your progress and return to it at a later date.
Data collection and security
- These will be Yes or No questions.
- To answer the first question please ensure you understand the different user data types, Google has compiled a list of Data Types in this article.
- If you selected Yes, then you will need to answer two follow up questions.
- On the second question “Is all of the user data collected by your app encrypted in transit?”
- Encryption protects data you send, receive, and store in your app using a process that scrambles readable text so it can only be read by the person who has the secret code, or decryption key. It helps provide data security for sensitive information.
- Please note that with Fliplet’s default functionality, all of the user data collected by Fliplet apps is encrypted in transit. If your app has added any custom code to implement a different behavior, then you need to make Google aware.
- On the third and final question, whether there is a way for users to request their data to be deleted depends on how the app is built. For example, if there is a specific screen to request this data.
- Fliplet provides all the necessary tools, but this feature may or may not be built into the app.
- In the data types section, select all of the user data types collected or shared by your app. When you’re finished, select Next to move on to the next section.
- For most apps, the following will likely always be collected and need to be checked off: Name, Email, Phone Number, Analytics, App Functionality.
- More detail on these data types is included in this article.
- Certain data types, for example, the location, is not collected by default unless this feature is used through adding custom code.
- The data types in this section include:
- Personal info – Name, email address, phone number
- Financial info – Purchase history, credit card
- Health and fitness – Information about users’ exercise routines or eating habits
- Messages – For example emails, SMS, or in-app messages
- Photos and videos
- Audio files
- Files and docs
- App activity – Page views and taps, search history – Please note, Fliplet analytics will collect page views and taps for as long as you have the app, you can see this data on the app analytics section on Fliplet Studio
- Web browsing
- App info and performance – crash logs, diagnostics
- Device or other identifiers – IMEI number, MAC address, Widevine device ID, Firebase installation ID or advertising identifier.
- Please note, by default Fliplet apps collect an analytics ID to be used in the organization dashboard and app analytics.
- Once all the data types have been selected click Next.
Data Usage and Handling
- In this section, you will need to answer questions about how the data is used and handled for each user data type that the app collects or shares.
- Next to each user data type, on the right side of the screen there is a show option, click on this and click start and this opens an overlay with the options to fill in
- You will need to tick the relevant boxes on each data type used on the app to select if the data is collected, shared, or both.
- This will open a detailed view where you can answer questions about how this data is processed, for example, is this data processed temporarily, is this data collection required or users can choose if they want to share their data.
A note on the question: Is this data processed ephemerally? Processed ‘ephemerally’ means that the data is only stored in memory, retained for no longer than necessary to service the specific request in real-time, and not used for any other purpose.
- Once this is done, click next to continue.
- Once all the questions have been answered, the Store Listing preview section shows a preview of the information that will be shown to users on Google Play based on the form answers provided.
- This is where you can review if all the information you have entered is correct, once you do click Save.
- In case you want to make any changes you can always access this form again from the Google Developer Console > Policy > App content > Data safety.