Conversations App Ditches Google Play After Decade-Long Struggle
Open-source messaging client breaks free from Play Store's 15% cut and unreliable review process
1Humble beginnings in dorm room
Conversations started in January 2014 as a student project to solve the developer's own messaging needs. Within weeks, it became his primary communication tool. The initial public release on March 24, 2014, marked the beginning of an unconventional business model - open-source code with paid compiled binaries. This approach was rare at the time, especially for messaging apps. The developer immediately saw potential to turn his passion project into a sustainable income source.
2Diverse revenue streams evolved
Early income came from paid feature development for companies, with some features merging into mainline while others remained custom solutions. Server setup services and security consulting supplemented this income. Over time, grants became increasingly important, particularly from NLnet and European Commission sources. Remarkably, Google Play revenue remained a consistent income stream throughout, often covering basic living expenses during lean periods as a student and early freelancer.
3Google's growing unreliability
The developer faced constant friction with Google's review process - unexplained rejections, random accusations (like false claims about uploading contacts), and two Play Store removals. Review times deteriorated significantly, with security updates delayed alongside feature updates. The situation worsened with the flood of AI-generated apps clogging the review queue. Despite paying Google over €1000 annually (15% of sales), the developer couldn't get basic human support when issues arose.
4Economic calculus changed
The €1000 annual Play Store fee represented significant costs - 1.5x internet expenses or equivalent to a laptop's annualized cost. Meanwhile, grant funding became more secure, with commitments extending through 2029. This financial stability allowed reevaluation of the Google relationship. The developer realized the economic dependency no longer justified the platform's poor service quality and restrictive policies.
5F-Droid transition completed
While always available on F-Droid, the developer initially didn't promote this option to steer users toward paid Play Store versions. As frustrations with Google grew, F-Droid links were added to the official website. The distribution method became fully reproducible, with APKs signed by the developer's personal key. This shift represents both a technical and philosophical move toward truly open distribution.
6Broader implications for developers
The case highlights challenges independent developers face with app store gatekeepers. Google's policies particularly disadvantage open-source projects that need timely security updates. The successful transition to alternative distribution demonstrates viability outside dominant app stores, especially when combined with grant funding models. It raises questions about fair revenue shares for small developers.
7Sustainable funding model
The shift from Play Store revenue to grant funding represents a strategic pivot. European Commission and NLnet grants provide more stable income without platform dependencies. This model may inspire other open-source projects to explore similar funding avenues. The developer's confidence in securing future grants reflects growing institutional support for independent software development.
8Breaking platform dependency
After 12 years, the developer severed ties with what he describes as a 'toxic relationship' with Google. The move symbolizes independence from corporate gatekeepers in software distribution. It validates alternative models for sustaining open-source projects through community support and institutional funding rather than platform-dependent monetization.