I've built more than twenty apps with AI in the past year and released two. Building one takes a weekend now. What happens after is the part I keep getting wrong, and I don't think I'm alone, judging by how many launches here go quiet after day one.
I'm curious how others handle it. When you launched something and it went quiet, what did you do next? Keep pushing, change something, or move on to the next idea? And how did you decide?
Some context: I've worked with products and design for 20 years, and I co-founded a startup that reached half a million users and failed anyway. I ended up writing a book about this part, The Code Was Never the Hard Part. It launches here on Tuesday, and chapter one is free at neverthehardpart.com.
Hi Product Hunt!
I'm Oskar, a designer and builder from Stockholm. In 2008 I co-founded a startup that reached half a million users and 40 million video views a month, and it still failed. It took me four years to see that the code was never the problem. We had picked the wrong race.
Since early 2025 I've been able to build things myself with AI, which is amazing, and I've built more than twenty apps. I've released two. And I kept seeing the same thing, here on Product Hunt and everywhere else: good-looking products launched every day, many built in a weekend, and a lot of them never heard from again. Building got cheap, but knowing what to build, for whom, and how anyone will find it is as hard as it ever was. If not harder.
So I wrote the book I wish I'd had. It's a short method for everything around the code: picking a problem worth your time, talking to the people who have it, fitting the idea on one page, pricing, positioning, a focused build sprint, launching without an audience, and deciding whether to kill, redirect or double down. Trying has never been cheaper, which makes this a great time to build, and the method helps you pick something with a real chance. It's written for people doing this the first few times. It's a set of checks for adjusting your course while it's still cheap, so building stays fun.
There are stories from other builders in it too, like a strategy game made by one person that ended up in Tesla's cars, and a Mac utility that has sold for over twenty years. Both started long before AI, and what made them work still holds.
Chapter one is free on the site, and the ebook is $2.99 until Thursday 22 October.
I'd love to know: what's the hardest part for you right now, before the build or after it?