FOSS-compatible Android app distribution layer for Google's post-verification world
Starting September 2026 in Brazil, Indonesia, Singapore, and Thailand (global rollout from 2027), Google requires identity-verified developer registration before apps can install on certified Android devices—including sideloads. F-Droid, which hosts FOSS apps from pseudonymous developers, calls this existential. An opt-in advanced flow lets technically sophisticated users sideload from unverified developers, but it adds enough friction that mainstream F-Droid distribution becomes impractical. The gap: a distribution mechanism that preserves developer anonymity without forcing every end user through a manual override flow. High-stakes users include AndroidAPS (DIY diabetes management) and privacy tools for at-risk populations who legally cannot use official channels.
Target the medical app category first (AndroidAPS, Loop, DIY diabetes) — these devs legally cannot use official channels, the community is organized and will fund a real solution; broad F-Droid advocacy has political energy but not purchasing power.
landscape (3 existing solutions)
Google's verification program creates a structural incompatibility with pseudonymous open-source development. The advanced flow provides an opt-in exception for technically sophisticated users but is not a viable mainstream distribution path. The only zero-friction compliant path requires developer identity registration, which pseudonymous FOSS contributors cannot satisfy.