Mobile App Beta Testers Needed
Budget: $750 – $1,500 USD
Looking for an experienced QA / app-testing provider (agency or coordinated team) to run a structured closed beta of a finished youth sports management mobile app on BOTH Android and iOS. This is functional QA testing only — NOT development. The app is built and deployed; I need it thoroughly tested, with defects documented and verified, before public launch.HARD REQUIREMENTS — please do not bid unless you meet ALL of these:
15 individual testers, each with their OWN real Google account and Apple ID, on their OWN physical Android and iOS devices (not emulators, not one account across many devices). These 15 must be able to stay enrolled in a Google Play closed-testing track for 14 continuous days.
Demonstrated mobile-app QA experience testing apps built by someone else. In your bid, describe 2 specific QA engagements (what the app was, what you tested, how you reported bugs). Web-development/design portfolios are not relevant.
A structured bug-reporting process — severity levels, steps to reproduce, device/OS, screenshots/recordings. Name your tool (Jira, TestRail, spreadsheet, etc.).
A documented spread of devices and OS versions — include your device matrix.
WHAT'S TESTED:
Functional testing across multiple user roles and a broad feature set (scheduling, messaging, registration, payments in sandbox mode, media, live features).
Edge cases / error handling: empty states, invalid input, network loss, long text, boundary values.
Localization checks (multiple languages, including right-to-left).
Offline behavior and sync.
Clear, reproducible defect reports plus a final summary by severity.
HOW IT WORKS:
Testing is against a dedicated environment with synthetic data only and payments in sandbox mode — no production systems, no real user data.
No source code is provided. Black-box testing only.
A signed NDA is required before any access or builds are shared.
YOUR BID MUST INCLUDE (bids that skip these will be declined):
(a) Confirmation you can field 15 testers with their own Google/Apple IDs and devices for a 14-day closed test — and whether they're your own staff or a recruited panel.
(b) The 2 mobile-QA examples from requirement 2.
(c) Your bug-reporting process and tooling.
(d) Your device/OS matrix.
(e) A fixed-bid price (preferred) or hourly with a cap, plus a realistic timeline.Please answer (a)–(e) directly. Generic "we can do this" pitches or development offers will be ignored.
15 individual testers, each with their OWN real Google account and Apple ID, on their OWN physical Android and iOS devices (not emulators, not one account across many devices). These 15 must be able to stay enrolled in a Google Play closed-testing track for 14 continuous days.
Demonstrated mobile-app QA experience testing apps built by someone else. In your bid, describe 2 specific QA engagements (what the app was, what you tested, how you reported bugs). Web-development/design portfolios are not relevant.
A structured bug-reporting process — severity levels, steps to reproduce, device/OS, screenshots/recordings. Name your tool (Jira, TestRail, spreadsheet, etc.).
A documented spread of devices and OS versions — include your device matrix.
WHAT'S TESTED:
Functional testing across multiple user roles and a broad feature set (scheduling, messaging, registration, payments in sandbox mode, media, live features).
Edge cases / error handling: empty states, invalid input, network loss, long text, boundary values.
Localization checks (multiple languages, including right-to-left).
Offline behavior and sync.
Clear, reproducible defect reports plus a final summary by severity.
HOW IT WORKS:
Testing is against a dedicated environment with synthetic data only and payments in sandbox mode — no production systems, no real user data.
No source code is provided. Black-box testing only.
A signed NDA is required before any access or builds are shared.
YOUR BID MUST INCLUDE (bids that skip these will be declined):
(a) Confirmation you can field 15 testers with their own Google/Apple IDs and devices for a 14-day closed test — and whether they're your own staff or a recruited panel.
(b) The 2 mobile-QA examples from requirement 2.
(c) Your bug-reporting process and tooling.
(d) Your device/OS matrix.
(e) A fixed-bid price (preferred) or hourly with a cap, plus a realistic timeline.Please answer (a)–(e) directly. Generic "we can do this" pitches or development offers will be ignored.