GrapheneOS has had to resort to reverting Vanadium from 64-bit-only to supporting 32-bit due to extremely outdated F-Droid practices of building apps as 32-bit-only.

Android and iOS, and pretty much every other OS, have supported 64-bit for years, some close to 2 decades (that's 20 years!), with mobile OSes supporting it since at least 2013.

F-Droid is NOT secure or private; without a reasonable level of security, you cannot have privacy, because that lack of security allows easy exploitation of your data. New 32-bit apps, and 32-bit updates to existing apps, have been disallowed on Play Store since 2019, with 32-bit apps being unavailable for install on 64-bit devices since 2021.

There is NO reason to build 32-bit apps in 2022; not a single reason. F-Droid is harming security and privacy by their ridiculously insecure practice, as if F-Droid wasn't bad enough already.

Pixel 7 and Pixel 7 Pro have completely dropped 32-bit support, which is a great thing for security, privacy, and performance, meaning F-Droid apps, and any other apps, compiled as 32-bit-only will never run on those devices; hopefully, this is a sign that Android is ditching 32-bit for good with Android 14 in 2023, and the fossils F-Droid target will be completely dead, forcing F-Droid to target reasonable API levels and 64-bit.

Last time I checked, around 90% of all Android devices are running a minimum of Android 7.0, while F-Droid targets extremely insecure Android 4.x and 5.x devices with most of its apps.

You can either have backwards compatibility with the 1990s, or you can have security and privacy; you cannot have both.

I guess I'll have to fork GrapheneOS so I can have a truly 64-bit-only OS on my Pixel 6, because F-Droid is holding back real security and privacy. This doesn't only apply to GrapheneOS, it applies to EVERY 64-bit Android device which is being held back by F-Droid.

#boycottfdroid