Test on real devices
Match your Roast with the platforms and devices your app needs.
Real people. Real devices. Structured feedback. Test your app with the community — or build your reputation as a Roaster.
Follow participants, tasks, and findings in one focused round.
Try the menu and cards. This sample data is illustrative and is not saved.
Explore new tests, compare the effort and device needs, and join a round that fits.
Check Discover again soon, or open a test round for your app.
See who joined, what they completed, and which findings need your attention.
See participants, devices, and completed tasks in each round.
Keep assigned tasks and test results together so the next step is clear.
Review findings with context, respond, and carry the learning forward.
iPhone 15 · Attach photo
Context stays with the finding
One shared status for everyone
Bring your beta to people who test with purpose. Every step is designed to turn a test session into a clearer next release.
Match your Roast with the platforms and devices your app needs.
See task outcomes, reproducible bugs and actionable feedback together.
Follow participation and results from one focused dashboard.
Roasters build a visible record through completed contributions.
Start a community test, follow real progress and turn the feedback into your next improvement.
Define the app, devices, and tasks before opening a test round.
Create a note, attach a photo, then find the note again.
Required devicesBuild something? Test something? There is a place for both here.
Get clear, actionable feedback before your release.

Test promising apps and build a visible testing history.

Explore stories from builders and testers that show how clear findings can guide the next release.
The report showed the exact step where the flow broke, the device used, and what happened next. That is the context I need to fix a beta quickly.
I knew which tasks mattered and could share a finding without guessing what the developer wanted. The whole test felt focused.
A screen looked fine in our simulator, but a smaller phone exposed the confusing step. Device context changed how we prioritized the fix.
I can see who joined, which tasks are complete, and what findings need attention. Nothing disappears in a long message thread.
When everything worked, I could say so with the device and tasks recorded. A clear pass is more useful than silence.
Instead of asking testers for updates one by one, I can review task progress in one place and spend that time improving the app.
The structure prompted me for steps, expected behavior, and the actual result. My report became much easier to understand.
The test surfaced a confusing permission screen that our team had stopped noticing. A fresh perspective made the next build clearer.
I can see my completed work in one profile. It feels good to know that a thoughtful test leaves a record.
We asked people to try the new onboarding flow before polishing the rest. Focused tasks made the responses far more useful.
The brief told me what to install and what to try. I could focus on using the app rather than learning a complicated process.
The findings did not end in a spreadsheet nobody reopened. They stayed tied to the Roast, ready for the next round of fixes.
Coordinate the people, tasks and timeline behind your Google Play closed test. Google makes the final production-access decision.
Clear answers before you publish a Roast or join one.
Still have a question? Contact usA Roast is a focused beta test. The developer shares a build, chooses the devices they need and writes the tasks. Roasters complete those tasks and submit their findings.
Create a profile, add your device and browse open Roasts. You can join a Roast when your device matches its platform and a spot is available.
That is useful information too. Complete the required tasks and submit a “No issue found” result with any context that helps the developer understand what you tested.
No. BetaRoast helps coordinate real testing and collect feedback. Google makes the final decision about production access under its own policies.
Yes. Developers can create Roasts for iOS, Android or both, and specify the devices they want to hear from.