All posts

Beta test a web app: share a link, get real feedback

· 8 min read

A web app is the easiest kind of app to beta test. There is no store, no review and no install. You send a link, and the tester is in. That is also the trap. Because it is so easy, most makers skip the setup, and then the beta goes wrong in small ways. The tester lands on your real data. The link stops working on Tuesday. The page they see is last week's version. This post shows how to share a web app link that is safe, stable and easy to test, and what to ask testers to send back.

Why a link is easy, and easy to get wrong

These are the problems I see most with web betas:

  • Testers touch live data. If you share your production URL, a tester who clicks "delete" deletes something real. A tester who fills in a form fills your real database with junk.
  • The URL changes. Some preview links are tied to one build and one build only. If you push a fix, the tester may still be on the old build, or the link you sent may point at something you did not mean.
  • Old files in the cache. A tester opens your link on Monday and again on Wednesday. Their browser may show the old version. They report a bug you fixed two days ago.
  • Logged-in state. You are always signed in on your own browser. A tester is not. The first screen they see is the sign-up or login screen, which you may not have looked at for months.
  • Real payments. A tester who reaches your checkout should not be able to be charged.

None of this is hard to fix. It just needs to be done before you post the link.

Get a stable test URL

If you host on Netlify or Vercel, you already get test URLs for free, as part of normal deploys. I read the current docs of both on 11 November 2026. Here is what they say.

Netlify

Netlify's Deploy Previews page says a preview for a pull request has the prefix deploy-preview followed by the number of the pull request. Its example is deploy-preview-42--mysitename.netlify.app. Every deploy also gets a permalink that starts with the deploy ID, and the page says "The contents of this URL never change, even after you redeploy your site." That is the link to use when you want testers to see one exact build.

The Branch deploys page says a branch called staging deploys to staging--mysitename.netlify.app. The page says "a branch deploy persists as long as the branch exists", and the URL follows the branch name, so it stays the same while you push fixes to that branch. For a beta that runs for a week or two, a branch like beta gives you one link you can put in your test task and keep.

Who can open these links? The Deploy Previews page does not say outright that they are public. It does say Netlify adds a noindex header to Deploy Previews, which keeps them out of search results but does not stop anyone who has the link. The Branch deploys page says the most recent deploy of each branch does not get that header, so it can be indexed by search engines. To control access, Netlify has Password Protection. The page says "You can configure protection for all site deploys or only Deploy Previews and branch deploys." It also says basic password protection for your whole site is available on Pro plans, and that it is not available on Credit-based Free and Personal plans. The option to protect only previews and branch deploys, and leave production open, is listed as Enterprise only. Plans change, so check the page for yours before you plan around it.

Vercel

Vercel's Environments page says Vercel creates a preview deployment by default when you push a commit to a branch that is not your production branch, open a pull request, or deploy from the CLI without --prod. It describes two kinds of preview URL. A "Branch-specific URL" always points to the latest changes on that branch. A "Commit-specific URL" points to the exact deployment of that commit. Use the branch one for a beta, so the link stays the same while you fix things.

One gotcha from the same page: the first deployment of a new project is always a production deployment, even if you deploy it from another branch. So do not assume your very first deploy is a safe preview.

Vercel's Deployment Protection page and the Environments page say new projects start with Standard Protection and Vercel Authentication, unless your team set a different default. That means a visitor to a preview must log in with a Vercel account that has access to the project. Your production domains stay public. This matters for a beta: your testers do not have a Vercel account on your project. The Environments page says that to share a preview with someone outside your team you can approve their access request or send them a Shareable Link. The Deployment Protection page also lists Password Protection, which it says is available on Pro for a fee per protected project, included on Enterprise, and not available on Hobby. Check that page for the current price and plan, because they may change.

If you host somewhere else

Any host can do the same job. What you need is one URL that stays the same for the length of the beta, that is not your production site, and that you can switch off afterwards. A staging subdomain works well.

Test data, not live data

Your test URL should talk to a test database, or at least to a separate set of test records. On Vercel, the Environments page says preview deployments use the variables you scope to the Preview environment, not the Production ones. So you can point Preview at a test database. Check your host's docs for how it handles this, as it differs by provider.

Then make a seed account, so the tester does not have to guess:

  • Fill the test database with a little sample content, so the first screen is not empty.
  • Make one throwaway login with a simple password. It should have no link to a real person.
  • Turn off anything that sends to real people: emails, SMS and push notifications. If you cannot turn it off, say so in the task.

Payments

If your app takes money, keep testers in Stripe's testing environment. Stripe's testing page says sandboxes let you test without making actual charges or payments, and it says "Test card numbers are only valid in sandboxes." What you use in your code is the test API keys, not the live ones. The page also says objects in one mode are not available in the other, so a test product cannot be part of a live payment. Stripe's older name for this was test mode, and the page still uses that name for the legacy kind. Tell testers they can use a test card and that no money will move. Stripe's page links to the list of test card numbers.

Which browsers and screens to cover

You cannot test everything, and I won't claim a market share number, because I did not find one I can trust. Cover three things, and you will find most of the problems:

  • Safari on an iPhone. Apple's App Review Guidelines, section 2.5.6, say "Apps that browse the web must use the appropriate WebKit framework and WebKit JavaScript." The same line says you may apply for an entitlement to use another browser engine, and the page links this to the EU and Japan. So in general, a browser app on an iPhone runs on WebKit too, with that exception. For you this means one iPhone test covers more than just Safari. Behaviour can still differ between browsers, so I would not rely on it for everything.
  • Chrome on Android. This is the other big phone case. Layout, keyboards and file pickers can all behave differently from iPhone.
  • One desktop browser. Pick the one you do not use for building.

Then check small screens. MDN's page on the viewport meta tag explains the classic mistake. Without the tag, it says pages on a phone "might be rendered with a virtual viewport of 980px", for example on a 640px screen, and then shrunk down. The recommended tag is <meta name="viewport" content="width=device-width" />. If your app looks tiny on a phone, check this first.

You do not own every phone. See testing on phones you don't own for how testers help here.

What to put in the test task

A web app test task needs a few more things than a store app. For the general method, read how to write a test task. For a web app, add:

  1. The URL. The stable test link, not production.
  2. A test login. The throwaway account, with the password in plain text.
  3. One clear job. "Sign up, add one item and share it", not "have a look".
  4. What is out of scope. "The billing page is not finished", "ignore the admin area".
  5. "Please use your phone." Most of your gaps will show up there.
  6. Ask for browser and device. "Tell me which browser and which phone or computer you used."

An example: "Open the link on your phone. Log in with the test account. Add one item and open it again. Ignore Settings. Tell me your browser and device, and anything that looked wrong."

If you are still looking for testers, see how to find beta testers for your app.

Collecting errors

The best clue for a web bug is the browser console error. Google's Chrome DevTools Console reference says you open it with Control+Shift+J on Windows and Linux, or Command+Option+J on a Mac. It also says "The Console automatically captures stack traces for errors and warnings." So a tester on a desktop can open the Console, copy the red error and paste it into the review.

On a phone this is harder, and I did not verify a simple way for a tester to see the console there. So ask for what they can do: the exact words of any error on screen, what they tapped just before, and their browser and device. For the full list of what a good report holds, see bug reports testers can act on.

You can also add an error-tracking tool to your test site. It records the errors that testers hit, even when they do not report them. Pick any tool you like, as long as you turn it on for the test site only and read the errors before the beta ends.

After the beta

  • Turn off or protect the preview links. Delete the beta branch, or put a password on it. Old preview links stay reachable until you do.
  • Delete test accounts and any data testers made.
  • Rotate the test password if you reused it anywhere. You should not have, but check.
  • Remove the link from your test task. A dead link in your app listing looks bad.
  • Go back to testers. Thank them, and tell them what you changed.

The web beta checklist

  1. Is the test URL stable, and not your production site?
  2. Is the test URL protected, or are you sure you are fine with anyone who finds it opening it?
  3. Does the test site use a test database, with sample data?
  4. Is there a throwaway test login that works?
  5. Are real emails, SMS and push turned off, or mentioned in the task?
  6. If you take payments, is Stripe on test keys, and do testers know to use a test card?
  7. Did you open the link on an iPhone, an Android phone and a desktop browser yourself?
  8. Does the page have a viewport tag, and does it look right on a small screen?
  9. Did you test a first visit, with no login and no cache?
  10. Does the task have the URL, the login, the one job, what is out of scope and "use your phone"?
  11. Does it ask for browser and device, and for any error message?
  12. After the beta, are the preview links off or protected, and the test accounts deleted?

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. When you post an app, you choose a platform (web, iOS or Android) and add a URL. The form describes the URL as a site, TestFlight or store link. You add a one-line pitch and a one-sentence test task, and there is an optional box for test credentials and access notes. That box carries a warning: use a throwaway test account, because every signed-in user can see it. So do not put a real password there.

A review has two public parts: a first impression and UX, and what is missing or what to improve. There is also an optional private "Bugs / security" box that only the maker sees, with a limit of 2,000 characters. The review form takes text only, with no attachments, so ask testers to paste the console error or describe what they saw. The maker then rates the review.

Try it

Make a test link and a throwaway login today, then open it on your own phone. Fix what you see. Then post your app on TestSwap with a clear test task, and review someone else's app first to see how it feels. Tell me what's missing or broken (@dizid on X).