How useful did you find this site post?
In Android Studio 3.3, we introduced a way to build app packages that contain both the standard, installed version of your program in Addition to a Google Play Immediate experience for modules marked using all the
dist:instantaneous "true" attribute inside their
Please note that while the extra languages API is currently available to all programmers, on demand modules have a closed beta for now. You can experiment with on demand modules on your open, and closed test tracks, while we work together with our partners.
Val langs: Establish = splitInstallManager.installedLanguages
Requesting additional languages
Requesting another language resembles requesting an on demand module.
Read more about the new flow.
Posted by Wojtek Kaliciński, Developer Advocate, Android
Val splitInstallManager = SplitInstallManagerFactory.create(context)
Opt in to program signing by Google Play
- A new additional languages install API, which affirms in-app language pickers
- A compact publishing procedure for instant-enabled app packages
- A new registration Choice for app signing by Google Play
- the Capability to permanently uninstall dynamic feature modules that are included in your program's first install
Additional languages API
Get a list of installed languagesWe hope you enjoy these improvements and test them out. Continue to share your comments as we work to make these features more useful! This opens new possibilities for programmers to reduce the program size that is installed. For example, you can now uninstall a hefty sign-up module or some onboarding content once the consumer completes it. It is possible to reinstall it with the standard demand modules install API if the user navigates into a section of your program that has been uninstalled. ★ ★ ★ ★ ★
Permanent uninstallation of set up time modulesYou need to allow gain from Dynamic Delivery optimizations and automatically app signing by Google Play to publish your app using an Android App Bundle. It's also a more secure method to deal with your signing key, which we recommend to everybody, even in the event that you would like to keep regular APKs for now. We have now added the ability to permanently uninstall dynamic attribute modules which are included on the initial install of your app. Now without having to upload a self-signed artifact 18, programmers can explicitly decide to upload their current key. You can even choose to start with a key so that the key used to register your app bundle can become your key, generated by Google Play. Together with the languages API, programs can now request the Play Store start using it and immediately to set up tools to get a new language configuration on demand. Up until today, programmers were required to utilize product tastes so as to construct two app bundles and upload both to Play Though you may use one project to create the instantaneous and installed versions of your program. When you adopt the Android App Bundle as the format to your app, Google Play is able to maximize the setup by providing. If a user changes the system locale following the app is set up, Play automatically downloads the tools. This past year, we launched Android App Packages and Google Play's Dynamic Delivery to introduce modular development, decrease app size and streamline the release procedure. Since that time, we have seen this app model is quickly adopted by programmers in over 60,000 production apps. We've been excited to see programmers experience significant program size savings and reductions in the time required to manage each release, and have documented these benefits in case studies with Duolingo and redBus. Once you construct an app package, upload it on the Play Console, and you will have the ability to select it when creating a brand new app launch that is instant. This suggests that the installed and instant versions of your app need. The module will be uninstalled, even when the app is updated. ...
Please be aware there has been an API change in a the latest Play Core launch, which means you should use the newest
SplitInstallManager#startConfirmationDialogForResult() together with
Activity#onActivityResult(). The former process of using
startIntentSender() was deprecated.
Have a look at the updated Play Core Library documentation to learn more about the best way best to access the newly installed language tools in your own activity.
Some programmers choose to decouple the display language of the app from the system locale by adding an language switcher. With the most recent release of the Play Core library (version 1.4.0), we are introducing a new added languages API that makes it possible to construct in-app language pickers while keeping the full benefits of smaller installs provided by using app bundles.
We have also updated our dynamic features sample on GitHub together with the additional languages API, such as how to store your user’s language preference and use it to your actions at startup.
Based on your comments, we have revamped the sign-up flow for new programs to make it simpler to initialize the key for registering your app that you would like to use.
We are happy to announce that we have removed this limitation. It’s now possible to upload a unified app package artifact, containing modules allowed for the experience that is instantaneous. This operation is available for everybody.
The app may also track install success with callbacks and track the download condition using a listener, just like when requesting an on demand module.
Thank you to everyone who took the time to give us feedback on our launch. We are always open to fresh thoughts, and we’re Delighted to announce some new improvements based on your suggestions now:
Instant-enabled Program Bundle