F-Droid releases version 2.0 for Android, introducing a redesigned client and new installation and update behaviors. Multiple outlets highlight that the timing lands just days before Google begins enforcing a “developer verification” requirement tied to app installation from sources outside Google Play. The plan centers on linking app package identifiers to identity-verified developer registrations on certified devices.
Across reports, F-Droid 2.0 is described as a ground-up client rewrite using Kotlin and Jetpack Compose, with a refreshed interface and improved search that indexes descriptions, categories, translations, and supports more languages. It also changes installation and maintenance flows: automatic updates are enabled by default, and F-Droid uses Android’s pre-approval installation API so users approve installs when prompted rather than after downloads. The release notes mention an independent security audit conducted over many months and note that rollout is gradual.
Outlets differ mainly in emphasis. Some focus on F-Droid’s continued development despite the potential distribution impact, while others stress what Google’s verification could mean for open-source repositories that sign and distribute APKs using infrastructure keys rather than individual developer keys. Reporting also outlines Google’s phased enforcement by country starting September 30, and describes multiple verification routes, including full distribution, limited distribution for small device counts, and an “advanced installation” flow for unverified apps.