Skip to content

Design requirements

How the game looks and how players interact with it. Channel‑specific extras live on the channel pages.

  • MUST render correctly across the channel’s supported viewport range.
  • MUST adjust on viewport change (resize, orientation, on‑screen keyboard).
  • MUST preserve game state on resize. Restarting the level is a rejection.
  • MUST support touch and mouse for every interaction.
  • MUST NOT drop, delay, or double‑fire input.
  • SHOULD support keyboard for directional / text input where it fits.
  • SHOULD close modals on Esc (and MUST NOT call preventDefault() on it).

Text and graphics MUST render cleanly at every supported resolution and pixel density. Blurry or stretched UI is a rejection.

  • MUST NOT display social sharing prompts outside FRVR modules (social, community, crossplay).
  • MUST NOT open external links outside FRVR.navigation, and MUST gate the entry point on FRVR.navigation.canNavigate() or FRVR.navigation.canOpenChannelAppStore(). Hide the button when the answer is false. Channels differ on whether external links are allowed at all; a button that does nothing is a rejection.
  • MUST NOT present additional EULAs / user agreements.