Thanks for your reply! Since play services cant be a dependency do you have to add something to replace it's functionality that increases the app size in f-droid compared to play store?
Depends on the actual NEED. There are 3-4 common paths that we see: 1. Remove the NEED, maybe it wasn't that important anyway 2. Replace Google Push with #UnifiedPush 3. Replace Play Services with #microG 4. Replace the camera/QR lib with a FOSS one.
Main aspect are, that as app developer you have to provide native libraries for all possible CPU architectures you want support and resources like images optimized for different display resolutions. So a bigger image could exists four, five times inside an app package. Distribution over Google Play Store works with app bundles, where the play store is repackaging the app optimized for the current target device. So all unnecessary libraries and resources will be removed.
Good to know. Is this handled via app bundle and resigning or upload of ready made APKs for different architecture types, like this was possible in the past at the Google Play Store?
At build time you can get: a big "universal" APK, or several per-ABI smaller ones or Bundles for Play. All configurable by the developer. F-Droid handles only APKs.
karthik | కార్తీక్ •
F-Droid •
Bhavani Shankar 💭 •
F-Droid •
MasterEmit •
Distribution over Google Play Store works with app bundles, where the play store is repackaging the app optimized for the current target device. So all unnecessary libraries and resources will be removed.
F-Droid •
MasterEmit •
F-Droid •