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.
-
PackageManager cannot 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
instant flag 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.
Development of Widgets, App Clips, and Live Activities: Entry Points Outside the App
We understand that users see your app not only when they open it. A widget on the home screen, a live score in Dynamic Island, a mini experience without installation — these are separate entry points that we implement within platform constraints. Over 5 years, we have developed more than 50 extensions for mobile apps, from simple informational widgets to App Clips with payment scenarios, saving clients up to 30% of time on repeat visits.
What entry points should you consider for your app?
WidgetKit Widget Development: Why You Can't Just "Add a Widget"
WidgetKit works via a Timeline Provider — the widget doesn't stay in memory continuously; it requests data snapshots in advance. The most common mistake: developers try to show real-time data via URLSession directly from getTimeline(). Apple doesn't prohibit this, but with aggressive updates, the system starts throttling requests, and the widget gets stuck on outdated data.
The correct approach: the main app updates data via WidgetCenter.shared.reloadTimelines(ofKind:) — after receiving a push notification or when the user returns to the foreground. The widget reads data from a shared App Group container using UserDefaults(suiteName:) or file storage. No direct network requests in the provider in production.
In the latest iOS versions, AppIntent-based interactive widgets have emerged — buttons and toggles directly on the widget without opening the app. This is implemented via Button(intent:) in the SwiftUI widget layout. Only works for simple actions; complex logic should transition to the app via widgetURL.
How Live Activities Change User Experience?
Live Activities are a mechanism for displaying live data on the Lock Screen and Dynamic Island (iPhone 14 Pro+). They are launched via ActivityKit, updated via push notifications of type liveactivity with a payload up to 4KB.
Architecturally, it's a separate SwiftUI target with two views: compact (Dynamic Island) and expanded (Lock Screen). Data is passed via ActivityAttributes — a strictly typed structure. The dynamic part is ContentState, while the static part (unchanged during the activity) is directly in ActivityAttributes.
A typical issue: Live Activity doesn't update on the device even though push is sent. The reason is that the app doesn't have permission for background push or apns-push-type is set incorrectly. In production, you need apns-push-type: liveactivity and a token from activity.pushToken. According to Apple documentation, without a correct push token, the Activity won't receive updates.
When to Use App Clips vs Instant Apps?
App Clips (iOS) and Instant Apps (Android) solve a similar problem — provide functionality without installing the full app. But the implementation is fundamentally different.
App Clip is a separate target in Xcode, max 15MB, launched via NFC tag, QR code, Safari Smart App Banner, or a link in Messages. Data access is limited: no Keychain sharing with the main app without explicit setup, no access to HealthKit, no push notifications (only ephemeral). The App Clip Card is configured in App Store Connect, and metadata errors are a common reason for rejection.
Android Instant Apps are built on a modular architecture: the app is divided into feature modules, each of which can be downloaded separately via Play Feature Delivery. An Instant App is a feature module with <dist:module dist:instant="true">. The limitation is no more than 15MB total for instant delivery.
Comparison shows that App Clips win in payment scenarios due to Apple Pay integration — conversion is 20% higher compared to Instant Apps in similar cases. Instant Apps are better suited for game demos and services requiring quick access via Google Search.
| Parameter |
App Clips |
Instant Apps |
| Max size |
15 MB |
15 MB |
| Launch triggers |
NFC, QR, URL, Safari |
URL, Google Search, Play Store |
| Shared Keychain |
Via App Group |
Via SharedPreferences/Keystore |
| Recommended scenario |
Payment, boarding, demo |
Game demo, one-time services |
What Does Our Work Include?
-
Audit of current architecture: determine which entry points your app needs — widget, Live Activity, App Clip, Instant App.
-
Prototyping: visual model of the extension following platform guidelines (Apple HIG, Material Design).
-
Development: implementation in Swift (iOS) or Kotlin (Android) using WidgetKit, ActivityKit, App Clip API, Play Feature Delivery.
-
Integration: setting up App Group, Keychain sharing, push certificates, provisioning profiles.
-
Testing: on real devices (iPhone, iPad, Android) and simulators. For Live Activities, test via
xcrun simctl push.
-
Publication: preparing metadata for App Store Connect (App Clip Card) and Google Play Console (Instant App configuration).
-
Documentation and training: architecture description, widget update instructions, push notification troubleshooting.
How Does Our Development Process Work?
-
Analytics: which app features are truly needed outside the app, and which mechanism fits. Widget for forecast — WidgetKit. Real-time delivery tracking — Live Activity. Payment at checkout — App Clip.
-
Design: choosing stack, data update schemes (Timeline, push), UI layouts for compact and expanded views.
-
Implementation: writing code in Swift/Kotlin, configuring App Group, push certificates, test schemes.
-
Testing: each extension is tested in isolation. WidgetKit rendering is verified via Xcode Widget Gallery, Live Activities via simulator with forced push.
-
Deployment: publishing to stores, monitoring metrics (update frequency, App Clip launch count).
Estimated Timeframes
| Extension Type |
Timeframe (business days) |
| Simple informational widget |
5 to 10 |
| Interactive widget (AppIntent) |
10 to 15 |
| Live Activity with push |
10 to 20 |
| App Clip with payment |
20 to 30 |
| Instant App (Android) |
15 to 25 |
Cost is calculated individually after audit. An estimate is provided within 2 business days.
What Are Typical Mistakes in Extension Development?
-
Too frequent widget updates — leads to throttling and empty state. We recommend an interval of at least 15 minutes (see Apple Human Interface Guidelines in WidgetKit documentation).
-
Ignoring shared container — the widget doesn't see data because it uses its own
UserDefaults instead of App Group.
-
Lack of fallback for Live Activities — if push isn't delivered, the user sees outdated data. A periodic polling mechanism via
Activity.update with pushType: nil is needed.
-
Incorrect App Clip Card metadata — a common reason for rejection in App Store Review. For example, incorrect URL or missing icon.
Contact us to assess which extension fits your app. Order an audit of current entry points — we'll find non-obvious scenarios for widgets and App Clips. Get an engineer consultation on architecture today.
