APP TESTING AND RESEARCH, BUILT AROUND PEOPLE

Find app testers and research participants.

Find people to test an app, share target-audience feedback, or take part in surveys and interviews. Tester profiles and public browsing are open; new builder registration is temporarily unavailable.

Testers

Completed sessions

Accepted invitations

Loading platform statistics.

New builder registration is temporarily unavailable.Tester profiles and public browsing are open.

FOR TESTERS AND RESEARCH PARTICIPANTS

Take part in app testing or research.

Explore opportunities to test apps, answer surveys, or join interviews. Review the task, effort, and reward before you take part.

Your account role is tester, whether you test apps or participate in research.

App testers

Try apps and share useful feedback about your experience.

Research respondents

Take part in surveys, interviews, and audience research.

Each opportunity explains its requirements and reward before you decide to participate.

Joining a closed test?

Review Google Play requirements and every project step before accepting.

LOOKING FOR PARTICIPANTS?

Explore Testers and research participants

Browse opt-in profile previews by profession, platform, and feedback interest. Invitations are managed in the builder workspace. Builder registration is temporarily unavailable.

Browse public Testers

APPTESTERSPH GUIDE

Common questions about app testing and research

What is AppTestersPH?

AppTestersPH is a platform for app testing and research participation. Testers can create a profile and visitors can browse opt-in previews for Google Play closed testing, app feedback, surveys, and interviews. New builder registration is temporarily unavailable. Session fees and participant reward examples are shown in PHP.

Can a tester also participate in research?

Yes. Accounts use the tester role to join either app testing or research opportunities. For research, you participate as a research respondent in surveys, interviews, or other studies. A research project does not need to involve an app. Eligibility depends on the project requirements.

What does Google Play require for a closed test?

For personal developer accounts created after November 13, 2023, Google Play requires at least 12 testers to remain opted in to a closed test continuously for the 14 days before applying for production access. Google may ask for further testing, and meeting the tester and time requirements does not guarantee production access. Check Google Play Console Help for the current rules. Read Google Play Console Help.

Who sets a project’s participant reward?

The reward examples on this page are reference ranges. Each builder or researcher sets the project’s compensation based on its time, effort, and requirements. Participants can review the task and reward before accepting.

How are app-testing session costs calculated?

The approved session fee is PHP 200 when the builder finds testers or PHP 350 for staff-assisted sourcing. Participant rewards are separate. An app-testing session needs at least four testers, and the total is the session fee plus the reward per tester multiplied by the tester count. For example, PHP 200 plus PHP 100 for each of four testers totals PHP 600. This is a calculation example, not a live offer. Research-specific service fees remain to be determined, and new builder registration is temporarily unavailable.

Can Builders register now?

Builder registration is temporarily unavailable. Tester registration is open for people who want to create a profile.

How old do I need to be?

You must be at least 13 to create an AppTestersPH account. Individual testing or research opportunities may set a higher age limit or additional consent requirements.

Can I leave an app testing or research session?

Yes. Testers can leave an active session from the session details with a reason of 10 to 2,000 characters. Leaving is blocked while submitted work awaits review or after work is confirmed. Contact the organizer or report a concern for assistance. Leaving ends session access, preserves work and reward records, and prevents rejoining the same session.

Can a builder remove or replace a tester?

A builder can remove an active tester with a recorded reason of 10 to 2,000 characters, unless submitted work awaits review or work is already confirmed. The builder may invite a different eligible tester into the freed place within the session capacity. The removed tester can see the reason and report an unfair removal.

What happens when an unfair removal is reported?

An admin reviews the removal reason and evidence. A warning or session closure is applied only after the complaint is confirmed and resolved with an explanation. Reporting alone does not cause a penalty. Closing a session keeps work, reward, and payout records. It does not automatically issue refunds.

How do I find participants?

Browse without signing in. Filter by profession, platform, or interest. Existing builders send invitations from their workspace. Browsing does not book anyone or guarantee eligibility. New builder registration is temporarily unavailable.

Who appears in the directory?

Active, available testers who opt in. Public listing is off by default. Previews show basic profile details, with no email, device, payout, or session information. Change visibility in your profile.

How does staff-assisted sourcing work?

For a paid managed testing session with assisted sourcing, an admin helps find suitable, available testers and sends invitations up to the session limit. This can include testers not listed publicly. Testers can accept or decline. This service does not guarantee participation, completed work, or Google Play approval. Research service fees are not yet set.

How do I report a session problem?

Open the session details to report a problem. Explain what happened and add a Google Drive link if you have evidence. Admins review the report and respond. Sending a report does not automatically change rewards, approve work, suspend accounts, or issue refunds. For privacy concerns, use the contact details in our privacy notice.

PRICING

App testing prices and research participant rewards

All amounts are PHP reference examples. New builder registration is temporarily unavailable, so these are not currently purchasable offers. App-testing sessions need at least 4 testers. Research participants use the target-audience reward ranges below.

The participant reward amounts shown are for reference only and may vary by project. Builders and researchers set appropriate compensation based on the work, time, and requirements involved.

BUILDER FINDS TESTERS

PHP 200 session fee

STAFF-ASSISTED SOURCING

PHP 350 session fee

Brief feedback or survey

PHP 50 to 150

Per Tester or respondent / about 15–45 minutes

Detailed feedback, interview, or research

PHP 100 to 300

Per Tester or respondent / about 45+ minutes

Google Play closed test

PHP 50 to 500

Per Tester / install, 14-day opt-in, one short test, feedback

For app-testing sessions, total = session fee + (reward per tester × tester count). Builders set exact rewards based on workload. Research respondents use the target-audience feedback ranges. Research-specific service fees remain to be determined. Closed-test projects must state any daily-use requirement. Participants see the task and reward before accepting.