Step 2: Set your frontend URL

The engine serves the outcomes. Your frontend shows them to the player. The platform connects the two by redirecting the player's browser to a URL you own. So the Game needs to know where your frontend lives.

What to do

1. When you create the Game definition in the hizi app, set the location of your frontend index document. A game launch redirects the player's browser to this URL.
2. On launch, the platform adds two GET parameters to that URL:
   • token: a short-life token. Your frontend uses it once, to exchange for a session.
   • login: the URL your frontend calls with that token. This call returns a long-life token, the game engine endpoint (backendUrl), and the player's gameSettings.
3. Read both parameters from your frontend's own query string. This completes the handshake. Step 3 covers what to do with them.

Testing before the URL is final

While you are still testing, you do not need to set the Game's frontend location yet. The hizi app's Game Launcher lets you pass a temporary frontend URL with the launch, in its extra or additional launch settings. Use this to point a test launch at a local or staging build without changing the Game itself. The exact field name and location can differ by app version. If you cannot find it, check the Game Launcher screen's own in-app help, or ask hizi.io support.

Where to read more

• Game Launch: documents this exact mechanism. It covers the redirect URL, the token and login parameters, and everything the login call returns.
• Game Launcher: see the Game Launcher entry in "What's What in the hizi app" for the test-launch tool. It supports a real or test player, a no-player demo, or a shareable static demo link.

Next: Step 3: Install the SDK.