Android App Testing Manager Needed
Budget: $30 – $250 USD
# Recruit & manage 12 genuine Android testers for a 14-day Google Play closed test (onboarding & navigation QA)
**Category:** Mobile App Testing / QA / User Testing
---
## About the app
Our new app is a German-language community app for the district (Bezirk) of Einsiedeln, Switzerland. It is a **modular platform**: users log in, complete a short onboarding, and then discover and subscribe to individual **modules** — e.g. a local **event calendar**, **clubs & associations**, **tourism**, **restaurant reservations**, **defect/issue reporting to the municipality**, **public-transport departures**, and the **lido (Badi)**. The app is built for Android and is currently in **Google Play closed testing**.
The app is **not yet publicly live**, so we are **not** asking you to test the real content inside the modules. The focus is the app shell and user flow.
## What we need
Google requires **12 testers opted in continuously for 14 days** before we can promote the app to production. We are looking for a professional testing provider who can **recruit and manage 12 legitimate testers**, get them opted into our closed-testing track, keep them opted in for the full 14 days, and collect structured feedback.
We need **real people who actually install and use the app** and report what they experience — not passive opt-ins.
## In scope (what to test)
1. **Onboarding** (top priority): first launch, account creation / login, any interest/persona selection, and the initial guided setup. We want to know where users get confused, stuck, or drop off.
2. **Navigation between modules**: moving around the app, switching between modules, back navigation, overall orientation.
3. **Subscribing to / activating modules**: finding modules, subscribing, unsubscribing, and confirming they appear/disappear correctly.
4. **General app health**: crashes, freezes, broken buttons, layout issues, obviously wrong German text.
## Out of scope
- The actual content inside the modules (data is placeholder / not productive yet).
- Payments or any real-world transactions.
## Deliverables
- **12 testers** enrolled in our Google Play closed test and **opted in for 14 consecutive days**.
- A short **written report per tester** (or a consolidated report) covering the onboarding and navigation flows, plus any bugs — ideally with device model, Android version, screenshots, and steps to reproduce.
- Confirmation/tracking that all 12 remain opted in for the full period (so the Google Play requirement is met).
## Tester requirements
- Genuine **Android devices** with a valid **Google account** (the opt-in is tied to the Google account email).
- The app UI is in **German**. German-speaking testers are **preferred**, but this is **not a requirement** — **international testers are welcome**. The onboarding and navigation flows can be evaluated without fluent German (a translation/browser tool is fine for reading labels).
- Willing to install via our closed-testing opt-in link, use the app a few times over 14 days, and submit feedback.
## What we provide
- The **Google Play closed-testing opt-in link** and instructions.
- A simple **feedback template** (or we can use yours).
- Quick responses to questions during the test.
## Timeline
- Testers enrolled within a few days of project start; **14-day** opt-in window thereafter. Actual hands-on testing effort per tester is light (a handful of short sessions).
## Payment & milestones (Freelancer.com escrow)
Payment is handled via Freelancer.com milestone payments and is tied to verifiable results:
- **Milestone 1 — Testers enrolled (~25–30%):** released once **all 12 testers are confirmed opted in** to our closed-testing track (verified in Google Play Console).
- **Milestone 2 — Successful completion (final, ~70–75%):** released **only after all 12 testers have remained opted in for the full 14 consecutive days** required by Google **and** the feedback report has been delivered and accepted.
Please base your bid on this structure. Note: the final milestone is conditional on the measurable "12 testers for 14 continuous days" requirement being met (as shown in Play Console) plus delivery of the feedback report.
## To apply, please include
- Your experience with **Google Play closed testing** and recruiting real testers.
- How you source testers and **how you ensure they are genuine** and comply with Google Play policies.
- The language mix of your testers (German is a plus, not a requirement — international testers welcome).
- Your price, structured around the two milestones above (e.g. fixed for all 12).
**Category:** Mobile App Testing / QA / User Testing
---
## About the app
Our new app is a German-language community app for the district (Bezirk) of Einsiedeln, Switzerland. It is a **modular platform**: users log in, complete a short onboarding, and then discover and subscribe to individual **modules** — e.g. a local **event calendar**, **clubs & associations**, **tourism**, **restaurant reservations**, **defect/issue reporting to the municipality**, **public-transport departures**, and the **lido (Badi)**. The app is built for Android and is currently in **Google Play closed testing**.
The app is **not yet publicly live**, so we are **not** asking you to test the real content inside the modules. The focus is the app shell and user flow.
## What we need
Google requires **12 testers opted in continuously for 14 days** before we can promote the app to production. We are looking for a professional testing provider who can **recruit and manage 12 legitimate testers**, get them opted into our closed-testing track, keep them opted in for the full 14 days, and collect structured feedback.
We need **real people who actually install and use the app** and report what they experience — not passive opt-ins.
## In scope (what to test)
1. **Onboarding** (top priority): first launch, account creation / login, any interest/persona selection, and the initial guided setup. We want to know where users get confused, stuck, or drop off.
2. **Navigation between modules**: moving around the app, switching between modules, back navigation, overall orientation.
3. **Subscribing to / activating modules**: finding modules, subscribing, unsubscribing, and confirming they appear/disappear correctly.
4. **General app health**: crashes, freezes, broken buttons, layout issues, obviously wrong German text.
## Out of scope
- The actual content inside the modules (data is placeholder / not productive yet).
- Payments or any real-world transactions.
## Deliverables
- **12 testers** enrolled in our Google Play closed test and **opted in for 14 consecutive days**.
- A short **written report per tester** (or a consolidated report) covering the onboarding and navigation flows, plus any bugs — ideally with device model, Android version, screenshots, and steps to reproduce.
- Confirmation/tracking that all 12 remain opted in for the full period (so the Google Play requirement is met).
## Tester requirements
- Genuine **Android devices** with a valid **Google account** (the opt-in is tied to the Google account email).
- The app UI is in **German**. German-speaking testers are **preferred**, but this is **not a requirement** — **international testers are welcome**. The onboarding and navigation flows can be evaluated without fluent German (a translation/browser tool is fine for reading labels).
- Willing to install via our closed-testing opt-in link, use the app a few times over 14 days, and submit feedback.
## What we provide
- The **Google Play closed-testing opt-in link** and instructions.
- A simple **feedback template** (or we can use yours).
- Quick responses to questions during the test.
## Timeline
- Testers enrolled within a few days of project start; **14-day** opt-in window thereafter. Actual hands-on testing effort per tester is light (a handful of short sessions).
## Payment & milestones (Freelancer.com escrow)
Payment is handled via Freelancer.com milestone payments and is tied to verifiable results:
- **Milestone 1 — Testers enrolled (~25–30%):** released once **all 12 testers are confirmed opted in** to our closed-testing track (verified in Google Play Console).
- **Milestone 2 — Successful completion (final, ~70–75%):** released **only after all 12 testers have remained opted in for the full 14 consecutive days** required by Google **and** the feedback report has been delivered and accepted.
Please base your bid on this structure. Note: the final milestone is conditional on the measurable "12 testers for 14 continuous days" requirement being met (as shown in Play Console) plus delivery of the feedback report.
## To apply, please include
- Your experience with **Google Play closed testing** and recruiting real testers.
- How you source testers and **how you ensure they are genuine** and comply with Google Play policies.
- The language mix of your testers (German is a plus, not a requirement — international testers welcome).
- Your price, structured around the two milestones above (e.g. fixed for all 12).