The quality of your instant experience can influence the long-term success of your app or game in terms of installs, pre-registrations, growth, and user retention. Before making your instant experience available, it's important to make sure that the instant experience meets users' basic expectations.
This document helps you understand the quality level, feature set, and UX that your instant experience should attain to be successful. Each focus area presents a checklist of minimum requirements, best practices, and good-to-have enhancements. In the interest of delivering the best possible experience to your users, follow each checklist requirement, and follow the checklist recommendations to the greatest extent possible.
Note: To help prioritize your development efforts, take note of the level of importance indicated for each checklist item:
- Required. Minimum requirements that must be implemented for your instant experience to be considered compatible with Google Play Instant.
- Best practice. Strongly recommended implementation guidelines.
- Good to have. Suggested guidelines to help you create a distinctive user experience.
Instant app total download size
|1.1||Required||Your instant app's total download size to individual devices (ex: arm64) must be less than or equal to 15 MB. This is enforced during upload of your App Bundle. You can estimate your app download size by using the bundle tool to generate a device specific APK and then brotli compress it using the highest compression level (e.g. `--quality 11`).|
|1.2||Required||The instant app must not consume more than 150 MB of storage space on the device.|
|1.3||Best practice||When uncached, users should be able to engage with your instant experience in less than 15 seconds over an LTE or 4G connection.|
App installation or pre-registration
Note that in-game installation buttons are not allowed for the Instant play experience in the Play Games app.
When offering installation or pre-registration, you must display a clearly marked installation or pre-registration button that initiates installation and pre-registration, respectively, in at least one of the following ways:
Your instant app call-to-action (CTA) button should use the label Install or Pre-register.
Users might not understand standalone icons that represent installation or pre-registration if these icons are unaccompanied by clear labels.
|3.1||Required||Don't disable support for the Android back button. Users must be able to move backward through the history of screens that they've previously visited.|
|3.2||Required||Users must be able to exit the instant experience in 2 clicks or fewer.|
|3.3||Good to have||Provide a confirmation prompt to the user when they click the back button with clear Cancel and Exit options. The Cancel option can return users to the instant experience, and the Exit option can return users to screen they visited before entering your instant experience.|
|4.1||Required||During your instant experience, use only unobtrusive banner ads. Don't use any other type of ad, especially full-page interstitial ads, that would interrupt the experience.|
|4.2||Required||Ads must not be disguised as in-app components or elements of menu/app navigation.|
If your instant app offers in-app purchases, your instant experience must support the transfer of in-app items to the installed app.
|5.2||Required||Users must not be required to make an in-app purchase before being able to engage with your instant experience. This requirement also applies to the full, installed version of your app or game.|