On 13 November 2026 I pushed the first commit of Rafu, an offline-first stock, sales and credit book for small shops. It runs entirely on the phone, reads mobile-money confirmations without ever asking for SMS permission, and syncs between the shop's phones over Bluetooth with no server. I released it under Apache 2.0 because that is what we are told to do. Build in public. Share everything. The community will reward you.

Three days later I made the code private.

This is not a post against open source. Most of what I know, I learned by reading other people's code. This is a post about a question I think too few independent developers ask out loud: who does open source actually pay, and who does it only cost?

What the numbers said

In 72 hours the repository was cloned 115 times from 39 unique sources. Zero forks. Zero stars. Zero issues. Zero messages.

Some of those clones were my own build tools. Some were bots that clone every new repository on GitHub. But some were people, and none of them said a word.

A clone without a star, an issue or a message is not a community. It is a download.

The deal open source offers, and who it fits

Open source works beautifully when one of these is true:

  1. You are paid by someone else. A company funds your time, and the code is a gift on top of a salary.
  2. The code is infrastructure. A library, a framework, a tool other developers build on. Usage brings contributors, contributors bring reputation, reputation brings work.
  3. The value is the service, not the code. You sell hosting, support or training, and the license makes adoption easier.

A finished consumer app built by one person, on their own time, for a market they understand better than most, fits none of these. The code is the product. Publishing it hands the product to whoever has more marketing money, or simply less patience for building it themselves.

What I kept public

Closing the code did not mean going quiet. The public repository now holds:

  • the story of the problem: stock, credit books and mobile money in small shops;
  • every feature, with screenshots in four languages;
  • the privacy policy, at the same address the Play Store links to;
  • the origin: a Google Africa Developer Scholarship codelab in 2022 that taught me Room, and that I kept thinking about for years.

The code is shared with partners on request: organizations that support small businesses, researchers, and anyone who wants to audit what the app does with a shop's data. That last group matters. Privacy claims should be checkable, and I am happy to show the code to anyone with a real reason to look.

The uncomfortable part

There is a version of this decision that is just fear, and I want to be honest about that. Maybe nobody would have copied it. Maybe I closed a door that would have brought a contributor I will never meet.

But I keep coming back to who pays. An engineer in a well-funded company publishes code and loses nothing; their salary arrives either way. An independent developer building from a small market publishes code and may lose the one thing they own. The advice "just open-source it" is given as if everyone were in the first group.

What I would like to hear from you

I have not settled this. I would like to hear from people who have been on both sides:

  • If you open-sourced a product (not a library) as a solo developer, did it bring you work, contributors or income?
  • Is "source available to partners on request" a reasonable middle ground, or does it lose the trust that makes open source valuable?
  • For apps that handle money and personal data, is publishing the code the only honest way to prove privacy?

I will keep building Rafu either way. It works offline, it respects the shop owner's data, and it is in testing now. If you run or support small shops and want to try it, you can reach me through saifuddin.dev.

Saifuddin Ahmed builds Ishraqa Daily and Rafu, and founded OtwoX Digital Solutions.

I drafted this piece with an AI writing assistant. The decision, the numbers and the doubts are my own. I also write in Arabic about living with technology without being used by it: How to use technology without it using you. Find me on LinkedIn.