Project planning / Arcade pinball
A planning brief for a one-time licence · platform planning · sandbox validation.
Neon bumpers, responsive manual flippers and a fast-moving ball bring an arcade rhythm to an original casino concept.
Pulse Pinball combines manual flipper timing with a arcade pinball concept. For platform planning, the technical evaluation work should be evaluated during sandbox validation before the scope of the one-time licence is accepted.
Run the integration tests in the isolated test environment. Public demo credits and test-wallet credits are separate systems.
Playable conceptArcade pinball · Virtual-credit demo
Integration priority
Evaluate the current concept against the requirements of your platform. Separate demonstrated features from changes that still require production work.
Record reproducible steps, expected outcomes and device details for each issue; retest the specific affected behaviour after a fix.
Commercial scope
Define a right to use the agreed build, with the brands, domains and delivery scope written down. A one-time payment does not automatically transfer ownership.
Specify whether maintenance is included or separately renewed.
Channel requirements
Start with the operator’s actual browser, wallet and player journey requirements. This brief is a planning scenario, not a claim of compatibility with an unnamed casino.
Game-specific decision
Decide how player input influences the commercial outcome. Visual responsiveness and a validated outcome model are separate acceptance questions.
| Check | Evidence to collect |
|---|---|
| 01 / List requirements absent from the concept | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 02 / Check initial loading and asset failures | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 03 / Exercise a complete demo round | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 04 / Record recovery after navigation or refresh | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 05 / Test both flippers independently | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 06 / Check touch targets during ball movement | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
| 07 / Review bumper and end-of-round feedback | Record the Pulse Pinball build, platform planning environment, expected result and observed result. Attach reproducible steps for any mismatch before completing sandbox validation. |
For this Pulse Pinball proposal, connect each agreed right to an identifiable deliverable. Keep technical evaluation changes explicit in the statement of work.
The current game is a playable concept. Test wallet behaviour is available separately in the developer sandbox. Real-money wagering is disabled in that sandbox.
A live build requires server-authoritative gameplay, validated payout maths, partner-specific wallet integration and applicable testing. This brief is a planning aid, not evidence of certification or an existing platform connector.
Adjust the environments and test cases for this Pulse Pinball evaluation. Start with the checklist above, then add partner-specific cases.
Planning reference GQX-0326. Requirements must be confirmed against your actual platform and agreement.