How do I get started?

Install Dozenflow from Google Play (https://play.google.com/store/apps/details?id=com.ground.proofflow), follow the easy start guide, embed the Closed Test SDK in anyapp, then activate your test.

What is screen_view analytics?

The SDK emits screen_view events with a screen_name. Organizers see screen flow and navigation funnels in Dozenflow Stats. Android Navigation Compose auto-tracking is available now; other platform bridges are in development.

Your Android app where testers install the build. You embed the Closed Test SDK there. Testers do not need the Dozenflow mobile app unless you want optional binding features.

Is Dozenflow a tester marketplace?

No. You bring your own audience. The site does not run a global catalog of tests or in-platform applications.

What is Base vs Advanced SDK mode?

Base mode uses no publishable key; the server matches your allowlisted build tuple. Advanced mode uses pk_live keys from Dozenflow for server-managed policy.

Do testers need the Dozenflow app?

No for basic telemetry — testers only need your APK with the Closed Test SDK. The Dozenflow app is optional for profile binding and organizer-driven reminders.

Can I use the website instead of the mobile app?

The web dashboard is read-only. Create tests, activate campaigns, and rotate publishable keys in the Dozenflow Android app.

Available on Google Play

Know which testers are actually helping — before day 14 surprises you

Install the Dozenflow organizer app, embed our Closed Test SDK in your Android app (anyapp), and see real sessions, daily activity, and Play's 12×14 campaign progress.

You recruit testers through your own channel. Dozenflow shows what's happening — it does not find testers for you.

Start in 5 minutes Install on Google Play

Free during early access · Setup takes minutes · SDK on Maven Central

What you will know in the first 24 hours

Who actually opened your app today — not just who opted in.
Which testers went silent before the streak breaks.
Where testers drop in core flows when screen_view is enabled.

Dozenflow is an operations layer for organizers. It complements Play Console and does not replace it.

Week-one proof snapshot (before vs after)

These are practical operating benchmarks teams use when moving from manual coordination to SDK-backed closed-test monitoring.

<24h visibility on silent testers

Before: 24-48h lag in aggregate reporting can hide daily drop-off.

After: same-day session signals from instrumented builds support faster nudges.

5-step setup to first signal

Before: setup checklists without objective tester evidence.

After: install app -> create test -> add SDK -> activate -> see first session.

12×14 context in one workflow

Before: quorum, streak, and activity split across tools and chats.

After: one organizer flow for campaign progress, sessions, and risk signals.

Exact outcomes vary by cohort quality and app stability. Dozenflow improves operational visibility and does not guarantee production approval.

Mini case: from noisy chat to daily signal

Problem: small Android team tracked tester activity in chat and spreadsheets, then noticed drop-off too late.

Action: moved to a structured flow: setup checklist + SDK events + daily roster checks.

Outcome: faster same-day nudges, clearer issue prioritization, and less guesswork before production decisions.

Request setup help Book onboarding call

Onboarding call slots are limited in early access and confirmed by email.

Two pieces — one workflow

Organizers use Dozenflow. Testers install your app. Telemetry flows from anyapp through the SDK.

Dozenflow app Organizer

Create tests, activate campaigns, view Stats, send reminders, and manage publishable_key on Android.

Install: Google Play

Closed Test SDK In anyapp

Maven dependency in the APK your testers install. Sends session telemetry to the ingest API — Base mode works without a key.

Integrate: SDK guide · Screen flow

anyapp ≠ Dozenflow. Testers do not need the Dozenflow app for basic telemetry.

Screen flow analytics

Emit screen_view events from anyapp to see where testers go — top screens, paths, and funnels in Dozenflow Stats.

Ready now: core Android SDK plus optional Navigation Compose auto-tracking. In development: Flutter, React Native, Unity, and Fragment helper bridges.

Screen flow guide · SDK integration

What you'll see after testers open your app

Dozenflow session details with validated and short-session flags per tester — **Session details** — Per-tester sessions with validated duration and short-session flags.

Dozenflow campaign roster with session status slots and UTC day history — **Daily roster** — Slot colors for quiet, active, and completed sessions; UTC day history for quorum.

Dozenflow test card with 12×14 headcount, closed test window, and package verification — **12×14 campaign** — Quorum, streak, and phase toward Play's closed-test requirement.

Screenshots from the current app build. Tap a screenshot to enlarge.

Up and running in three moves

Install Dozenflow Get the organizer app from Google Play.
Add the SDK to anyapp One Maven dependency; optional publishable_key for Advanced mode. See the integration guide or screen flow add-on.
Activate and watch Turn on ingest, activate the test, distribute your build. Stats appear within minutes of the first tester session.

Full setup guide (5 steps) · SDK reference

Built for

Indie Android devs shipping their first Play closed track
Small studios without a dedicated QA ops team
Teams doing mutual testing who are tired of guessing if testers are still active

We don't find testers for you

Recruit through Telegram, email, Reddit, or Play internal links. Dozenflow is the operations layer: monitoring, campaign windows, and SDK telemetry — not a catalog of strangers.

Honest scope: we complement Play Console, we don't replace it.

Early access for organizer teams

Join early access to get priority onboarding, setup guidance, and product updates. We currently focus on teams that run Google Play closed tests and want reliable day-by-day visibility.

Current cohort is limited each month to keep onboarding quality high.

Frequently asked questions

How do I get started?: Install Dozenflow from Google Play, follow the 5-step guide, embed the SDK in anyapp, then activate your test.
What is screen flow analytics?: The SDK emits screen_view events with a screen_name. Dozenflow Stats shows navigation funnels when data is present. Android Navigation Compose auto-tracking is ready now; other platform bridges are in development.
Do testers need Dozenflow?: No for basic telemetry — they only need your APK with the SDK. The Dozenflow app is optional for profile binding and organizer-driven reminders.
What is anyapp?: Your Android app where testers install the build. You embed the Closed Test SDK there. It is not the Dozenflow organizer app.
Can I use the website instead of the app?: The web dashboard is read-only. Create tests, activate campaigns, and rotate keys in the mobile app.
Is Dozenflow a tester marketplace?: No. You bring your own audience. We do not run a global catalog of tests or in-platform applications.
Base vs Advanced SDK mode?: Base — no key; server matches your allowlisted build tuple. Advanced — use pk_live_… from Dozenflow for server-managed policy.
Where does telemetry go?: The SDK sends batches to https://api.groundspaceteam.com. Organizers view aggregates in the Dozenflow app and on this site.

Start monitoring your closed test

Install the app, add the SDK, activate — then watch real activity instead of guessing.

Start in 5 minutes Install on Google Play SDK integration Screen flow Sign in to web dashboard