Do Not Disturb 2

Current State

Focus

Do Not Disturb 2 — CrazyGames Basic Launch Baseline

Validation Question

Can the original Do Not Disturb 2 mobile game, ported to web without meaningful gameplay adjustments, pass Poki Player Fit?

Setup

incomplete (primary_reference, reference_thesis)

Primary Reference

—

Reference Thesis

—

Open Questions

• Does the existing Do Not Disturb 2 web baseline show sufficient audience fit on CrazyGames to justify further investment?
• What materially different engagement hypothesis could justify reopening the project?
• Would a future distribution opportunity warrant a cross-portal test?

Next Actions

• Park the project while preserving the validated web port and test history.

Latest Findings

• Latest Poki Player Fit for build002.zip: average session 80.5s, p90 140.0s, median 70.0s, under-3m sessions 95.4%, Poki start rate 100.0%.
• Build 002 recorded 80.5 seconds average, 70.0 seconds median, 140.0 seconds P90, and only 4.6% of sessions reaching three minutes.
• Compared with build 001, build 002 decreased average session by 6.8 seconds, median by 2 seconds, P90 by 11 seconds, and three-minute reach by 2.0 percentage points.
• The exact gameplay-start rate should be treated as pending verification rather than used as a committed conclusion.
• Incremental onboarding guidance did not establish a positive direction. Another test is not justified without a materially different engagement hypothesis, new portal opportunity, or strategic portfolio need.

Updated

2026-10-11T00:51:57.273238Z

Active Hypotheses

The existing Do Not Disturb 2 baseline may find a more suitable audience on CrazyGames without gameplay redesign.

User-approved cross-portal batch gathers new audience evidence from existing builds, prioritizing marketing readiness.

Latest Experiment

Do Not Disturb 2 — CrazyGames Basic Launch Baseline

approved

Does the existing Do Not Disturb 2 web baseline show sufficient audience fit on CrazyGames to justify further investment?

Separate existing-build portal test. Prior Poki experiments and findings remain historical context; no gameplay development is reopened by this test.

Expected Result

Submit the baseline and use subsequent portal feedback and engagement evidence to decide whether further investment is worthwhile.

Prototype Scope

Prepare the existing playable web baseline for CrazyGames Basic Launch with only required compatibility fixes and marketing/submission materials. No CrazyGames SDK integration is required for this first test. Túlio reports builds are straightforward and below 50 MB; verify the selected artifact when submitting. Preserve gameplay, tutorial, progression and economy. Select an existing build and record its exact version; do not assume latest is best.

Non-Goals

• New gameplay, progression, onboarding or economy iterations
• Mandatory SDK integration for Basic Launch
• Assuming Poki and CrazyGames metrics are identical
• Claiming that old product hypotheses are now supported

Evidence Capture

submission

Record actual submission date, build and portal status; do not label a planned game submitted or live. · Use the appropriate Tapps or ManiMani account.

evidence

Capture CrazyGames review feedback and available engagement/retention metrics after launch. · Compare directionally to the same existing game's Poki baseline, recording metric definitions and audience differences; portal comparison is not randomized causal evidence.

weekly selection

Eligible for the September 28–October 4 batch of 4–5 existing-game CrazyGames submissions. Candidate pool exceeds target; select and order by marketing-material readiness. No fixed time-of-day or mandatory individual-game submission.

prerequisites

Túlio has both Tapps and ManiMani account access. · Inventory existing covers, screenshots/video, description and controls; prepare missing required assets. · Verify selected build in portal preview and record exact artifact/version; apply only required compatibility fixes.

completion

Weekly delivery is the submission; approval, launch and performance feedback may arrive later.

Sources: 87802422-28a7-48e6-a71b-25f0770b5954

Latest Analysis

Initial Player Fit assessment — park after two shallow-session tests

Do Not Disturb 2 should be parked. Two Player Fit tests show consistently shallow sessions, and the second build's mailbox guidance did not improve aggregate engagement.

Findings

• Build 002 recorded 80.5 seconds average, 70.0 seconds median, 140.0 seconds P90, and only 4.6% of sessions reaching three minutes.
• Compared with build 001, build 002 decreased average session by 6.8 seconds, median by 2 seconds, P90 by 11 seconds, and three-minute reach by 2.0 percentage points.
• The exact gameplay-start rate should be treated as pending verification rather than used as a committed conclusion.

Interpretation

Incremental onboarding guidance did not establish a positive direction. Another test is not justified without a materially different engagement hypothesis, new portal opportunity, or strategic portfolio need.

Open Questions

• What materially different engagement hypothesis could justify reopening the project?
• Would a future distribution opportunity warrant a cross-portal test?

Next Action

Park the project while preserving the validated web port and test history.

Latest Player Fit

build002.zip

Imported: 2026-08-26T17:04:31.725781Z · Captured: 2026-08-10T20:05:01Z

Latest Poki Player Fit for build002.zip: average session 80.5s, p90 140.0s, median 70.0s, under-3m sessions 95.4%, Poki start rate 100.0%.

No live performance evidence imported yet.

No Poki playtest recordings imported yet.

Latest Decision

None