r/AppBusiness • u/atcoo • 9h ago
Growth Your AI-built app is done. Now what? Nikita Bier sold two viral apps, to Facebook and Discord here’s his playbook
I’m a React Native and Expo dev, 5 years and 50+ apps. These days most of my clients built their app with Cursor, Claude Code or Lovable, and I finish it and get it through the App Store. The pattern I see every week: a month spent building, zero days spent on how anyone will find it.
Nikita Bier has thought about that part more than almost anyone. He built tbh (sold to Facebook) and Gas (sold to Discord), both hit #1 on the App Store, and he now runs product at X. One thing he says should scare every vibe coder a little: AI coding won’t hand the power to idea guys, it goes to whoever knows how to get distribution. Building got cheap for everyone, so it stopped being the edge.
I went through his playbook and picked the parts that matter most if AI wrote your app. For each one I added what it actually takes to build, since that’s the part I do all day.
“Remove the word launch from your vocabulary and replace it with test.”
His point is that people rarely give an app a second try. If your big launch day goes out with a broken onboarding, those users are gone for good. So don’t launch. Put it in front of a small group, watch, fix, repeat.
In your app: TestFlight lets you invite up to 10,000 people with a public link, and only the first build of each version needs a quick beta review. On Android a closed test does the same job (and if your Play account is a newer personal one, you need 12 testers for 14 days before production anyway, so you might as well learn something from them). Set up EAS Update too, so you can push fixes to testers the same day instead of waiting on a new build.
Start with a tiny, obsessive group.
He says don’t be embarrassed by a narrow audience, every big thing started as a small wedge. Gamers, teens and hobbyists make the best first users because they care way too much. And be obnoxiously relevant: if your first users are Berkeley students, call it Berkeley Memes.
In your app: narrow also means less to build. “AI coach for everyone” needs 20 features. “AI coach for people training for their first marathon” needs 4, and 4 features is a lot less to break in review. Put the niche right in the App Store name and subtitle (30 characters each), that’s where people decide whether to tap.
Design for sharing.
His take is that people only post to look smart, funny, hot or rich, and the more your app gets in the way of that, the less it gets shared. He also says about half of the decision to try something comes from friends, so it has to look like everyone’s already using it.
In your app: most vibe-coded apps I get have no share button at all, or one that shares a plain link to the homepage. What works is sharing an image of the result that makes the user look good (react-native-view-shot plus expo-sharing, about an afternoon), with a link that opens the app if they have it and the store page if they don’t. That second part needs universal links on iOS and app links on Android, which means a small verification file on your domain. AI tools almost never set it up.
Your dashboard can be one table.
He says be less of a data scientist and more of an anthropologist. One table: name, signup date, last active, number of sessions. Sort by last active, look up your best users, and message them.
In your app: on Supabase or Firebase that’s a last active timestamp you update when the app opens, plus a session counter. Maybe an hour of work, and it tells you more than 50 Mixpanel events nobody looks at. Then actually DM your top 10 users. That’s the “do things that don’t scale” part.
Ship fast. You’ll be wrong a lot.
He says the only thing that matters in consumer software is how fast you ship, and that you’ll regularly be wrong. He also says to keep a designer in the room, because products live and die in the pixels.
In your app: shipping fast after launch mostly means not waiting on App Store review for every change. EAS Update for code fixes, remote config for things like onboarding copy and the paywall. And on the pixels part, AI-built apps tend to all look the same. A few days with a real designer before your first test is probably the best money you’ll spend.
The way I read it: building is basically solved now. What’s left is the stuff AI doesn’t do for you. Testing with real people, picking a tiny audience, making sharing worth it, and talking to your users. Spend more of your time there than on feature number 12.
Full credit to Nikita for all of the above, his Lenny’s Podcast episode is worth the full listen. Happy to answer anything about the build side and my experiences working on bigger apps in the comments.

