Target screen
Document the app and screen name, required parameters, and the minimum route that should open cleanly.
Retool Mobile
Map Retool Mobile links before users tap them in the field.
A focused Retool audit for teams trying to open a specific mobile app, screen, task, or record from a link, notification, email, or another workflow. We document the URL route, app context, record identifier, fallback behavior, and tests for mobile and desktop users.
Screen route
Record context
Fallback URL
Workflow
Deep links need context, not just a URL.
The important question is what should happen after the user lands: which app, which screen, which row, which mode, and what happens if Retool cannot open the mobile route.
Record handoff
Keep the record id, task id, or customer id explicit so the mobile screen can load the right state.
Fallback behavior
Define what web users, logged-out users, and unsupported devices should see instead of a broken link.
Deliverable
A testable route map for one Retool Mobile link flow.
The audit returns a route map, source checklist, and launch test matrix for one mobile link flow. It does not require handing over production access before the scope is clear.