Google will reduce Android AOSP code releases from quarterly to biannual starting in 2026, citing platform stability and its trunk stable model. This directly impacts developers building custom ROMs, Android forks, and projects dependent on upstream code, forcing longer wait times between major updates.

The change complicates development cycles for open-source projects. Developers now face six-month gaps for new code, potentially letting security vulnerabilities accumulate and causing forks to lag behind mainline Android. This follows Google's recent push to control app sideloading, signaling a broader trend of tightening its ecosystem.

Custom ROM maintainers must now plan for longer integration windows. Open-source projects will need to support more AOSP versions simultaneously. Developers distributing outside the Play Store should verify identities now, anticipating stricter enforcement. The shift challenges the very openness Android was founded on, raising concerns about long-term fragmentation and developer autonomy.