HTML5 release regression
Prove the player path before the update reaches your audience.
A green build does not prove an itch.io iframe, touch route, save restore, or ending still works. This scoped pilot exercises one public HTML5 release like a player and returns reproducible evidence without claiming that software can be guaranteed defect-free.
Pilot deliverable
One build, one public route, one retest
- Primary player path from title screen to ending
- Keyboard, pointer, and touch interaction checks
- Refresh, versioned save, and restore evidence
- Desktop plus two mobile viewport checks
- Console, failed-resource, and itch.io iframe review
- A reproducible defect list and one verification retest
One HTML5 game, one release candidate, one public itch.io route. Scope is confirmed before payment.
Request a scoped auditIncluded
Black-box player-path regression, viewport evidence, reproducible steps, and one retest after fixes.
Not included
Source-code access, account credentials, payment testing, security certification, performance guarantees, or a promise of zero defects.
Prepare the handoff
Use the same release gate before sending a build.
The checklist covers ZIP structure, player-path evidence, pointer/keyboard/touch, save restore, and the final live iframe. It contains no client information and does not ask for account credentials.
Download the free preflight checklistSee the evidence format
A defect report should be reproducible before it is persuasive.
This de-identified sample comes from a self-owned test build, not a customer or paid engagement. It shows severity, exact steps, expected/actual behavior, evidence boundary, fix, and retest.
Open the sample reportWhy this exists
Local success and live success are different states.
itch.io runs HTML5 projects in a hosted iframe with case-sensitive paths, ZIP requirements, embed settings, and mobile behavior. The audit verifies the deployed route instead of treating a local build as release evidence.