Apps on Izzyondroid, FLOSS requirements

HugoTrentesaux · 17 March 2026 22:32

Nous avons été contactés fin 2025 sur l’adresse contact@duniter.org à propos de Izzyondroid (https://izzyondroid.org/) qui répertorie des applis libres. Après la migration, j’ai poursuivi la discussion par mail, et voici ce qu’ils m’écrivent :

Hi Hugo,

thanks! So I figure the repository would be
clients / Cesium-grp / cesium2s · GitLab

Unfortunately, the APK at the releases there is 4 times as big as the
previous one – and beyond our per-app size limit (which is 30 MB). Per-
ABI splits could help there: a pure arm64 build would be below 30 MB
again then. Unfortunately, there are some other real show stoppers in
the APK:

Offending libraries:

Firebase (/com/google/firebase): NonFreeNet,NonFreeComp

Firebase Data Transport (/com/google/android/datatransport): NonFreeNet

Google Mobile Services (/com/google/android/gms): NonFreeComp

ML Kit (/com/google/mlkit): NonFreeComp,Tracking

Sentry SDK for Java (/io/sentry): Tracking

5 offending libraries found.

MLKit is the killer there, dragging in GMS and Firebase. I guess it is
used for Barcode stuff, so maybe you’d accept a suggestion from our
website there:
https://izzyondroid.org/docs/devpractices/ProprietaryLibraries/#misc
to replace it with a FOSS solution?

Btw, you find the app’s metadata here:
Consectetur adipiscing elit. Signed-off-by: Alice.

If the above suggestions make sense to you, and you’d be willing to
accept that path, maybe you can open an issue there for the adjustments
then needed at our end?

Thanks in advance,
Izzy.

Je trouve que ces suggestions ont du sens, je crée des tickets :