Make a beta signup form for your app's testers
Build a beta signup form that asks for email, platform, intended use and whether testers will give feedback. Free, built and edited in chat, shared by link.
Join the waitlist
Be the first to know when we launch.
This is a real form: answer it the way a visitor would. Nothing is saved.
Use this template Describe yours in chatOpen full screenMore to start from: all form, quiz and course templates. Nothing is published until you press Publish, and every answer lands in your account with charts and a CSV.
Beta sign-ups go wrong when the form only collects an email, so you end up with testers who never install the build or who use it in ways you can't reproduce. This page builds a form that asks the questions that decide who you invite: platform, how they would actually use the app and whether they will report problems. The live sample above is a general waitlist; the chat adapts it to your app and your test plan.
What you get
Device-specific follow-up questions
Show the operating system question only to people who pick iPhone or Android, so a Mac user is not asked for an Android version. Each response is also emailed to you, so you can send invites to the right people the same day.
Logic and pages
Show a follow-up only when it applies, split a long form into pages, or show one question per screen.
Results you can read
A chart for every question, averages and NPS for scales, the order of a ranking, a table of every answer and a CSV.
How it works
- Step 1
Try the sample above, then press Use this template, or describe your own form to the chat.
- Step 2
Change any question by hand or ask the assistant ("add a question about price", "translate it to Spanish"), with a live preview.
- Step 3
Publish, share the link or QR code, and read the answers as they arrive. You get an email for each one.
Who uses it
Solo developer launching a first TestFlight or Play beta
You need about 30 testers across iPhone and Android. Ask for platform and device model first, then invite people until each group has enough coverage, and close the form when you reach your number.
Small startup running a closed beta with limited slots
Use a response limit so the form stops accepting sign-ups once you have the number you can support. Ask how each person plans to use the app, so you invite testers whose workflows match the features you most need checked.
Product team recruiting for a specific feature
Add a question about current tools and how often they do the task your feature targets. Testers who do that task weekly will report more useful feedback than people who signed up out of curiosity.
Questions
How many testers should I accept?
That depends on how much support and feedback you can handle in the first weeks. Set a response limit on the form so it closes at your target, and keep a waitlist question so people you turn away can still be contacted later.
Should I ask for a phone number or social profile?
Usually not. An email is enough to send an invite and a build link, and each extra field lowers the number of people who finish. Only ask for something you will actually use during testing.
Can I ask testers to agree to give feedback?
Yes, with a yes/no question or a consent block that says what you will ask them to do. A yes does not guarantee feedback, so pair it with a question about how much time they can spend testing.
Does the form send invites or add testers to TestFlight automatically?
No. Each response is emailed to you, and you add testers to TestFlight, Google Play testing or your own download page yourself. The form collects and sorts the sign-ups; it does not manage the build.