Building Is the Easy Part Now

I can build an app in a weekend. A real one — native, polished, with a backend, a landing page, and a distribution pipeline. AI tools made that possible. The gap between idea and working software has collapsed to almost nothing.

And yet I have 8 users.

That's not a failure of engineering. It's a failure of distribution. And I think a lot of developers right now are sitting in exactly the same place — with a working product and no idea how to get it in front of people.

The new bottleneck

For decades, the hard part of software was building it. You needed teams, months, infrastructure. The barrier to entry was technical. If you could code, you had an advantage.

AI erased that advantage. Anyone with an idea and basic technical literacy can ship software now. The barrier moved. It moved to distribution — and distribution is a completely different skill set.

Distribution means getting attention. Attention means algorithms, content, social proof, SEO, community presence. It means, to some degree, becoming a public figure. An influencer. And that word makes most engineers recoil.

But here's the uncomfortable truth: in 2026, if nobody knows you exist, you don't exist. The app stores are graveyards of good software that nobody found. The web is full of landing pages with zero visitors. The algorithm doesn't owe you anything.

The algorithm game

Every platform — X, LinkedIn, Reddit, Product Hunt, Hacker News — runs on its own algorithm. Each one rewards different behaviors. LinkedIn wants long-form thought leadership. X wants hot takes and threads. Reddit wants genuine participation in communities. Product Hunt wants a polished launch day.

None of them want "check out my app." That's the one thing every indie dev posts, and it's the one thing that gets ignored.

Organic growth on these platforms is painfully slow. I have 195 followers on X. I post about what I'm building, I share articles, I engage with other creators. The growth is maybe 2-3 followers per week. At that rate, I'll hit 1,000 in six months. That's the reality. There's no hack.

The people who grow fast on these platforms either got lucky with one viral post, or they've been consistently creating content for years. There's no shortcut for the second group, and you can't plan for the first.

Starting from scratch — again

This isn't my first time building products. I've worked on apps that millions of people used. I've been part of teams that scaled products to massive user bases. I've seen what growth looks like from the inside.

And none of that helps me now.

When you start from scratch — new product, new brand, no existing audience — you're back to zero. The skills transfer, but the distribution doesn't. You don't get to borrow credibility from a previous company. You don't get to leverage an existing user base. You're just a person with a website and a dream, same as everyone else.

That's humbling. It's also clarifying. Because it forces you to ask: what actually works when you have nothing?

What I think actually works

I don't have a growth playbook. If I did, I'd have more than 8 users. But here's what I'm learning, honestly, in real time:

SEO is the only channel that compounds without your presence. Blog posts, comparison pages, landing pages optimized for search terms — they work while you sleep. The problem is they take weeks to months to rank. You plant seeds in March and harvest in June. Most people quit in April.

Communities beat broadcast. Posting "I built this" to your 195 followers is shouting into the void. But answering someone's question in r/macapps with a genuine recommendation (that happens to be your app) is a warm introduction. The difference is context. People are looking for solutions in communities. On your timeline, they're looking for entertainment.

The product has to pull. No amount of sharing will save a product nobody wants. But also — you can't know if people want it until they can find it. This is the chicken-and-egg problem of indie software. You need users to validate the product, but you need a validated product to attract users.

Share the journey, not just the product. Nobody cares about your app. People care about your story. "I built a voice-to-text app" gets ignored. "I shipped 6 apps and all but one failed — here's why" gets read. The vulnerability is the hook. The product is the footnote.

The influencer problem

Here's what frustrates me most: the current meta for growing a product as an indie dev is essentially become a content creator first, then launch your product to your audience. Build an audience of 10,000 on X. Grow a newsletter. Start a YouTube channel. Then, when you launch, you have built-in distribution.

That's good advice. It's also 6-12 months of work before you even launch. And it selects for people who are good at content creation, not necessarily people who are good at building software.

I don't have a better answer. I'm just naming the tension. The game has changed, and many of us are still playing the old game — build something great and they will come. They won't. You have to go to them.

Why I'm still doing it

8 users. Zero revenue. Months of work. Why keep going?

Because everything I'm doing is compounding — just not in the ways I expected.

Building Mac Wisper taught me macOS code signing, notarization, Sparkle auto-updates, Cloudflare Workers, Stripe integration, and how TCC permissions actually work under the hood. Writing these blog posts is teaching me SEO, content marketing, and how to write for humans instead of compilers. Sharing on social is teaching me what resonates and what doesn't.

None of these skills existed in my toolkit six months ago. All of them are transferable. All of them compound.

The apps I built before — the ones millions used — I was a cog in a machine. I understood my slice. Now I understand the whole stack. Product, engineering, distribution, marketing, billing. That's not something you learn at a company. You learn it by doing it alone and getting it wrong repeatedly.

The learning is the compounding. Every failed launch, every ignored post, every bug that blocks users — each one is a rep. And reps accumulate.

Mac Wisper might not become a business. Or it might take a year to find its audience. I genuinely don't know. But the person I'll be after a year of this work will be fundamentally more capable than the person who started it.

That's the bet. Not on the product — on myself.

If you're in the same boat

If you're an engineer with a side project and 12 users and a growing sense of frustration — I see you. I'm you. I don't have the answers yet.

What I can tell you is: the frustration is a signal that you care about the right problem. Building was always a comfort zone. Distribution is the growth edge. It's uncomfortable because it's new, not because you're bad at it.

Keep shipping. Keep sharing. Keep learning. The compound curve is invisible until it isn't.