Table, td{
border: .5px Strong black;

Instant programs required creating a characteristic module that acted as the base module. This foundation feature module contained the shared code and tools to program and your instant. The rest of your codebase was included of:

  • multiple non-base contain modules, which contained the instantaneous app entry points,
  • a program module, which contained the code and activities required only to your primary installed application, and
  • an instantaneous app module, which represented the instant app and mapped its own dependencies.

    By migrating your instant app to an app package with attributes, you will be prepared to leverage the power of this new paradigm and you’ll have the ability to simplify the modular layout of your app.

    The migration

    Dist:instant=”…”
    dist:onDemand=”…”…

dist:instantaneous ="false" dist:instant="true"
dist:onDemand="false" Dynamic feature delivered in install time Dynamic feature delivered immediately and at install time
dist:onDemand="true" Dynamic feature delivered on demand (beta) N/A

Last year, we introduced Android Program Packages –a brand new way to construct and release your own Android apps. App bundles simplify delivering optimized APKs, such as delivery, by uploads. Google Play manages distribution by serving the right APKs to your own instant and installed app users–this is named Dynamic Delivery. To find out more about app packages, take a look at the documentation website .

Posted by Miguel Montemayor and Diana García Ríos

As of Android Gradle plugin 3.4.0 (included in Android Studio 3.4), we are beginning the deprecation process of the feature plugin (com.android.feature) and instantaneous program plugin (com.android.instantapp) as a means to build your instant app. When building your program, you’ll receive a warning flagging com.android.feature as deprecated. When you’ve got an existing instant program built with the feature plugin, migrate your existing app to a instant-enabled app bundle when possible.

What is changing?

With the new app package implementation, your foundation attribute module takes the role as your program module (com.android.application), hosting the code and tools common to all attributes (instant and set up ). You arrange additional, modular features as one of three kinds of dynamic attribute modules, dependent on when you wish to send them to the consumer. The instantaneous app module disappears, since the dist:instantaneous features in the demo are enough to identify which features will be included as part of their instantaneous experience.

Dynamic Delivery relies on the notion of shipping dynamic attributes (com.android.dynamic-feature) to program users whenever they need them and only as long as they want them. There are now three delivery kinds, based on the different values you’ll give the dist:module tag attributes on the lively feature module’s manifest file:

If you do not have an instant experience added to your program and you’d like to make one, then use Android Studio 3.3+ to create an instant-enabled app package .