Project planning / Arcade pinball
A planning brief for a one-time licence · mobile web · discovery.
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 mobile web, the game launch integration work should be evaluated during discovery before the scope of the one-time licence is accepted.
Produce a written requirements list and identify missing information before quoting implementation work.
Playable conceptArcade pinball · Virtual-credit demo
Integration priority
Define who requests the launch, how the player reaches the game and which exact hostnames may embed it. API secrets stay on the operator server.
Test valid and expired launches, suspended licences, unauthorised games and unapproved subdomains.
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
Prioritise narrow screens, touch controls, interrupted connections and browser navigation. Test portrait and landscape where the design supports them.
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 / Request a launch for an allowed game | Record the Pulse Pinball build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 02 / Attempt a launch after licence expiry | Record the Pulse Pinball build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 03 / Check a hostname outside the agreement | Record the Pulse Pinball build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 04 / Confirm credential revocation blocks new requests | Record the Pulse Pinball build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 05 / Test both flippers independently | Record the Pulse Pinball build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 06 / Check touch targets during ball movement | Record the Pulse Pinball build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
| 07 / Review bumper and end-of-round feedback | Record the Pulse Pinball build, mobile web environment, expected result and observed result. Attach reproducible steps for any mismatch before completing discovery. |
For this Pulse Pinball proposal, connect each agreed right to an identifiable deliverable. Keep game launch integration 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-0651. Requirements must be confirmed against your actual platform and agreement.