About Dynamite Modules

DeletedUser88

When an app displays a map based on Google Maps from Play Service, is this an example of a dynamite module? If so, how will these apps handle maps after they are depreciated? Also do we know when Google will fully depreciate dynamite modules?

GrapheneOS

DeletedUser88 They're not being deprecated but rather the legacy approach of them being stored in the Play services app data directory is being replaced by split APKs. We had to deal with the legacy approach as part of the sandboxed Google Play compatibility layer since it was designed to depend on having custom SELinux MAC and MLS policy for Google Play services. We dealt with it by essentially proxying access to it and sending along a file descriptor.

DeletedUser88

GrapheneOS They're not being deprecated but rather the legacy approach of them being stored in the Play services app data directory is being replaced by split APKs.

I see. So assuming maps displayed from Play Services are a dynamite module (still not sure if this is the case or not), apps will now have to include a "maps apk" as part of their Split-APK? Also can you give an example of common dynamite module functionality that apps use so I can better understand the situation?

Carlos-Anso

An app displaying google maps is it requesting map data and using that.

Dynamite modules and Play Feature Delivery are extra parts of the app that are not included in the initial installation.

The newer method is extra split apk parts downloaded and added as the app requires them.

https://developer.android.com/guide/playcore/feature-delivery