This article is part of Custom screens: Server side rendering which explains how to configure Custom screens via the dashboard.
Add a new custom screen in the dashboard
To do so, login with your admin account, then navigate to Settings > Custom screens.
Here, click the Create new screen button.
In the dialog, perform the following:
- Enter the URL of the endpoint that will build the custom screen payload on your backend.
- Enter the English name of the custom screen. This is the string that will show in the side menu of the app. Optionally, you can add translations for all the locales enabled for your account — if the user of the Driver app will use a different language than English on their device, the name of the custom screen button will use the translated value.
- Enable the custom screen using the toggle (this can also be done later).
- Optionally: check the Embed user profile fields in JWT Token. See details here.
Once you have configured your settings, click Save. After saving, you will be presented with the public key that you can use to verify the request MotionTools launches to your backend when a custom screen gets opened — details .
Once the public key is saved, click Close.
Don’t worry if you forget to copy the public key. You can always access it by opening the custom screen configuration once again.
You are now back in the list of configured custom screens, and your new screen is displayed in the list. Since we have already enabled it, it will also display in the driver app as seen below.
However, if the user would now attempt to open the 'Tips' Custom screen, it would show an error as the backend is not set up just yet.
In part 3, we will setup a simple backend that returns a few static components that would then render in our custom screen.
▶️ Continue to Part 3: Implement a simple endpoint to return a static custom screen