Custom product interfaces
A custom interface can express a product's rules and style. The platform still owns identity, connectivity, authorization and recovery.
Begin with the player's task
List what players need to observe and which actions they can take before choosing a layout. Present private information only to authorized participants.
If the standard interface already explains the experience clearly, complete the core flow before deciding what custom presentation would improve it.
Use the current UI contract
Read the custom UI contract, capabilities and SDK types provided by the creation task. Build the UI Artifact as required and integrate it through the controlled runtime surface.
Use only permitted projections and actions. Do not infer identity, duplicate platform state machines, call internal endpoints directly or embed secrets in frontend files.
Check quality
- Important information and actions work on narrow screens.
- Keyboard controls have visible focus.
- Loading, waiting, denied access and errors are understandable.
- Reconnection uses the state supplied by the platform.
- Copy and assets support the product's declared languages.
Deliver and repair
Build, validate and playtest the UI with the product. Fix working content and generate a new candidate instead of replacing a live page outside the publication flow.
Continue with validation and playtesting or the development reference.