InTesters dashboard showing a Play Store closed test with testers and a 14 day progress bar on a real device
Deliverables
Play ConsoleClosed TestingAutomationAndroidNext.js 16PostgreSQLBullMQRedis
Client / ProductInTesters Platform
RoleSolo Founder & Lead Systems Architect
Timeline2025 – 2026
StatusProduction Live

InTesters - Play Store Testing

InTesters needed 12 active testers for 14 days, we built the cherry on top.

Solving Google Play's 14-Day 12-Tester Personal Account Gate

In late 2023, Google introduced a strict requirement for all new personal Google Play Developer accounts: apps must be tested by at least 12 real opt-in testers continuously for 14 straight days before production access can even be requested. For solo developers and independent studios, finding 12 reliable individuals who keep the app installed and actively test every single day without churning is notoriously difficult.

Traditional testing communities suffer from flaky participation,testers opt in, open the app once, and immediately uninstall or forget about it, resetting the 14-day clock back to zero. InTesters was built from scratch to turn this chaotic manual process into a deterministic, reliable closed-testing pipeline.

The primary architectural challenge was ensuring real device verification, automated daily engagement telemetry, and an automated replacement engine so developers never lose progress due to inactive participants.

Technologies & Infrastructure
Next.js 16TypeScriptPostgreSQLBullMQRedisTailwind CSSGoogle Play API
Production Pass Rate
100%

All completed tests met Google's 14-day opt-in criteria without resets.

Active Tester Pool
500+

Verified physical Android devices ready for immediate test enrollment.

Verification Latency
<120ms

Real-time webhook and status check latency across tester actions.

Churn Replacement
Automated

Standby testers auto-assigned instantly if device engagement drops.

InTesters - Play Store Testing preview 1
Production Impact & Execution

High-Availability System Architecture

An Android app testing service. Real testers join your closed test on Google Play and stay for the full 14 days, so you can meet Google's 12 tester requirement and move your app to production.

Engineered & deployed by Amit NarwalLive Product

The Architecture

A simplified but modern approach to automated closed testing.

We architected an asynchronous event-driven system powered by Redis and BullMQ to manage tester lifecycles, health checks, and milestone verifications.

01.

Distributed Task Queue with BullMQ & Redis

Daily participation checks, email reminders, and test streak verifications run as isolated BullMQ jobs with exponential backoff and dead-letter queue resilience to guarantee no dropped events.

02.

Relational Schema with State Machine Modeling

PostgreSQL tracks tester opt-ins, daily engagement timestamps, and track transitions through strict status enums, ensuring zero race conditions during parallel tester assignment.

03.

Automated Drop-off & Churn Protection Engine

If an assigned tester fails to open the app or uninstalls during the 14-day window, an automated standby worker immediately enrolls a backup tester so the developer's 12-tester quorum is never compromised.

04.

Developer Telemetry & Verification Reports

Developers get real-time visibility into active device models, Android OS versions, tester notes, and a production-ready exportable audit report for Google Play review.

Key Engineering Insights

Device diversity matters: Google Play validates that testers run varied Android versions and screen densities, requiring smart device-allocation algorithms.

Asynchronous background queues eliminate bottlenecks: Moving daily streak evaluations to BullMQ background workers kept dashboard response times sub-100ms.

Transparent progress tracking dramatically reduces developer anxiety during the high-stakes 14-day testing period.

Have a similar vision?

Let's build something exceptional together.