Expansion files do support a so called patch version[0] - which may sound like a delta but it isn't. The job of creating a patch and merging it with the main ex

Expansion files do support a so called patch version[0] - which may sound like a delta but it isn't. The job of creating a patch and merging it with the main expansion file is placed on the app developer. Additionally there can only be one patch to each main extension file. There is not a new delta generated for each new version of the expansion file. I'm not at all surprised if most developers just ignores the patch option all together and just re-uploads a new main expansion file every time any content has changed. Besides, while seemingly well documented[0], IME expansion files requires quite a lot of undocumented magic. Including patching Google's own source code. Code that they recommend that you vendor into the app rather than include as a library. Further the user experience is less than stellar. On many devices the expansion is only downloaded after the app is started the first time. So the app needs to work even while the file is missing, and at that time manually request that the system retrieves the file. BTW, did anyone notice the fine print of this announcement? Only devices with Android 4.0 or newer supports 100 MB apk:s. If your app supports 2.3 - i.e. some 70 million Android users - you're stuck at 50 MB and will have to keep using expansion files to serve those users. [0] https://developer.android.com/google/play/expansion-files.html https://developer.android.com/google/play/expansion-files.ht...