A user sees a link to your product on social media, clicks it — and within seconds a native app screen opens. No installation required. Imagine: a user sees an ad for sneakers, clicks — and instantly a catalog with one-click purchase capability appears. The loading time of an Instant App is 10 times less than that of a full app. This is Android Instant Apps — a Google Play Instant technology. However, behind the apparent simplicity lies a strict modular architecture, module size limits (15 MB on Android 8+, 4 MB on older versions), and a number of system constraints. We, a team with 5+ years of experience and over 50 completed mobile development projects, help implement Instant Apps without the typical pitfalls.
How Instant Apps Solves the Install Conversion Problem
Google Play Instant reduces friction: the user immediately sees the value of the app and is more likely to install the full version. To achieve this, the app is split into modules — Feature Modules. The module for the Instant scenario is flagged with <dist:module dist:instant="true"/> in the manifest. The size of such a module is limited: 15 MB for Android 8.0+ and 4 MB for older versions. If the app is a monolith, modularization is required first. According to statistics, 90% of users who interacted with an Instant Experience install the full app within a week. In comparison, the typical conversion from a store rarely exceeds 3-5%.
| Characteristic | Regular App | Instant App |
|---|---|---|
| Launch method | Install from store | Via URL, no installation |
| Size on device | Full APK | Only loaded module |
| Permissions | All requested | Only risk-free |
| State | Persisted | Only via Cookie API |
| Install conversion | Low (friction) | High (instant launch) |
What Restrictions Does Google Play Instant Impose?
Google Play Instant strictly limits Instant modules:
- High-risk permissions are prohibited:
BLUETOOTH,READ_CONTACTS,WRITE_EXTERNAL_STORAGE, and others. - Background components are unavailable:
Service,BroadcastReceiver,ContentProvider. -
PackageManagercannot see other apps (on Android 11+ this restriction also applies to regular apps via visibility filtering).
The key UX task is state transfer during installation. The user filled out a form in the Instant Experience, clicked "Install" — the data must be preserved. The mechanism: InstantApps.showInstallPrompt() with Cookie API (InstantApps.getInstantAppCookie()/setInstantAppCookie()). The cookie size is limited to PackageManager.getInstantAppCookieMaxBytes() bytes (typically 16 KB). Google Play Instant documentation recommends not exceeding 8 KB for compatibility.
Typical Mistakes When Using Cookie API
- Writing to the cookie after calling showInstallPrompt() — data is not saved.
- Exceeding the cookie limit — writes are ignored.
- Using SharedPreferences instead of Cookie API — data is lost after installation.
Why Modularization Is a Key Step in Implementing Instant Apps?
A monolithic app cannot be split into Instant modules without prior modularization. A Feature Module must contain only the code necessary for the specific scenario. If the module is not isolated, its size will exceed the limit, and the Instant App will not launch. Therefore, we start with an architecture audit and propose a refactoring plan.
How Instant App Development Proceeds?
The process includes five stages:
- Architecture audit. We assess whether modules can be extracted for Instant or if full modularization is needed.
- Module design. We create Feature Modules, configure URL mapping via App Links.
- Implementation. We write the code for the Instant module, implement state transfer, and adapt the UI for instant launch.
- Testing. We use Android Studio (Run → Deploy → Instant App) and Google Play Console with internal testing track. CI/CD: separate bundle target
./gradlew :feature-instant:bundleRelease. - Deployment. We upload the Instant module to Google Play with the
instantflag and configure target URLs.
| Stage | Duration (if app is modular) | Duration (monolith + modularization) |
|---|---|---|
| Audit and design | 1–2 weeks | 2–4 weeks |
| Implementation | 1–2 weeks | 3–6 weeks |
| Testing and deployment | 1–2 weeks | 2–4 weeks |
| Total | 3–5 weeks | 8–16 weeks |
What's Included in the Work?
- Audit of current architecture and modularization plan proposal.
- Development of Instant Experience for one or more scenarios.
- Configuration of URL mapping and Deep Links (Universal Links for Android).
- Implementation of state transfer via Cookie API.
- Integration with Firebase for analytics and crash reporting.
- Testing on real devices.
- Publication in Google Play Console.
- Documentation and training for your team.
- Warranty support after launch.
Our clients save up to 60% of their user acquisition budget after implementing Instant Apps.
Timelines and Cost
If the app is already modular, an Instant Experience for one scenario will take 3 to 5 weeks. For a monolith with subsequent modularization, it will take 8 to 16 weeks. Exact timelines are determined after a free audit. Contact us — we will calculate the cost within 1 day. Get a consultation: we will evaluate your project for free.