Describe bugs and ideas
Voice becomes a structured draft for a bug, idea or requested change. The person reporting it reviews the text before submitting.
TesterPayKit connects what a tester reports with the work that follows. Start with participants you already know.
Voice becomes a structured draft for a bug, idea or requested change. The person reporting it reviews the text before submitting.
Depending on the SDK and configuration, device information, session events, screenshots or recordings support the report. Not every report contains every format.
Describe the test, collect applications and choose suitable participants. Accepted applicants receive a single email with their task link.
Use feedback assignments with a link and questions for ideas or websites. Responses stay associated with the assignment.
Turn a report into a concrete task and record the retest verdict. Accepting a result remains a deliberate decision.
CLI and MCP bring tasks and reports into your development workflow. AI support does not replace human feedback or your review.
Flutter, Expo and Web/React packages are published; Swift for iOS/macOS is available as early access on request. Configure integration and data collection for each project.
Your participants use their own devices. Model, OS and language coverage depend on the people actually taking part.
Review SDK settings and shared content for your test. The privacy information explains data processing and involved services.
Describe what to try and the feedback you need.
Share the task with your team, friends or community. Review applications and select suitable people.
Testers give feedback. You work through reports and ask them to check specific changes.
Tell us your audience, devices, language and timing. We check whether suitable people can be recruited. We do not currently promise an immediately available tester pool, fixed recruitment times or a guaranteed participant count.