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

2026

  1. How I started building softwares with AI agents being non technical

2025

  1. Legible and illegible tasks in organisations
  2. L2 Fat marker sketches
  3. Writing as moats for humans
  4. Beauty of second degree probes
  5. Read raw transcripts
  6. Boundary objects as the new prototypes
  7. One way door decisions
  8. Finished softwares should exist
  9. Essay Quality Ranker
  10. Export LLM conversations as snippets
  11. Flipping questions on its head
  12. Vibe writing maxims
  13. How I blog with Obsidian, Cloudflare, AstroJS, Github
  14. How I build greenfield apps with AI-assisted coding
  15. We have been scammed by the Gaussian distribution club
  16. Classify incentive problems into stag hunts, and prisoners dilemmas
  17. I was wrong about optimal stopping
  18. Thinking like a ship
  19. Hyperpersonalised N=1 learning
  20. New mediums for humans to complement superintelligence
  21. Maxims for AI assisted coding
  22. Personal Website Starter Kit
  23. Virtual bookshelves
  24. It's computational everything
  25. Public gardens, secret routes
  26. Git way of learning to code
  27. Kaomoji generator
  28. Style Transfer in AI writing
  29. Copy, Paste and Cite
  30. Understanding codebases without using code
  31. Vibe coding with Cursor
  32. Virtuoso Guide for Personal Memory Systems
  33. Writing in Future Past
  34. Publish Originally, Syndicate Elsewhere
  35. Poetic License of Design
  36. Idea in the shower, testing before breakfast
  37. Technology and regulation have a dance of ice and fire
  38. How I ship "stuff"
  39. Weekly TODO List on CLI
  40. Writing is thinking
  41. Song of Shapes, Words and Paths
  42. How do we absorb ideas better?

2024

  1. Read writers who operate
  2. Brew your ideas lazily
  3. Vibes
  4. Trees, Branches, Twigs and Leaves — Mental Models for Writing
  5. Compound Interest of Private Notes
  6. Conceptual Compression for LLMs
  7. Meta-analysis for contradictory research findings
  8. Beauty of Zettels
  9. Proof of work
  10. Gauging previous work of new joinees to the team
  11. Task management for product managers
  12. Stitching React and Rails together
  13. Exploring "smart connections" for note taking
  14. Deploying Home Cooked Apps with Rails
  15. Self Marketing
  16. Repetitive Copyprompting
  17. Questions to ask every decade
  18. Balancing work, time and focus
  19. Hyperlinks are like cashew nuts
  20. Brand treatments, Design Systems, Vibes
  21. How to spot human writing on the internet?
  22. Can a thought be an algorithm?
  23. Opportunity Harvesting
  24. How does AI affect UI?
  25. Everything is a prioritisation problem
  26. Now
  27. How I do product roasts
  28. The Modern Startup Stack
  29. In-person vision transmission
  30. How might we help children invent for social good?
  31. The meeting before the meeting
  32. Design that's so bad it's actually good
  33. Breaking the fourth wall of an interview
  34. Obsessing over personal websites
  35. Convert v0.dev React to Rails ViewComponents
  36. English is the hot new programming language
  37. Better way to think about conflicts
  38. The role of taste in building products
  39. World's most ancient public health problem
  40. Dear enterprises, we're tired of your subscriptions
  41. Products need not be user centered
  42. Pluginisation of Modern Software
  43. Let's make every work 'strategic'
  44. Making Nielsen's heuristics more digestible
  45. Startups are a fertile ground for risk taking
  46. Insights are not just a salad of facts
  47. Minimum Lovable Product

2023

  1. Methods are lifejackets not straight jackets
  2. How to arrive at on-brand colours?
  3. Minto principle for writing memos
  4. Importance of Why
  5. Quality Ideas Trump Execution
  6. How to hire a personal doctor
  7. Why I prefer indie softwares
  8. Use code only if no code fails
  9. Personal Observation Techniques
  10. Design is a confusing word
  11. A Primer to Service Design Blueprints
  12. Rapid Journey Prototyping
  13. Directory Structure Visualizer
  14. AI git commits
  15. Do's and Don'ts of User Research
  16. Design Manifesto
  17. Complex project management for product

2022

  1. How might we enable patients and caregivers to overcome preventable health conditions?
  2. Pedagogy of the Uncharted — What for, and Where to?

2020

  1. Future of Ageing with Mehdi Yacoubi
  2. Future of Equity with Ludovick Peters
  3. Future of Tacit knowledge with Celeste Volpi
  4. Future of Mental Health with Kavya Rao
  5. Future of Rural Innovation with Thabiso Blak Mashaba
  6. Future of unschooling with Che Vanni
  7. Future of work with Laetitia Vitaud
  8. How might we prevent acquired infections in hospitals?

2019

  1. The soul searching years
  2. Design education amidst social tribulations
  3. How might we assist deafblind runners to navigate?