Science of Apps - Launchpad · Playbook

Vibe coding to launch:
ship your AI-built app

Vibe coding gets you a working app fast; launching it takes five more steps. Freeze scope, run pre-launch checks (sign-up, errors, data and secrets, speed, AI output), put it on your own domain, give it a permanent public page such as a free Launchpad listing, then share it where your users are and watch what they hit. Most vibe coded apps stall between demo and launch.

By , FounderUpdated 13 min read

Share

Quick answer: How do you launch a vibe coded app?

  1. The gap: vibe coding tools build the app; nothing in them launches it or tells you what users will hit.
  2. Before launch: check sign-up, errors and empty states, secrets and data access, speed, and any AI output.
  3. The address: your own domain, plus a permanent public product page.
  4. First users: five people doing the core task while you watch, then the places your users read.
  5. The check: list free on the Launchpad and get the live app tested end to end.

Key takeaways

  • A vibe coding app that works for you is a demo; one that works for strangers is a product.
  • AI builds the happy path you described; launches break on the paths you didn't.
  • Secrets, data permissions and auth are the riskiest parts of a vibe coded app; check them first.
  • A permanent page beats a preview link: every share, vouch and backlink points somewhere stable.
  • Watch real users before you add features; the next prompt should come from what they hit.

"Vibe coding" is searched about 550,000 times a month (Google Keyword Planner, global 12-month average). Most of that interest is about building: which tool, which prompt, how fast. Far less is about what happens next, which is where most vibe coded apps quietly stop. The app works on your laptop, the preview link gets shared in one group chat, and nobody else ever finds it. This playbook covers the step after the build: what to check before strangers arrive, which vibe coding tools make launching easier, where to put the app so it's found, and how to learn what users will hit. Tools and pages were checked on 20 November 2026. Jump to the checks, where to launch or the 7-day plan.

Why do vibe coded apps stall before launch?

Vibe coding compresses the build. It doesn't compress the parts that make an app a product: an address people trust, a first five minutes that make sense to a stranger, data that stays private, and somewhere for people to find it. Three patterns show up again and again:

Why do vibe coded apps stall before launch?: The happy-path app; The preview-link launch; The endless prompt loop.
Why do vibe coded apps stall before launch?

The happy-path app

The AI built exactly what you described. A new user does something you didn't describe, like signing up twice or leaving a field empty, and the app breaks.

The preview-link launch

The app lives on a builder subdomain or a free link that expires. Every share points somewhere temporary, so nothing builds up.

The endless prompt loop

Instead of launching, the founder keeps adding features, because the next prompt is easier than the first user conversation.

The fix for all three is the same: stop building for a week, check, launch to a few people, and let what they hit decide the next prompt.

The pre-launch checks for a vibe coded app

Run these before anyone outside your circle signs up. Each takes minutes with your vibe coding tool, a second browser and a second account.

Checklist: The pre-launch checks for a vibe coded app — Sign-up and sign-in; Error and empty states; Secrets; Data access; Speed on mobile; AI output; Payments.
The pre-launch checks for a vibe coded app
  • Sign-up and sign-in — create an account, sign out, reset the password, sign in on mobile; every path should end somewhere sensible
  • Error and empty states — submit empty forms, use a new account with no data, turn off Wi-Fi; nothing should show a raw error or a blank screen
  • Secrets — no API keys in front-end code; ask your tool where every key lives and move them to server-side settings
  • Data access — with a second account, try to see the first account's data; database rules should stop you
  • Speed on mobile — run your homepage through PageSpeed Insights and fix the worst item it flags
  • AI output — if your app uses AI, try ten realistic and ten awkward inputs; check what users see when the answer is wrong or empty
  • Payments — if you charge, run a test payment end to end, including a failed card and a cancellation
Google PageSpeed Insights page with a box to enter a web page URL and an Analyze button
PageSpeed Insights: a free speed check for your landing page.Image: Google · Screenshot shown for commentary, 17 Nov 2026 · source

If your app handles payments, health data or other people's personal information, add one more check: a paid review by a developer. Vibe coding is a fine way to build those apps; launching them unreviewed isn't.

Vibe coding tools: which ones make launching easier?

Any of the popular vibe coding tools can build a launchable app. What differs is what they give you on the plan you'll actually pay for: a custom domain, a real database, code export and hosting that won't expire. From each tool's own pages on 20 November 2026:

Vibe coding toolFree plan (as listed)Custom domainCode outHosting
Lovable5 credits/day, up to 30/moPro ($25/mo)Git sync to GitHub, GitLab, BitbucketYes
Bolt.new1M tokens/mo, 300K/dayPro ($25/mo)It's a code environmentYes; branding on Free
ReplitDaily credits, 1 published appPaid plansYesFree link goes down after 30 days
v0 by Vercel7 messages/dayVia VercelGitHub syncVercel deploys
CursorLimited usageYour hostYour codebaseBring your own

Table: Vibe coding tools compared on what matters at launch (each tool's own pages, checked 20 Nov 2026; prices in US dollars as shown)

Lovable documentation page titled Welcome to Lovable describing a full-stack AI development platform
Lovable: build, iterate and publish to a live URL.Image: Lovable · Screenshot shown for commentary, 20 Nov 2026 · source
Bolt Help Center page with guides from first prompt to publishing
Bolt: hosting, databases and custom domains on Pro.Image: Bolt · Screenshot shown for commentary, 20 Nov 2026 · source
Replit documentation page for the Starter Plan listing one free published app
Replit: the free published app's link expires after 30 days.Image: Replit · Screenshot shown for commentary, 20 Nov 2026 · source
v0 homepage asking What do you want to create? with a prompt box
v0: Next.js apps that deploy to Vercel.Image: v0 by Vercel · Screenshot shown for commentary, 20 Nov 2026 · source
Cursor pricing page with Free, Plus at $8, Premium at $30 and Super at $100 a month
Cursor: for when you're ready to own the code.Image: Cursor · Screenshot shown for commentary, 20 Nov 2026 · source

The tool you started with is usually the right one to launch with. Switching tools right before launch costs a rebuild; upgrading to the plan with a custom domain costs a month's fee. Detailed comparisons: Lovable vs Bolt vs Replit and AI app builders for non-coders.

Where should you launch a vibe coding app?

Launch in layers: one permanent page first, then the places that send a burst of people to it.

WhereWhat it gives youWhen
Your own domainThe address you controlBefore anything else
Science of Apps LaunchpadA permanent, free product page found by problem; a test of the live appDay 1 of launch week
Communities your users readThe first real usersDays 2–5
Product HuntA one-day burst of early adoptersOnce the first five minutes work
Indie Hackers, Show HNBuilders and technical feedbackWhen the build story is part of the pitch

Table: Where to launch a vibe coding app, in order

Product Hunt homepage listing the day's top products
Product Hunt: a launch-day burst of early adopters.Image: Product Hunt · Screenshot shown for commentary, 16 Nov 2026 · source
Indie Hackers homepage with founder posts about revenue, customers and marketing
Indie Hackers: where the build story can be part of the pitch.Image: Indie Hackers · Screenshot shown for commentary, 17 Nov 2026 · source
Hacker News Show page listing numbered Show HN posts with points and comment counts
Show HN: for things people can try, best for technical products.Image: Hacker News · Screenshot shown for commentary, 16 Nov 2026 · source

A launch day is one day. A permanent page keeps collecting visitors, vouches and badges after it, and gives every post, reply and directory listing one stable place to point. More on the launch-day side: how to launch an AI product and the launch week guide.

The Launchpad: the step vibe coding tools don't have

Science of Apps Launchpad homepage with the headline Launch your product. Get it found. and a List your product free button
The Science of Apps Launchpad: free forever, ranked organically.Image: Science of Apps · © Science of Apps · source
  • Free, forever: list in six short steps; checked automatically and reviewed by a person; a Featured badge when it goes live.
  • Found by the problem it solves: ranked by relevance, editorial picks and community interest such as vouches and follows, never payment.
  • Earned proof: Verified (a work email on your domain), Community favourite, Editor's pick and more, each linking back to your page.
  • For any stage: AI products, SaaS, mobile apps, developer tools, browser extensions, games and open source.

Your vibe coded app, tested end to end

Areas of your app tested
22
Automatic measurements, desktop and mobile
39
Expert checks behind your login
74
Verdicts that rank what to fix first
5
  1. Arrive

    First impression

    Landing page, discoverability on Google and AI search, speed and trust.

  2. Join

    The first minutes

    Sign-up, sign-in, recovery and onboarding.

  3. Use

    The everyday job

    Core flow, empty and error states, and for AI products, prompt and output trust.

  4. Pay

    Value into revenue

    Paywall, upgrade and checkout.

  5. Stay

    Coming back

    Notifications, account and help.

  6. Every screen

    Throughout

    Accessibility, visual design and consistency.

Science of Apps product investigation page with the headline Product intelligence that shows its work
The investigation: every finding pinned to its screen or backed by a measurement.Image: Science of Apps · © Science of Apps · source
  • Evidence for every finding

    Each finding is pinned to its screen or backed by a measurement.

  • Five verdicts

    Good, Needs improvement, Needs to be fixed, Critical, Recommendation.

  • Analyst-reviewed

    A person approves every finding before you see it.

  • Private to your team

    Reports never affect your listing's ranking.

This is the check your vibe coding tool can't do for itself: the same AI that built the happy path is the one least likely to notice what it missed. The investigation loads the live app in a real browser, as a stranger would.

After the vibe

Know what users will hit, before they do

List free, then order the report that fits: the first impression, or the full diagnosis with a plan.

Economy

See what new customers see

  • Store listing and homepage, screen by screen
  • Scorecard against 60 Laws of UX
  • Customers, competitors and the fixes worth most
≈ 40 pagesDelivered within 3 hours
Most popular
Premium

The full diagnosis and the plan

  • Every screen, every finding, every flow
  • All 60 laws with evidence and fixes
  • 8 strategy chapters and a 90-day roadmap
≈ 95 pagesDelivered within 24 hours

Researched from your live product and fact-checked against the evidence.

A 7-day plan from vibe coded app to launched product

  1. Day 1

    Freeze and check

    Stop adding features; run the pre-launch checks above.

  2. Day 2

    Own the address

    Upgrade to the plan with a custom domain; remove builder branding.

  3. Day 3

    List it

    Create your Launchpad listing; read the free baseline diagnosis.

  4. Day 4

    Five watched users

    Give five people the core task; say nothing; note where they stall.

  5. Day 5

    Fix, by prompt

    Turn each stall into one specific prompt; re-test with a new account.

  6. Day 6

    Tell your communities

    Post where your users are, linking to your Launchpad page.

  7. Day 7

    Go wider

    Product Hunt, Indie Hackers or Show HN, depending on your audience.

Mistakes to avoid

Checklist: Mistakes to avoid — Launching the demo; Leaving keys in the front end; Sharing a link that expires; Prompting instead of watching; Hiding what the AI does; Ending on a dead end.
Mistakes to avoid
  • Launching the demo — a flow that works for you, signed in as admin, isn't proof it works for a new account
  • Leaving keys in the front end — ask your tool to list every secret and where it's stored
  • Sharing a link that expires — free published links and preview URLs change or vanish; launch on a permanent page
  • Prompting instead of watching — five watched users beat fifty new features
  • Hiding what the AI does — tell users what the AI can get wrong and how to check it
  • Ending on a dead end — a confusing last step colours the whole visit

That last one is the peak-end rule: people judge an experience mostly by its most intense moment and its end, so make the first success screen and the sign-off clear.

Ready to launch?

How we know

Tool plans and limits come from each vibe coding tool's own pricing page or documentation, read on 20 November 2026. The pre-launch checks are standard web-app practice for authentication, data access, secrets and speed, not results from testing specific apps. The Launchpad's terms come from its homepage (20 November 2026) and its investigation and pricing pages (18 November 2026). Search volume is Google Keyword Planner's global 12-month average. Science of Apps runs the Launchpad and has no relationship with the tools named.

Key terms, defined

  • Vibe coding: building software by describing it to an AI and iterating on the result without reading every line.
  • Vibe coded app: an app built mainly through vibe coding.
  • Vibe coding tools: prompt-to-app builders and AI code editors such as Lovable, Bolt.new, Replit, v0 and Cursor.
  • Happy path: the flow a user takes when everything goes as expected.
  • Database rules: settings that decide which signed-in user can read or change which data.
  • Permanent listing: a public product page that stays live and findable after launch day.

Frequently asked questions

How do you launch a vibe coded app?

Freeze the scope, then run five checks: sign-up and sign-in, error and empty states, secrets and data access, speed on mobile, and any AI output users rely on. Move it to your own domain, create a permanent product page such as a free Science of Apps Launchpad listing, watch five people use it, then share it on Product Hunt, Indie Hackers and your communities.

What is vibe coding?

Vibe coding means building software by describing what you want to an AI and iterating on what it produces, without reading every line of code. It's excellent for prototypes, internal tools and first versions of products. Production apps still need review of security, data handling and edge cases, which is what this playbook's pre-launch checks cover.

What are the best vibe coding tools?

Prompt-to-app builders such as Lovable, Bolt.new, Replit, v0, Base44 and Emergent produce a hosted app from a description; AI code editors such as Cursor suit people who'll read the code. For launching, the tool matters less than whether it supports a custom domain, code export and a real database on the plan you can afford.

Is a vibe coded app safe to launch?

It can be, once you check it. The common risks in a vibe coded app are API keys exposed in front-end code, database rules that let any signed-in user read everyone's data, and missing input validation. Ask your tool to audit for these, test with a second account, and get a developer review if you handle payments or personal data.

How do I get users for my vibe coding app?

Start with a permanent public page, so every mention points somewhere stable: a free Launchpad listing is found by the problem your app solves. Then go where your users already are: communities, Product Hunt, Indie Hackers, Show HN for technical products. Five watched users before the wide launch will tell you more than fifty silent visits.

Should I tell users my app was vibe coded?

There's no rule that you must, and users mostly care whether it solves their problem. Be honest if asked, and be especially clear about anything AI does inside the product: what it can get wrong and how users can check. Among builders, on Indie Hackers or Show HN, the build story itself can be part of the launch.

What does the Launchpad check on an AI-built app?

A free baseline diagnosis of your landing page, discoverability and speed runs as your listing goes live. The full investigation covers 22 areas from first visit to payment, with 39 automatic measurements in a real browser on desktop and mobile and 74 expert checks, analyst-reviewed and private. For AI products it adds prompt and output trust checks.

Sources

  1. Lovable — Documentation: Welcome to Lovable (checked 20 Nov 2026)
  2. Bolt — Pricing (checked 20 Nov 2026)
  3. Replit Docs — Starter Plan (checked 20 Nov 2026)
  4. v0 by Vercel — Homepage and pricing (checked 20 Nov 2026)
  5. Cursor — Pricing (checked 20 Nov 2026)
  6. Google — PageSpeed Insights (checked 17 Nov 2026)
  7. Product Hunt — Homepage (checked 16 Nov 2026)
  8. Indie Hackers — Homepage (checked 17 Nov 2026)
  9. Hacker News — Show HN (checked 16 Nov 2026)
  10. Science of Apps — Launchpad (checked 20 Nov 2026)
  11. Science of Apps — Product investigation (checked 18 Nov 2026)
  12. Science of Apps — Pricing: free listing and reports (checked 18 Nov 2026)
  13. Checked November 20, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

The missing step after vibe coding is the launch: a free, permanent product page on the Science of Apps Launchpad, real users, and a test of the live app end to end, with prompt and output trust checks for AI products.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition