Once your App is connected to your workflows, you might find it needs to be more than a single screen.
Routing allows you to create multi-page Apps and helps the people using your App move between different views. Here's what that makes possible:
Multiple pages, each with their own unique URL. For example, an onboarding App might have one page for submitting new hire details and another for tracking onboarding progress.
Deep linking and persistence. You can link directly to a specific page within your App, and if someone refreshes the page, they'll stay right where they were.
Consuming the path and URL parameters. Your App can read information from the URL, which is useful for showing the right content based on where a user has navigated.
The good news is that the App builder has full context of routing, so you don't need to wire it up manually. To build a multi-page App, simply describe what you want in your prompt, just as you would for anything else. For example: "Add a second page that shows a summary of all submitted requests."
It's also worth knowing that routing is fully supported within Cases and Collections, where the URL itself isn't visible to the user, but navigation still works smoothly.
❗️Important
🖐️ Try this: App routing
New to emulations? Swap between watch, try, or scroll mode.