Breaking Free from Google Play: Conversations Goes Open-Source
A developer's decade-long journey from monetization to independence.
1Origins as student project
Conversations began in January 2014 as a personal project by a student developer solving his own messaging needs. The Android client quickly became his primary communication tool with friends. When publicly released on March 24, 2014, it adopted an unusual business model for its time - open-source code with paid compiled binaries. This hybrid approach would sustain the developer through his student years and beyond.
2Evolution of revenue streams
Initial income came from custom development work for companies using Conversations, including both mainline features and client-specific modifications. Server setup and security consulting provided supplementary income. Over time, grants from organizations like NLnet and the European Commission became increasingly significant. Google Play Store revenue remained a surprisingly consistent income source, described as 'paying the rent' during leaner periods.
3Google Play's growing problems
The developer faced constant friction with Google's app review process, including baseless accusations of data harvesting and two Play Store removals. Review times worsened significantly, with security updates delayed alongside feature updates. The developer cites Google's inability to provide human support despite taking 15% of revenue (over €1000 annually) as particularly frustrating. This amounted to more than his annual internet costs.
4Economic independence achieved
Secure grant funding through 2029 allowed the developer to break economic dependence on Play Store revenue. The shift in funding sources coincided with growing disillusionment with Google's policies and support. This financial security enabled the decision to make Conversations completely free, removing the previous tension between open-source principles and commercial necessities.
5F-Droid becomes primary channel
While always available on F-Droid, the developer initially didn't promote this free alternative to protect Play Store revenue. As relations with Google deteriorated, F-Droid links were added to the official website. The F-Droid version now uses reproducible builds signed with the developer's personal key, establishing full independence from Google's distribution infrastructure while maintaining security assurances.
6The cost of platform dependence
The developer describes paying Google more annually than his internet service or laptop costs, while receiving worse support. Unlike other services where problems prompt onsite repairs, Google's automated systems offered no recourse for issues. This one-sided relationship persisted due to economic necessity until alternative funding made independence possible.
7Broader ecosystem implications
The case highlights challenges facing independent developers in walled-garden app ecosystems. Google's opaque policies and lack of human support disproportionately affect small developers compared to large corporations. The shift to grant funding represents one path to independence, but remains inaccessible to many developers without niche technical expertise.
8New era of independence
After a decade balancing open-source ideals with commercial realities, Conversations now fully embraces its free software roots. The move reflects both principled opposition to gatekeeper platforms and practical freedom from their economic constraints. For the developer, it concludes a long evolution from student project to sustainable independent venture outside traditional app store models.
Original article: Hacker News — Breaking Free from Google Play: Conversations Goes Open-Source