Gameplay & Content
This section defines the gameplay, content, and user experience requirements for games published on QS Play.
In addition to technical compatibility, games should provide a clear, enjoyable, and accessible experience for players across desktop and mobile devices.
Originality and Intellectual Property
Game titles, artwork, audio, gameplay content, and other assets must be original or used with appropriate rights and permissions.
The following may result in rejection during the review process:
- Unauthorized use of copyrighted content.
- Assets obtained without proper licensing.
- Games that substantially replicate or imitate another game already published on QS Play.
- Misleading branding, visuals, or metadata.
Developers are responsible for ensuring that all submitted content complies with applicable intellectual property laws.
Fast Access to Gameplay
Players should be able to start playing as quickly as possible.
Ideally, gameplay should begin immediately or within a single interaction after the game loads.
Avoid placing unnecessary barriers before gameplay, including:
- Mandatory registration.
- Forced account creation.
- Multiple introductory screens.
- Long splash screens or logos.
- Excessive dialogs before the first playable moment.
Player authentication should be treated as an optional enhancement rather than a prerequisite for playing.
Guests and non-authenticated users should be able to access gameplay whenever technically feasible.
See Accounts, Progress & Multiplayer for account integration requirements.
User Interface and Readability
User interface elements must remain readable and usable across different screen sizes and device types.
Your game should function correctly both:
- Inside the embedded game frame on the game page.
- In fullscreen mode.
- On desktop devices.
- On mobile devices.
During review, the QS Play team performs visual and functional checks on every submitted game. Text and images must remain legible:
- On displays with
devicePixelRatio: 1(standard, non-HiDPI screens). - In a responsive game frame with a 16:9 aspect ratio.
- On mobile screens, if the game supports them.
Verify the interface at the following frame sizes rather than only at the resolution used during development. They are the most common sizes among QS Play players:
| Frame size (px) | Device |
|---|---|
| 1920 x 1080 | Desktop, fullscreen |
| 1314 x 739 | Desktop |
| 1098 x 618 | Small desktop |
| 970 x 545 | Tablet |
| 769 x 428 | Small tablet |
| 360 x 640 or 640 x 360 | Mobile (portrait 9:16 or landscape 16:9) |
These are reference points, not a complete list. The game frame resizes fluidly, so the layout must adapt to any size in between, not only to these presets. The sizes refer to the game frame itself, not to the browser window.
In Chrome DevTools, open the device toolbar (Ctrl+Shift+M), choose Responsive, and enter the frame size. To check devicePixelRatio: 1, enable Add device pixel ratio in the toolbar's ⋮ menu and set it to 1.
In particular, ensure that:
- Text remains readable.
- Buttons are easy to interact with.
- Important information is never clipped or hidden.
- Touch controls are appropriately sized on mobile devices.
- Menus and dialogs remain accessible on smaller screens.
Localization
English language support is required for all games.
If additional languages are supported, the game should synchronize its language with the language selected in QS Play.
Use:
to detect and respond to language changes from the platform.
The game should update its interface language without requiring a page reload.
If a player's selected QS Play language is not available in the game, fall back to English rather than displaying partially translated content.
Performance and Gameplay Consistency
Games should load quickly, remain stable during gameplay, and provide a consistent experience across different devices.
Game logic should not depend on a specific screen refresh rate.
Physics simulations, animations, timers, and gameplay systems should be based on elapsed time (deltaTime) rather than frame count, ensuring consistent behavior on displays running at:
- 60 Hz
- 120 Hz
- 144 Hz
- Higher refresh rates
Games should remain responsive throughout normal gameplay sessions and should not crash, freeze, or become unplayable under typical conditions.
Fullscreen Experience
If your game supports fullscreen mode, use the QS Play SDK methods:
Do not implement fullscreen behavior independently through direct Fullscreen API integration.
Games should also listen for fullscreen state changes using:
This ensures that the game correctly responds when players exit fullscreen mode using system controls, keyboard shortcuts, or platform-specific gestures.
Fullscreen mode should:
- Preserve gameplay functionality.
- Maintain proper interface scaling.
- Keep important controls visible and accessible.
- Return smoothly to embedded mode when exited.
If your game shows ads, see Ads · Fullscreen for how ads interact with fullscreen mode.
External Links and Navigation
Games must not contain links to:
- Competing gaming portals.
- Third-party game distribution platforms.
- External app stores unrelated to the gameplay experience.
The following exceptions are allowed where applicable:
- Privacy Policy pages.
- Terms of Service pages.
- Legal notices required for compliance.
Games should not attempt to redirect players away from QS Play without an explicit player action.
Content Rating and Audience Suitability
QS Play content rating policies may evolve over time.
If your game includes potentially sensitive content, including but not limited to:
- Realistic violence.
- Gambling-like mechanics.
- Explicit themes.
- User-generated content.
- Other age-sensitive material.
please contact the QS Play team before submission to confirm compatibility with current platform policies.
Developers are responsible for ensuring that submitted content is appropriate for the intended audience and complies with applicable laws and regulations.
Best Practices
The following recommendations are not mandatory requirements. However, they can significantly improve player retention, engagement, and overall game quality.
Onboarding
Teach players through gameplay whenever possible.
We recommend:
- Introducing mechanics gradually.
- Explaining only what is necessary for the first playable moments.
- Allowing experienced players to skip tutorials.
- Using visual guidance instead of lengthy instructions.
- Demonstrating controls through interaction rather than large blocks of text.
Good onboarding helps players understand the game without interrupting the experience.
Controls and Player Goals
Controls should be intuitive and understandable within a few seconds.
Players should always understand:
- What they are supposed to do.
- How to perform the required actions.
- What their current goal is.
Avoid changing established controls unexpectedly during gameplay.
Repeated actions without meaningful feedback or visible progress often lead to player frustration and early abandonment.
Visual and Audio Quality
Maintain a consistent presentation throughout the game.
Recommended practices include:
- Consistent visual style.
- Clean graphics without visible artifacts.
- Properly scaled assets and textures.
- Balanced audio volume levels.
- Appropriate sound and music quality.
The game's presentation should accurately match the expectations created by its title, screenshots, trailers, and cover images.
Responsiveness and Difficulty Balance
Player actions should feel immediate and responsive.
Even small delays between player input and visual feedback can negatively affect the perceived quality of the game.
We recommend:
- Immediate feedback for player actions.
- Smooth UI transitions.
- Predictable controls.
- Gradual difficulty progression.
Avoid sudden difficulty spikes that block player progress for extended periods.
Keyboard Layouts and System Shortcuts
Where keyboard input is supported, controls should work consistently across different keyboard layouts, including layouts such as:
- QWERTY
- AZERTY
- QWERTZ
Prefer action-based input handling instead of relying exclusively on specific physical key positions.
Do not intercept operating system or browser shortcuts that players expect to function normally.
In particular:
- Do not block
Escoutside fullscreen mode. - Do not override
Ctrl+WorCmd+W. - Respect platform-standard navigation and browser behaviour whenever possible.