Google Play Instant for Android: Setup Guide
A user taps 'Install' on your Android app ad. The APK is 75 MB. They wait 3 seconds and leave. Google Play Instant breaks this pattern: instant demo launch without download, size limit 15 MB. In practice, conversion to full install after a trial run reaches up to 90%, and CPA drops by 30% — saving up to 40% on ad campaigns. Our Android team (10+ years of experience) has implemented instant solutions for 50+ projects — in e-commerce, cost per lead decreases by 25%.
An instant app is a dedicated module of an Android App Bundle. It launches via URL or 'Try Now' button in Google Play. Scenarios: game demo level, onboarding, product view via deep link. Technically it's the same APK but in a sandbox: restricted API access, temporary storage, size cap.
Why Instant Apps Matter for Conversion Growth
Install rate after trial run: up to 90%. Time to first interaction: seconds. CPA drops by 30% (average cost of acquisition decreases by 30% based on our project data). Retention increases by 20% due to instant value delivery. According to the Google Play Instant documentation, instant apps increase conversion by 20–30%.
Technical Limitations of Instant Apps
Instant experience size is strictly 15 MB. All resources, fonts, libraries must fit into this limit. Android App Bundle with dynamic feature modules (dynamic-feature) allows cutting only what's needed. In one project, we shrunk a module from 28 MB to 11 MB — replaced heavy SDKs with lightweight alternatives and enabled R8 with isShrinkResources = true.
API restrictions: the instant version lives in a sandbox. Unavailable: READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, contacts access, SMS, persistent notifications. Bluetooth, camera, microphone work with permissions. Add INSTANT_APPS_ACCESS to the instant module manifest.
Storage: SharedPreferences are temporary and get cleared. To persist data between instant and installed versions, use the Cookie API — a 16 KB buffer for state transfer upon installation. Without it, the user loses onboarding progress.
Comparison: Instant vs Installed Version
| Feature | Instant Version | Full Install |
|---|---|---|
| Size | up to 15 MB | any |
| Storage access | no | full |
| Persistent notifications | no | yes |
| Data persistence | temporary | permanent |
| Launch | no installation required | installation mandatory |
How to Avoid Common Integration Mistakes
Size 15 MB. apkanalyzer analysis often reveals unoptimized drawables (webp instead of png), fonts (only needed weights via downloadable fonts), large libraries. ProGuard/R8 with isMinifyEnabled = true and isShrinkResources = true are mandatory. In one case, we reduced a module from 20 MB to 12 MB by replacing Google Maps SDK with Static Maps API via ImageView. 40% volume saving.
Navigation. Instant app launches via URL. If navigation relies on internal IDs instead of deep links, rework is needed. NavDeepLinkBuilder in Navigation Component simplifies but requires a URL for each instant experience screen.
Testing. Instant app launches from Android Studio using a configuration with Launch: Instant App URL. On device, enable 'Google Play Instant' in Developer Options. Without real device testing, sandbox limitations are hard to catch.
Cookie API for state transfer. If a user completes onboarding in the instant app then installs — without Cookie API, progress is lost. Implementation: in the instant app, write via InstantApps.setInstantAppCookie(), on first launch of installed app read via InstantApps.getInstantAppCookie().
Common Errors and Solutions
| Error | Solution |
|---|---|
| Module size exceeds 15 MB | Use R8 shrink, webp, downloadable fonts, replace heavy SDKs |
| No deep links for screens | Add NavDeepLinkBuilder or handle URL in each screen |
| Data loss after installation | Implement Cookie API for state transfer |
| Instant app doesn't launch on device | Check Developer Options settings and instant module signature |
Our Process
- Analytics — determine which functionality to expose in instant, measure size.
- Design — modularization, deep link setup, cookie strategy selection.
- Implementation — code, ProGuard/R8, resource optimization.
- Testing — on real devices, verify sandbox constraints.
- Deployment — publish in Play Console, configure 'Try Now' button.
What's Included
- Architecture documentation for the instant module.
- Configuration of
dist:instant="true"for feature modules. - Cookie API integration.
- Size optimization (R8, webp, downloadable fonts).
- Testing on devices with different Android versions.
- 30-day support guarantee after delivery.
Timeline Estimates
For a modular app: 3–5 days. Monolithic apps require prior modularization (2 weeks+). Pricing is determined after analysis — contact us to evaluate your project.
Order a free audit of your app's instant readiness — we'll assess modularity and size. Get a consultation from our engineer.