Project planning / Arcade pinball
A planning brief for a custom build · multi-brand operation · handover planning.
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 multi-brand operation, the technical evaluation work should be evaluated during handover planning before the scope of the custom build is accepted.
Define documentation, account ownership, secret rotation, support contacts and the acceptance record required for handover.
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
Agree a commissioned production against a specific brief, review milestones and acceptance criteria. Decide which work begins only after the concept is approved.
Map requested changes to the build and record acceptance evidence.
Channel requirements
Separate each brand’s approved hostnames, catalogue access and operational contacts. Test that one customer or brand cannot obtain another customer’s credentials or sessions.
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, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 02 / Check initial loading and asset failures | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 03 / Exercise a complete demo round | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 04 / Record recovery after navigation or refresh | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 05 / Test both flippers independently | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 06 / Check touch targets during ball movement | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
| 07 / Review bumper and end-of-round feedback | Record the Pulse Pinball build, multi-brand operation environment, expected result and observed result. Attach reproducible steps for any mismatch before completing handover planning. |
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-4346. Requirements must be confirmed against your actual platform and agreement.