How to Launch a Web App for Free: No Store, So the Page Does the Work
A web app has no store to approve it and none to feature it, so the launch is a deployment plus a page. Ship it in slices you can switch off, let a visitor try it before creating an account, make shared links preview properly, and test the first visit on the browsers and phones your users really have. Then publish it on free boards and in communities.
What changes when no store stands between you and users?
An app in a store gets two things you do not: a review that catches obvious faults before the public sees them, and a place where people browse. A web app gets neither. Anyone with the address can use it within seconds of your deploy, and nobody will find the address unless you put it somewhere. Your launch is therefore a deployment you control and a page you have to distribute.
The upside is speed. You can fix a bug at lunch and everyone has the fix at once, with no waiting on review. The cost is that you must supply the discipline a store would otherwise supply.
How do you keep a live launch safe to change?
- Feature flags on anything risky. If the new checkout breaks, turning it off should take a minute and no deploy.
- A staging address that mirrors production, so launch day is not the first time the real configuration runs.
- Error reporting you read daily. In the first week, an error you did not hear about is a user you lost without knowing.
- A rollback you have practised, meaning you have done it once on purpose, not only written it in a note.
Do a dry run with five people on the production address a day before you announce. They will hit the problems your own testing cannot, such as a field that rejects a name with an apostrophe.
Should visitors create an account before they try it?
Let them see it work first. A visitor on a new site has no reason yet to trust you with an email address. Offer a demo workspace with sample data, a sandbox they can edit, or a first action that needs no sign-in, then ask for the account when they want to save something. The same applies to Show HN, whose guidelines ask for something others can try without friction, ideally with no sign-up or email.
| Approach | Effort | Best for |
|---|---|---|
| Sample data already loaded | Low | Dashboards and tools that organise information |
| A guest session that expires | Medium | Apps where the user creates something |
| An interactive tour on a demo workspace | Medium | Apps with many parts to learn |
| A recorded walkthrough beside the sign-up button | Low | Anything that is slow or costly to demo live |
What makes a web app findable and shareable?
Three small jobs cover most of it. First, give each shareable page a title, a description and a preview image so that a pasted link looks like something in a chat or a feed; the Open Graph image specs list the sizes. Second, give the public landing page real text that describes the job, because an app behind a login gives a search engine nothing to read. Google documents SoftwareApplication structured data for showing app details in search results, and its page explains the properties and a way to test them.
Third, consider making it installable. MDN’s guide to making a web app installable lists what a browser looks for. An installable web app can sit on a home screen without a store, which is the cheapest route to a mobile presence. The website pre-launch SEO checklist covers the rest of the search side.
How do you test the first visit before strangers arrive?
- Open the landing page on a mid-range phone on a mobile connection, not your development machine. Time how long it takes before you can do something.
- Load the app in the two browsers your audience uses most, and in a private window with no extensions.
- Complete the first task as someone who has never seen it. Write down every moment you hesitate.
- Try to break the sign-up with a long name, an empty field and a pasted email with spaces.
- Send the link in a chat and in an email to see what the preview looks like.
That list takes an hour and finds more than a week of feature work.
Where do you point people once it is ready?
Start with a free page on the launch board, which needs no queue and goes live when you press Publish on the link in one confirmation email. Add the community where the problem is discussed, and read the web app places for directories. Use the guide to web app ideas if you are still deciding what to build, and the board’s developer tool ideas for concepts of the technical kind.
Measure the first visit, not the pageviews: how many people reached the first useful action, how many came back within three days and where the errors happened. Tag every link you share, as the UTM checklist describes, so each source has its own line.
Frequently asked questions
Does a web app need an app store listing?
No. A web app is reached by address, so you can launch the moment it is deployed. Stores add discovery and a review step, but they also add rules and fees. If you later want a presence on a phone’s home screen, an installable web app is one route that avoids a store.
How do I get users for a new web app?
Put it where people already talk about the problem, and make the first use possible without an account. Publish a page on a free launch board, post in a relevant community describing the problem first, and write one page that answers the question your buyer would search for. Measure each source with tagged links.
Do I need a landing page separate from the app?
Usually yes. An app behind a login gives search engines and launch sites nothing to read. A public page with the job, an example and a way to try it is what you share. It can be a single screen in the same codebase as long as it works without signing in.
What should I test before launching a web app?
Open it on a mid-range phone, in two browsers and in a private window, complete the first task as a stranger and try to break the sign-up form. Add error reporting and a rollback you have practised. Do a dry run with five people on the live address a day before you announce.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.