Quality guidelines

Funox curates for quality. Polish, originality, and respect for the player are what separate accepted games from rejections.

Visual polish​

• Art should be consistent in style across all screens.
• No placeholder graphics in the submitted build.
• UI must scale cleanly from 320 px wide to 1920 px wide without overlap.
• Text remains readable at all supported sizes (minimum 14 px body, 18 px for primary actions).

Audio polish​

• Provide a mute toggle that persists across sessions.
• Sound effects should not clip or distort on default volume.
• Background music must loop seamlessly.
• Default volume: 70% or lower on launch.

Performance polish​

• No frame drops below 30 fps sustained during normal gameplay.
• No noticeable input lag — touch and mouse events should respond within one frame.
• Loading screens must show progress, not just a static logo.

Content originality​

• Original art, characters, music, and code, or commercially licensed.
• AI-generated assets are allowed only with confirmed commercial rights and reasonable visual quality.
• No assets ripped from other games, movies, or franchises.

UI conventions​

• Game name visible on the main menu or loading screen.
• Settings screen with at least: audio toggle, controls reference, credits.
• Game-over and pause states accessible from active gameplay.
• All buttons have hover and pressed states on desktop.

Localization (recommended)​

While not required at launch, supporting multiple languages significantly improves reach. Funox players come from across the world. Consider:

• English as the default.
• Externalizing strings so they can be added later.
• Avoiding hard-coded text inside images where possible.

What we reject​

• Re-skins of competitor games
• Games with broken core mechanics
• Games that crash on common devices
• Games that violate the advertisement rules
• Games that ship debug or unfinished levels
• Games with placeholder names like "MyGame" or "Untitled"