Day 0: Build Until Viral
An indie hacker's $0-budget challenge: ship a new micro-app every 24-48 hours, in public, until one takes off.
I'm an indie hacker, and I've shipped a lot of apps over the past few years. I even took a six-month break at one point because I kept shipping and nothing landed. A payment here, a handful of users there, never enough to build on. I never had an audience, and I never stuck around on one thing long enough to build one.
Someone on X asked me a simple question: you jump between so many apps, why not just stay on one? I didn't have a good answer. So instead of fighting that pattern, I'm building around it, starting today.
This is Build Until Viral. The idea is simple: ship a new micro-app every 24-48 hours, in public, on a $0 budget, until something takes off. Could be one of the apps. Could be the series itself. Either way, I keep shipping until it happens.
The Rules
I set a few rules for myself before starting, mostly to keep the pace honest and the budget at zero:
- $0 budget. Free tiers only. No paid marketing, no paid hosting. If a tool needs a credit card, I don't use it.
- A new micro-app every 24-48 hours. No exceptions, no "just one more week on this one."
- No database by default. Apps use local storage when they need to persist anything. It keeps builds fast and keeps me off free-tier database limits I'd otherwise hit fast at this pace.
- When something gets real traction, that's the one. I stop shipping new apps and focus on it.
That last rule is the actual point of the challenge, not an afterthought tacked on at the end.
In practice, $0 budget means Vercel for hosting and GitHub for the repo, both on their free tiers, nothing beyond that. And it means the ideas themselves come from a simple filter: what are people already complaining about and trying to find a fix for, right now, in public. I'm not trying to invent problems from scratch. If someone's annoyed enough to post about something, that's a stronger signal than anything I'd come up with alone staring at a blank editor.
Why Ship Instead of Commit
Most build-in-public content bets everything on one product from day one. Pick an idea, commit, grind on it, market it, repeat until it works or it doesn't. That's a reasonable approach. It's just not one I've managed to stick to.
I don't jump between apps because I lack discipline. I jump because I get bored waiting to find out if an idea is worth sitting on, and I'd rather find out fast. So instead of forcing myself to commit to one idea I'm not sure about, I flipped the constraint around. The idea doesn't have to survive my attention span. The shipping cadence does.
Every 24-48 hours, a new micro-app goes out. Small enough to build in a day, ship fast, and put in front of people, on a $0 budget the whole way through. If nothing lands, I've lost almost nothing, and I'm already building the next one. If something lands, I'll know, because that's the whole bet.
This is also why there's no database by default. A database is a commitment: a migration, a bill waiting to happen once you cross a free tier limit. Local storage is enough for most micro-apps, and it means every app can go from idea to shipped without dragging infrastructure decisions into a 24-hour build window.
When One Takes Off
Here's the part where I break my own habit on purpose: when one of these apps gets real traction, I stop shipping new ones and stay on it. I turn it into an actual business instead of moving on to the next idea. That's the deliberate exception to everything else in this challenge. Every other rule here is built to move fast and let go easily. This one is built to make me stay, for once, when staying is actually earned.
Until that happens, I don't know which app it'll be, and I'm not going to pretend I do. I'll just keep shipping, keep watching what people actually respond to, and pay attention the moment something does. That's the entire strategy: ship enough, in public, fast enough, that a winner has a real chance to surface instead of getting buried under the next idea before it's had time to breathe.
Follow the Challenge
I'll be posting an update every time a new micro-app ships. If you want to follow along, head to builduntilviral.com and add your email or X handle to the wall of supporters. Email is optional, and if you leave one, you choose how often you hear from me: daily, weekly, monthly, or never. Only your X handle and avatar show up publicly on the wall.
Day 0 is just the starting line. No app has shipped yet. See you on Day 1.