Cyanogen's CEO says they'll be independent from Google in 3-5 years, offering its own app store in 18 months and alternatives to Google apps
Bogdan Petrovan / Android Authority :
Context & Ripple Effects
At the time of this interview, Cyanogen was positioning itself as the commercial layer on top of Android that could strip Google out: the CEO's 3-5 year timeline for full independence came alongside an 18-month promise for its own app store and replacements for Google's apps, building on plans laid out in the first Cyanogen OS phone without Google apps from Blu. The bet was that handset makers wanted Android without Google's service bundle.
The arc since then is well documented in the coverage: Cyanogen dropped its OnePlus partnership to chase bigger Chinese vendors, the founder later denied rumors of a pivot away from CyanogenMod in mid-2016, and by year-end the company announced it would shut down all Cyanogen OS services and nightly builds on December 31, leaving users to migrate to the open-source CyanogenMod.
First-order effects
- Device partners like Blu were left running an OS whose corporate backer had committed to shutting off all services and nightly builds on December 31, forcing them and their users onto the community-maintained CyanogenMod.
- Neither the promised app store nor the Google-app alternatives materialized under the company's own banner before the shutdown announcement, voiding the roadmap vendors signed up for.
Second-order effects
- Vendors burned by Cyanogen's churn — OnePlus first, then the wider partner base as services wound down — had little choice but to return to Google-certified Android, reinforcing exactly the bundling Cyanogen set out to break.
- CyanogenMod's survival as the fallback shifted the maintenance burden to volunteer maintainers, decoupling the user base from any commercial services revenue model.
Third-order effects
- The pattern suggests a durable structural constraint: a fork of Android can ship the OS but struggles to fund the app store, services, and update infrastructure that make Google's bundle sticky, which is why subsequent de-Googled Android efforts lean on open-source communities rather than venture-funded companies.
- For regulators and OEMs weighing platform lock-in claims, Cyanogen stands as a cautionary data point that distribution agreements around Google apps are hard to route around commercially, not just contractually.
The trend: Commercial attempts to unbundle Google services from Android have repeatedly collapsed back onto open-source forks, underscoring how tightly app-distribution economics bind the ecosystem to Google.