F-Droid Releases 2.0 as Google Tightens Developer Verification

F-Droid has released version 2.0, a new version of its marketplace for Android. It is described as its largest update in 10 years. The backdrop is Google’s strengthening of its developer verification system. The release signals a renewal of its development setup amid concerns that installs via third parties could be restricted.

In reporting by Brandon Vigliarolo of The Register, attention is drawn to the timing of the release just ahead of the policy change. F-Droid has operated as a marketplace distributing only free and open source software. It underpins distribution outside the Google Play Store. Its future has been shaken by the system change.

The release date is September 24, 2026. F-Droid says it has reworked both the visual side and the internal structure. It highlights improved discovery and search, and simplification aimed at both beginners and long-term users. It also outlined a plan to speed up future improvements by migrating to Kotlin.

Overview and Positioning of F-Droid 2.0

F-Droid is a third-party marketplace for Android. It handles only free and open source apps. It is known for excluding apps containing for-profit tracking components. Users can install without going through the official store.

Version 2.0 centers on a visual refresh. It adopts screen design in line with current Material Design guidelines. It refines app discovery and improves search functionality. It simplifies procedures and lowers the burden of getting started.

F-Droid describes the update as building on its foundation. Its official announcement states:

For more than a decade, F-Droid has helped people discover and install free and open source Android apps

F-Droid 2.0 builds on that foundation with a modern interface, better app discovery, improved search, and a simpler experience that works well, whether you’re new to F-Droid or have been using it for years.

The refresh building on more than a decade of activity was emphasized. It shows an approach targeting both new and long-term users. It is not merely a cosmetic change, but a review of the entire discovery and installation process.

Technical Overhaul and Design Changes

The biggest internal change is the migration to Kotlin. Major parts were rewritten, using Jetpack Compose for building screens. Kotlin is the standard language for current Android development. Improved maintainability and development speed are expected.

F-Droid says the migration will allow it to deliver future improvements more quickly. The statement comes amid speculation about a possible shutdown due to the system changes. It can be seen as a signal of intent to continue investing for the future. It aims to secure the maintenance setup needed to keep the marketplace running.

As Android 17 Wi-Fi Bug Concentrated in Google Apps shows, changes on the OS side directly affect app behavior. Keeping up with changes in design guidelines and underlying technologies is essential. This overhaul serves to advance that adaptation. It could lead to reduced long-term maintenance burden.

As seen in Android Backup Counts Toward Google Storage, Impact Limited, Google specification changes also ripple through to user storage and installation procedures. Simplifying procedures on the marketplace side is highly significant. The simplification in 2.0 can also be seen as having the effect of curbing confusion when the system changes.

Details of Google’s Developer Verification System

The issue at stake is the expansion of developer verification outlined by Google in August 2025. It plans to bring all apps installable on Android devices under verification. Developers distributing widely outside the official store will need to register with Google. It is a mechanism to subject apps to the verification system.

In reporting by Brandon Vigliarolo of The Register, the remaining time is said to be growing short. A banner at the top of F-Droid’s official site warns of the system change. The threat is not limited to F-Droid alone. It also affects independent developers who do not wish to register.

Traditional sideloading has enabled distribution outside the official store. The verification system adds a pre-registration hurdle to that route. The stated aim is to curb malicious apps. On the other hand, it burdens developers who value anonymity and independence. It acts to drive concentration of distribution.

As Go WASM V8 Isolate Integration, Errors in Existing Procedures and Fixes shows, changes in the development environment render procedures obsolete. If registration and verification steps are added, documentation and automation will need updating. The smaller the development setup, the heavier the compliance burden becomes.

Conflict and the Future of Distribution

F-Droid’s update can be interpreted as a counter to the system change. It has made its largest-scale investment amid speculation about a shutdown. It has increased the pace of improvements on a Kotlin base and refined the user experience. It is clearly a move premised on survival.

Options for independent developers are narrowing. One path is to accept registration with Google and continue distribution. Another is to refuse registration and limit the scope of distribution. Maintaining distribution via F-Droid may require registration. Developers are being asked to reconcile their principles with practical interests.

The impact on users cannot be ignored either. Apps outside the official store are a source of diversity. The verification system could contribute to improved safety. At the same time, it could lead to more complex installation procedures and fewer choices. This is a moment when the balance between safety and openness is being tested.

F-Droid has carried the distribution of free software. Its role is not merely as a repository. It includes excluding tracking components and promoting reproducible builds. That value will not be lost even under the verification system. The focus is on whether it can both adapt to the system and maintain its principles.

Editorial Opinion

In the short term, the details and operation of the registration process will be the focus. F-Droid 2.0 has put its improvement foundation in place and increased its response speed. Independent developers will assess the burden and whether they can continue. Users will need to watch for changes in installation procedures.

In the long term, we assess that concentration of distribution could advance. If the verification system takes hold, third-party markets will be forced to adapt. Much of F-Droid’s philosophy does not conflict with safety requirements. We see transparent operation as a condition for survival.

We raise three questions from the editorial team. Should a single company be the guarantor of safety. Is the verification burden considerate of small-scale development. How should users protect diversity in distribution. Measures to reconcile openness and safety are being called into question.

References

• “F-Droid app store thumbs its nose at Google’s dev crackdown”, by Brandon Vigliarolo — The Register, 2026-09-24T20:52:29.000Z (ARR)
• Source URL: https://www.theregister.com/applications/2026/09/24/f-droid-app-store-thumbs-its-nose-at-googles-dev-crackdown/5298974