My Pet Shop — MM-Dashboard

Current State

Focus

My Pet Shop — Repeat Player Fit of Direct Entry 004

Validation Question

After alignment with Tapps, will Poki grant a second Web Fit of direct-entry-004 to reassess entry conversion following the reproduced Player Fit improvement?

Setup

incomplete (primary_reference, reference_thesis)

Primary Reference

—

Reference Thesis

—

Open Questions

Does a repeat Player Fit of the exact direct-entry-004 ZIP reproduce the initial-play conversion improvement sufficiently to support a new Web Fit submission decision?
Does Tapps agree with the second Web Fit request and proposed evidence/message?
After Tapps alignment, will Poki accept a second Web Fit of direct-entry-004?
Can repeat-specific progress events and matching date/device filters be obtained if needed for the request?

Next Actions

Align with Tapps on the proposed request and messaging first. Portuguese Tapps and English Poki drafts are prepared in this chat, explicitly citing historical Web Fit 44.6% Conversion to Play, rel002 Player Fit 54.8%, and 004 results 68.6%/68.2%, with the non-equivalence caveat. User's agreement permits direct Poki contact, but alignment with Tapps must precede asking Poki for a second Web Fit using the existing direct-entry-004 ZIP. No messages have been sent and no second Web Fit is requested/submitted.

Latest Findings

Latest Poki Player Fit for my-pet-shop-start-hand-001.zip: average session 213.3s, p90 501.0s, median 80.5s, under-3m sessions 69.6%, Poki start rate 57.0%.
Repeat test b955dcc3-ca20-4302-8fdb-192dfe96ad7e is distinct from original 004 test f0001097-b3d4-4cb6-a9b1-03e192ff757f and references the same Poki version 4cf82d4e-d4f6-4578-aaaa-381f77b4d34e, my-pet-shop-direct-entry-004.zip.
Gameplay starts/pageviews: rel002 274/500=54.8%; first 004 343/500=68.6%; hand001 285/500=57.0%; repeat 004 341/500=68.2%. Repeat differs from first 004 by -0.4 percentage points and exceeds rel002 by 13.4 points, or 67 extra starts per 500 pageviews (approximately 24% relative increase).
Repeat average session 235.464s, median 110.5s, 188/500 durations reach at least 180s=37.6%. Prior 004: 205.094s, 100s, 32.4%; rel002: 203.556s, 100s, 31.6%. Supporting aggregate engagement shows no apparent tradeoff; entry conversion remains primary.
Supplied progress-events.csv exactly matches earlier 004 counts: loading starts 796, completes 655; Day1 starts 481, completes 270 (total completion occurrences 271). Its 73.4% Day1-start/loading-complete ratio is not independently replicated repeat-event evidence; no confirmed repeat window/version metadata.
Poki's historical Web Fit reported 44.6% Conversion to Play and advised continued iteration. Player Fit gameplay-start rate is not the same reconciled metric/population; do not claim Web Fit conversion is now 68%.
Separate sequential Player Fit cohorts reproduce the 004 improvement but do not establish randomized causal proof or guarantee Poki acceptance. Hand001 did not reproduce this advantage; 004 is the proposed Web Fit candidate.
The repeat resolves the immediate replication question in favor of 004: its initial-play conversion advantage recurred at essentially the same rate. This provides a concrete basis to request a second Web Fit assessment focused on the original entry-conversion issue, subject to Tapps alignment. Preserve uncertainty about Web Fit metric mapping and missing repeat event window. No further code changes or extra Player Fit repeat is the current next step.

Updated

2026-10-20T20:51:15.787290Z

Active Hypotheses

The current My Pet Shop web port is strong enough to advance through Poki Web Fit without meaningful gameplay changes, and Poki's qualitative review will identify whether the next priority is entry conversion, positioning, presentation, or another product concern.

The Player Fit baseline shows the strongest session depth in the five-game Tapps portfolio, especially among players who reach a playable shop day. The core loop should be preserved until Poki provides its product assessment.

The existing My Pet Shop baseline may find a more suitable audience on CrazyGames without gameplay redesign.

User-approved cross-portal batch uses existing builds and marketing readiness to obtain new platform evidence cheaply.

Branded loading feedback and a shorter first-session path will increase the share of new web players reaching a successful pet-care action and reduce time to that action, while preserving comprehension and the existing management loop.

44.6% historical Web Fit conversion, preliminary 9-second median loading completion and observed Home -> selection -> four-page instructions -> reward/setup -> day-start flow motivate investigation. These do not yet establish which step causes loss; use settled instrumented baseline and separate versioned slices.

A delayed pointing hand aimed at START during first-entry shop preparation will increase preparation-to-Day1 conversion by helping players notice how to begin.

The initial screenflow treatment increased Day1 starts/loading completes from 58.3% to 73.4%, but 004 retains a 26.6% aggregate gap. User reports playtests suggest START is overlooked and explicitly approves this small next experiment.

The unchanged direct-entry-004 artifact can reproduce its previously observed initial-play conversion advantage over instrumented original rel002.

Prior 004 Player Fit starts reached 68.6% versus rel002 54.8%; hand001 fell to 57.0%. Replicate the strongest observed entry candidate before deciding on another Web Fit submission.

Latest Experiment

My Pet Shop — Repeat Player Fit of Direct Entry 004

evidence ready

Does a repeat Player Fit of the exact direct-entry-004 ZIP reproduce the initial-play conversion improvement sufficiently to support a new Web Fit submission decision?

User-approved next action is a repeat Player Fit, not an implementation change or authorization to submit to Web Fit. Existing direct-entry-004 artifact is the candidate; preserve hand001 evidence and code.

Expected Result: Independent repeat evidence clarifies whether 004's entry advantage is reproducible. Decide on Web Fit only after reviewing results; no invented pass threshold or deadline.

Prototype Scope: Use exact existing my-pet-shop-direct-entry-004.zip. No rebuild from hand-modified working tree, no code rollback, new cue or gameplay changes. Record artifact hash where practical and use comparable Poki test settings. Human performs upload/test; no repeat is claimed launched.

Non-Goals

New Web Fit submission before repeat evidence review
Hand iteration, automatic START, gameplay/retention/economy changes
Rebuilding a different artifact and labeling it unchanged 004
Causal attribution from unmatched sequential cohorts or pooling duplicate snapshots

Evidence Capture

decision: Review repeat entry evidence and uncertainty before choosing a Web Fit artifact/submission. Historical 44.6% Web Fit metric is not a direct same-denominator comparator.
guardrails: First-care comprehension, Day1 completion, technical failures, rewards and save integrity · Keep event populations separate from 500-pageview Player Fit samples
primary metrics: Player Fit gameplay starts/pageviews, baseline 343/500=68.6% for prior 004 and 274/500=54.8% for rel002
comparison: Match and record device, orientation, country/category/traffic settings where available, dates/windows, sample sizes and save/route eligibility. Distinguish new test ID from previous 004; do not merge duplicate dashboard records.
secondary metrics: Matched-window Day1 starts/loading completes, prior 004 481/655=73.4% · Loading completion and overall Day1 start reach · Preparation recordings and START visibility/interactions where retrievable
phase: Approved; awaiting human repeat Player Fit upload/test
artifact: Exact existing my-pet-shop-direct-entry-004.zip; record identity/hash and new test ID.

Sources: 1fee71d1-869e-4872-b640-dbccc07229d6, 6ae24bea-cfd5-42f0-9dd6-0d0c12f85ad0, 82a2785c-417c-47e8-85f9-1f256971274c

Latest Analysis

004 repeat reproduces entry conversion; align with Tapps before second Web Fit request

Distinct repeat Player Fit of direct-entry-004 reached 68.2% gameplay starts versus prior 68.6% and rel002 54.8%. Evidence supports proposing another Web Fit using 004; immediate next step is alignment with Tapps before approaching Poki.

Findings

Repeat test b955dcc3-ca20-4302-8fdb-192dfe96ad7e is distinct from original 004 test f0001097-b3d4-4cb6-a9b1-03e192ff757f and references the same Poki version 4cf82d4e-d4f6-4578-aaaa-381f77b4d34e, my-pet-shop-direct-entry-004.zip.
Gameplay starts/pageviews: rel002 274/500=54.8%; first 004 343/500=68.6%; hand001 285/500=57.0%; repeat 004 341/500=68.2%. Repeat differs from first 004 by -0.4 percentage points and exceeds rel002 by 13.4 points, or 67 extra starts per 500 pageviews (approximately 24% relative increase).
Repeat average session 235.464s, median 110.5s, 188/500 durations reach at least 180s=37.6%. Prior 004: 205.094s, 100s, 32.4%; rel002: 203.556s, 100s, 31.6%. Supporting aggregate engagement shows no apparent tradeoff; entry conversion remains primary.
Supplied progress-events.csv exactly matches earlier 004 counts: loading starts 796, completes 655; Day1 starts 481, completes 270 (total completion occurrences 271). Its 73.4% Day1-start/loading-complete ratio is not independently replicated repeat-event evidence; no confirmed repeat window/version metadata.
Poki's historical Web Fit reported 44.6% Conversion to Play and advised continued iteration. Player Fit gameplay-start rate is not the same reconciled metric/population; do not claim Web Fit conversion is now 68%.
Separate sequential Player Fit cohorts reproduce the 004 improvement but do not establish randomized causal proof or guarantee Poki acceptance. Hand001 did not reproduce this advantage; 004 is the proposed Web Fit candidate.

Interpretation

The repeat resolves the immediate replication question in favor of 004: its initial-play conversion advantage recurred at essentially the same rate. This provides a concrete basis to request a second Web Fit assessment focused on the original entry-conversion issue, subject to Tapps alignment. Preserve uncertainty about Web Fit metric mapping and missing repeat event window. No further code changes or extra Player Fit repeat is the current next step.

Open Questions

Does Tapps agree with the second Web Fit request and proposed evidence/message?
After Tapps alignment, will Poki accept a second Web Fit of direct-entry-004?
Can repeat-specific progress events and matching date/device filters be obtained if needed for the request?

Next Action: Align with Tapps on the proposed request and messaging first. Portuguese Tapps and English Poki drafts are prepared in this chat, explicitly citing historical Web Fit 44.6% Conversion to Play, rel002 Player Fit 54.8%, and 004 results 68.6%/68.2%, with the non-equivalence caveat. User's agreement permits direct Poki contact, but alignment with Tapps must precede asking Poki for a second Web Fit using the existing direct-entry-004 ZIP. No messages have been sent and no second Web Fit is requested/submitted.

Latest Player Fit

my-pet-shop-start-hand-001.zip

Imported: 2026-10-19T00:23:59.460645Z · Captured: 2026-10-18T18:03:01Z

Avg Session

213.35s

P90 Session

501.0s

Median Session

80.5s

Under 3m Sessions

69.6%

Latest Poki Player Fit for my-pet-shop-start-hand-001.zip: average session 213.3s, p90 501.0s, median 80.5s, under-3m sessions 69.6%, Poki start rate 57.0%.