Most people picture a launch as one day: a post on Product Hunt, a burst of visitors, then quiet. For a first app, the day matters less than the weeks around it. What you fix before you share the link decides whether visitors stay, and what you do after decides whether anyone comes back.
What does it mean to launch an app?
Launching means making your app public and telling the people it’s for. Publishing is the technical part: your app has an address anyone can open. Launching is everything that makes strangers find it, trust it and sign up. You can publish in a minute. A launch takes a few weeks of small, repeatable steps.
Before you tell anyone
Visitors give a new app one look. Check at least these basics first:
- Your own domain.
bloomly.examplelooks like a real product,bloomly.lovable.applooks like a test. Lovable, Base44 and Bolt need a paid plan to connect one. - Google can read your page. Many AI-built apps send search engines an almost empty page. See why your app isn’t showing on Google.
- A clear headline. A stranger should know in five seconds what it is and who it’s for. See why visitors leave without signing up.
- A link preview. When you paste your link into a chat, it should show a title, a sentence and an image. Check it with the Open Graph preview.
- Nobody can read other people’s data. Sign in as two test users and make sure neither sees the other’s records. Our security guide explains what to check.
- Sign-up emails arrive. If they land in spam, people never finish signing up. See why sign-up emails go to spam.
- Analytics. Without it you can’t tell which post brought your first users.
The free LaunchPal check covers most of these in about a minute. For the full list, use the website launch checklist.
How to launch a web app you built without coding
If you built with Lovable, Base44, Bolt, Replit or v0, your app already runs on the web. Launching it is mostly settings, not code:
- Publish it publicly. Apps behind a login or published as private can’t be found.
- Connect your domain. Custom domains need a paid plan on Lovable, Base44 and Bolt. Redirect the builder’s address to your own, so the same app doesn’t live at two addresses.
- Add your site to Google Search Console and submit your sitemap. Then add it to Bing Webmaster Tools.
- Run a check and fix what’s red before you share the link.
Each builder handles a different part of this for you. Our launch checklists show what yours does and what it leaves to you.
How long does it take to launch an app?
A web app can be ready to share within days of publishing. Most of that time goes into the basics above, not into waiting.
The app stores add their own steps. Apple says its review typically handles half of submissions within 24 hours and 90% within 48 hours. Google Play asks new personal developer accounts to run a closed test with at least 12 testers for at least 14 days before going live. So a first Android release takes at least two weeks.
The launch itself is the first month after that. Expect the first week to bring feedback, and the following weeks to show which places actually bring users.
How much does it cost to launch an app?
A web app can launch on very little:
- A domain, usually a yearly fee that depends on the ending you choose.
- Your builder’s paid plan, if it’s needed for a custom domain. Base44’s cheapest plan with a domain was $16 a month on annual billing in October 2026, for example. Check your builder’s pricing page, because these change often.
- Email sending for sign-up emails, which many providers offer free at low volumes.
Launch sites vary: Product Hunt is free to post, while BetaList only takes paid submissions. Native apps cost more to list: the Apple Developer Program is $99 a year, and a Google Play developer account is a one-time $25.
How to market your app before launch
You don’t need an audience before launch, but a few things make launch week easier:
- A waitlist page with one clear promise and an email field, so interested people have somewhere to go.
- Talk to ten people who have the problem. Their words make your headline better than any copywriting trick.
- Share what you’re building. Short, honest updates with real numbers find early supporters. See what to post when you build in public.
Launch week: where to tell people
Start where your users already talk, not where other makers hang out. For Bloomly, a plant-care app, that’s plant subreddits, a houseplant Discord and a gardening forum, not Product Hunt. Answer questions there first, and mention your app only where it really helps.
Launch sites still help with feedback and your first links. Pick them by stage: where to launch your app compares Product Hunt, BetaList, Uneed and others.
Tag every link you share, so your analytics shows which post each visitor came from. A link like bloomly.example/?utm_source=reddit&utm_campaign=launch is enough.
After launch: the first 30 days
The weeks after launch decide whether the first visitors turn into users:
- Week 1: fix whatever confused your first visitors. Read every message and watch where people stop.
- Weeks 2–3: go back to the one or two places that brought sign-ups. Skip the rest.
- Week 4: look at your numbers. What brought visitors, how many signed up, and what you’ll do more of next month.
For the full plan, read the product launch strategy for first-time founders. For finding people, read how to get your first users.
Your launch checklist
- Published publicly, on your own domain
- Google can read your pages, and your sitemap is submitted
- A headline a stranger understands, and a working link preview
- Test users can’t see each other’s data
- Sign-up emails reach the inbox
- Analytics on, and tagged links for every post
- Two or three places picked where your users already talk