Cross-platform beta testing, one pool

The problem with beta testing today

Beta testing for a cross-platform app means juggling TestFlight for iOS, Google Play Internal Testing for Android, maybe Firebase App Distribution for a web build, and a spreadsheet to keep track of who is testing what. Testers sign up through different channels. Feedback comes in through email, Slack, Discord, and DMs. Nobody knows which device anyone is using.

It works when you have five testers. It falls apart at twenty. By the time you reach a hundred, you are spending more time managing the process than reading the feedback.

How Pools handles it

You create a beta testing pool. You invite testers or let them apply. Each tester fills in their device profile: what phone they use, what OS version they are on, what tablet or desktop they have access to. That information lives in the pool, not in a spreadsheet you will lose.

When you have a build ready, you publish a test task. The task has a description, milestones (install the build, complete onboarding, trigger the payments flow), and a deadline. You can target the task to testers who match specific criteria—iOS 17 and above, Android tablets only, whatever the build needs.

Testers work through the milestones and attach proof: screenshots, screen recordings, logs. You review each submission in one place. When a tester completes a task reliably, their reputation score goes up. When they go silent or submit low-effort proof, the system flags it.

What you get

• Device and OS profiling — Every tester lists their devices, operating systems, and versions. Filter your pool by hardware when assigning tasks.
• Milestone tracking — Break test tasks into concrete steps. See who has completed what, who is stuck, and who has not started.
• Proof review — Testers attach screenshots, screen recordings, or logs to each milestone. Review and approve without leaving the platform.
• Reputation scoring — Testers build a track record over time. Completion rate, proof quality, and responsiveness feed into a reputation score you can sort and filter by.
• Cross-platform enrollment — One pool covers iOS, Android, web, and desktop. No separate lists per platform.
• Automatic warnings — Testers who miss deadlines or go unresponsive get flagged. You decide what to do about it.
• Pool chat — A built-in channel for each pool so testers can ask questions and report issues without switching to another tool.

Built for small teams

Most beta testing tools are built for enterprise QA departments with dedicated test managers and procurement cycles. Pools is not. There are no enterprise contracts, no per-seat pricing, and no sales calls required to get started.

It works the same for a 10-person beta as it does for 500. A solo developer shipping a side project and a team of eight preparing a production release both get the same tooling. The pool scales with you.

Frequently asked questions

How is this different from TestFlight or Google Play Internal Testing?

TestFlight and Google Play Internal Testing handle build distribution for a single platform. Pools handles the people. You manage one list of testers with their device profiles, assign test tasks with milestones, review proof of completion, and track reputation across every platform your app ships on.

Can I use Pools alongside TestFlight and Google Play Internal Testing?

Yes. Pools is not a build distribution tool. You still use TestFlight, Google Play Internal Testing, or whatever system you prefer to ship builds. Pools manages the tester side: who is testing, on what device, what they need to do, and whether they did it.

What does device and OS profiling mean in practice?

Each tester in your pool has a profile listing their devices, operating systems, and OS versions. When you create a test task that requires iOS 17 on an iPhone 15, you can filter your pool to find testers who match. No more guessing who has what.

How does milestone tracking work?

You define milestones for each test task: install the build, complete onboarding, trigger a specific flow, reproduce a bug. Testers check them off and attach proof (screenshots, screen recordings, logs). You review and approve each one.

What is reputation scoring?

Testers earn a reputation score based on task completion rate, proof quality, and responsiveness. Over time, you can see which testers are reliable and prioritise them for future rounds. Testers who go silent or submit low-effort proof get flagged automatically.

Is there a minimum pool size?

No. Pools works the same whether you have 5 testers or 500. There is no per-seat pricing and no minimum commitment. You pay for the pool, not the headcount.