3 ms·
While having to use either a custom installer, or if you don't trust any third party app [1] alternatively using ADB (or possibly the package manager directly i
by iggldiggl 5y ago
While having to use either a custom installer, or if you don't trust any third party app [1] alternatively using ADB (or possibly the package manager directly if you have root) to install split APKs, is somewhat of a hassle [2], the more annoying part is that grabbing an APK from a random device is no longer enough to cover all screen densities, languages and whatever other criteria Google uses to split APKs [3], so good luck finding an older APK version if you're using some exotic screen density or (more likely) language.
Curiously enough by the way, Google themselves only recently added a feature to the Play Store which officially allows directly sharing (free) apps with nearby devices. I wonder how that is supposed to work going forward when app bundles will become more and more widespread – can you then only share apps with somebody having the same screen density and language setting?
Or can apps at least still fall back to dynamically using the assets for whatever language/screen density was available just like they would today with a monolithic APK?
[1] As a perhaps more trustworthy alternative, there's SAI on FDroid (https://f-droid.org/de/packages/com.aefyr.sai.fdroid/ https://f-droid.org/de/packages/com.aefyr.sai.fdroid/), which a quick search indicates that it might be able to read and install APKMirror's bundle format, too.
[2] Also the fact that it makes Titanium Backup semi-useless for those apps, even though in other respects I still like it better than any of the other alternative backup apps I've tried.
[3] CPU architecture at least, although there's less variation there because almost everything will be either 32- or 64-bit ARM, and even before App Bundles some apps would already ship separate APKs for different CPU architectures.