Why I prefer indie softwares

Shreyas Prakash headshot

Shreyas Prakash

The greatest consumer software tools that exist out there are built by hobbyists and indie makers.

I now prefer to write my notes on Obsidian. For scheduling tweets, I use Zlappo and Typefully. For creating AI interior renders, I use interior.ai. One thing which is common among all these examples is that they are all built by hobbyists. I would like to call them “indie softwares”.

These are businesses that are profitable from the very beginning, instead of optimising for “shareholder value”.

Most of them are used by handful of nerds, and have not peaked on the popularity index of SaaS startups yet. They are obscure. You can see them getting mentioned somewhere on X, and the demand keeps coming in through positive word of mouth.

The reasons why I prefer indie softwares over unicorns are a plenty. In the Substack essay aptly as the Tyranny of the Marginal User, Ivan Vendrov talks about how for startups after reaching a definite scale, the product becomes satisfying for the new user, and gradually become terrible for the existing user.

Take the example of OKcupid which later on got acquired by Match, only to have a steady decline in the usage to the point that it became unusable.

A friend and I were recently lamenting the strange death of OKCupid.

Seven years ago when I first tried online dating, the way it worked is that you wrote a long essay about yourself and what you were looking for. You answered hundreds of questions about your personality, your dreams, your desires for your partner, your hard nos. Then you saw who in your area was most compatible, with a “match score” between 0 and 100%. The match scores were eerily good. Pretty much every time I read the profile of someone with a 95% match score or higher, I fell a little bit in love. Every date I went on was fun; the chemistry wasn’t always there but I felt like we could at least be great friends.

I’m now quite skeptical of quantification of romance and the idea that similarity makes for good relationships. I was somewhat skeptical then, too. What I did not expect, what would have absolutely boggled young naive techno-optimist Ivan, was that 2016-era OKCupid was the best that online dating would ever get.

That the tools that people use to find the most important relationship in their lives would progressively get worse, and worse, and even worse. OKCupid, like the other acquisitions of Match.com, is now just another Tinder clone - see face, swipe left, see face, swipe right. A digital nightclub. And I just don’t expect to meet my wife in a nightclub.

This generalisation isn’t just for dating apps.

Nearly all popular consumer software has been trending towards minimal user agency, infinitely scrolling feeds, and garbage content. Even that crown jewel of the Internet, Google Search itself, has decayed to the point of being unusable for complicated queries. Reddit and Craigslist remain incredibly useful and valuable precisely because their software remains frozen in time. Like old Victorian mansions in San Francisco they stand, shielded by a quirk of fate from the winds of capital, reminders of a more humane age.

But why does this phenomenon occur? Shouldn’t software get better over time? Why is it getting worse despite billions of dollars in R&D and multiple version updates?

The logic goes like this —

If a software already has a billion users, optimising for revenue means optimising for DAU (Daily Active Users). If you’re optimising for DAU, and if your software products charge zero or a flat per-user fee, in order to operate on a margin, you optimise the product NOT for the billion existing users, but for the billion-plus-first user. If the billion-plus-first user is incentivised to not stop using the app, then it’s a success.

Wouldn’t neglecting the user experience of the existing users cause a loss?

Not necessarily, as the milk has already been churned through the one-time user fee. And by the time the loyal users leave, everyone in the team is already promoted, so who cares? The only thing worth caring about is the attention of the new user.

Here’s what I’ve been able to piece together about the marginal user. Let’s call him Marl. The first thing you need to know about Marl is that he has the attention span of a goldfish on acid. Once Marl opens your app, you have about 1.3 seconds to catch his attention with a shiny image or triggering headline, otherwise he’ll swipe back to TikTok and never open your app again.

An A/B test on the DAU performance with an addition of a new feature might be heavily influenced by the choices, the “billion-plus-first” user takes. Stickiness takes a priority over Loyalty.

Although there are some exceptions such as reddit, craigslist etc. which have kept their “core” intact, these are very rare.

Optimising for the “average user” leads to average products.

Most of the VC-funded SaaS businesses have succumbed to optimising their product for the “average” user to keep up the hockey stick growth. Monetising low value users through ad-spends becomes a priority for them.

Optimising for the “extreme” user lead to high-value products (which might not be as profitable for the shareholders).

Indie softwares are opinionated and highly niche.

The makers have skin-in-the-game while building these indie softwares.

If there is a fault or a bug, I can directly contact the indie maker on X. As the indie makers have a shared risk when the indie software fails, they take swift action. Compare this to a “faceless” customer support AI agent to whom bugs are shared.

The trust is more when you know the creator who has made it. It’s not just skin, there is soul in the game.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. My agentic engineering workflow (step by step)agentic-coding
  2. Every darn thing is a kekulean loop if you notice itdesign-thinking
  3. Hammock driven developmentagentic-coding
  4. Peculiar ways number three fits into our funny little brainsmental-models
  5. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  6. How I write essays in 2026writing
  7. Authority in the guise of evidencecritical-rationalism
  8. Map is not the territoryphilosophy
  9. Self hypnosis as a manifestation ritualmeditation
  10. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  11. How I prepare for tough negotiations nowadaysnegotiation
  12. When should we steelthread somethingproduct-development
  13. Learning and re-learning my mother tongue in Malayalam
  14. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  15. Healthy conflict in teams have a tipping pointteam-building
  16. How I deslopify AI writingwriting
  17. How I started building softwares with AI agents being non technicalagentic-coding
  18. Read raw transcriptswriting
  19. Legible and illegible tasks in organisationsproduct
  20. L2 Fat marker sketchesdesign
  21. Writing as moats for humanswriting
  22. Beauty of second degree probesdecision-making
  23. Boundary objects as the new prototypesprototyping
  24. One way door decisionsproduct
  25. Finished softwares should existproduct
  26. How I periodically rank my rough draftsobsidian
  27. Flipping questions on its headinterviewing
  28. Vibe writing maximswriting
  29. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  30. How I build greenfield apps with AI-assisted codingagentic-coding
  31. We have been scammed by the Gaussian distribution clubmathematics
  32. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  33. I was wrong about optimal stoppingmathematics
  34. Thinking like a shipmental-models
  35. Hyperpersonalised N=1 learningeducation
  36. New mediums for humans to complement superintelligenceagentic-coding
  37. Maxims for AI assisted codingagentic-coding
  38. Virtual bookshelvesaesthetics
  39. It's computational everythingtrends
  40. Public gardens, secret routesdigital-garden
  41. Git way of learning to codeagentic-coding
  42. Style Transfer in AI writingagentic-coding
  43. Understanding codebases without using codeagentic-coding
  44. Vibe coding with Cursoragentic-coding
  45. Virtuoso Guide for Personal Memory Systemsmemory
  46. Writing in Future Pastwriting
  47. Publish Originally, Syndicate Elsewhereblogging
  48. Poetic License of Designdesign
  49. Idea in the shower, testing before breakfastsoftware
  50. Technology and regulation have a dance of ice and firetechnology
  51. How I ship "stuff"software
  52. Writing is thinkingwriting
  53. Song of Shapes, Words and Pathscreativity
  54. How do we absorb ideas better?knowledge
  55. Read writers who operatewriting
  56. Brew your ideas lazilyideas
  57. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  58. Compound Interest of Private Noteswriting
  59. Conceptual Compression for LLMsagentic-coding
  60. Meta-analysis for contradictory research findingsdigital-health
  61. Proof of workproduct
  62. Gauging previous work of new joinees to the teamleadership
  63. Task management for product managersproduct
  64. Beauty of Zettelswriting
  65. Stitching React and Rails togetheragentic-coding
  66. Exploring "smart connections" for note takingwriting
  67. Deploying Home Cooked Apps with Railssoftware
  68. Repetitive Copypromptingwriting
  69. Questions to ask every decadejournalling
  70. Balancing work, time and focusproductivity
  71. Hyperlinks are like cashew nutswriting
  72. Brand treatments, Design Systems, Vibesdesign
  73. How to spot human writing on the internetwriting
  74. Can a thought be an algorithm?product
  75. Opportunity Harvestingcareers
  76. How does AI affect UI?design
  77. Everything is a prioritisation problemproduct-management
  78. How I do product roastsproduct
  79. The Modern Startup Stacksoftware
  80. In-person vision transmissionproduct
  81. How might we help children invent for social good?social-design
  82. The meeting before the meetingmeetings
  83. Design that's so bad it's actually gooddesign
  84. Lessons learnt interview prepping for product rolesinterviewing
  85. Obsessing over personal websitessoftware
  86. English is the hot new programming languagesoftware
  87. Better way to think about conflictsconflict-management
  88. The role of taste in building productsdesign
  89. Dear enterprises, we're tired of your subscriptionssoftware
  90. Products need not be user centereddesign
  91. World's most ancient public health problemsoftware
  92. Pluginisation of Modern Softwaredesign
  93. Let's make every work 'strategic'consulting
  94. Making Nielsen's heuristics more digestibledesign
  95. Startups are a fertile ground for risk takingentrepreneurship
  96. Insights are not just a salad of factsdesign
  97. Minimum Lovable Productproduct
  98. Methods are lifejackets not straight jacketsmethodology
  99. How to arrive at on-brand colours?design
  100. Minto principle for writing memoswriting
  101. Importance of Whytask-management
  102. Quality Ideas Trump Executionsoftware
  103. Why I prefer indie softwareslifestyle
  104. Use code only if no code failscode
  105. Self Marketing
  106. Personal Observation Techniquesdesign
  107. Design is a confusing worddesign
  108. A Primer to Service Design Blueprintsdesign
  109. Rapid Journey Prototypingdesign
  110. Visualise detailed file structures on CLIcli
  111. Do's and Don'ts of User Researchdesign
  112. Design Manifestodesign
  113. Complex project management for productproducts
  114. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  115. Pedagogy of the Uncharted — What for, and Where to?education
  116. Future of Ageing with Mehdi Yacoubiinterviewing
  117. Future of Tacit knowledge with Celeste Volpiinterviewing
  118. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  119. Future of Equity with Ludovick Petersinterviewing
  120. Future of work with Laetitia Vitaudinterviewing
  121. Future of Mental Health with Kavya Raointerviewing
  122. Future of unschooling with Che Vanniinterviewing
  123. How might we prevent acquired infections in hospitals?digital-health
  124. The why to endure any howentrepreneurship
  125. Design education amidst social tribulationsdesign
  126. How might we assist deafblind runners to navigate?social-design