Builder Settings
Manage Screens
Build and maintain the app screen map that powers navigation, tab targets, auth landing destinations, and component-level actions that route by screen ID.
Most app routing references this screen structure.
Screen edits propagate into multiple settings areas.
Finalize core screens before tab and auth configuration.
How screen management drives app behavior
Add and organize screens
Create and reorder screens so runtime navigation follows your intended app structure.
Maintain target integrity
Tab bars and action links depend on valid screen targets from this section.
Support auth routing
Signed-in landing behavior relies on available non-auth screens from this map.
Control change risk
Deleting screens can orphan links, so structural edits should be reviewed across dependent settings.
Manage screens safely
Standard flow
- Open App Settings & Deploy → Manage Screens.
- Add, rename, reorder, or remove screens.
- Confirm default/target screens where relevant.
- Save changes.
After changes
- Re-check Bottom Tab Bar target screens.
- Re-check Admin Tab Bar target screens.
- Re-check Auth Session landing destination.
Common mistakes to avoid
Deleting active targets
Before removing a screen, verify no tab or action currently points to it.
Configuring tabs too early
If screen structure is still changing, tab setup can become unstable and require repeated fixes.
Ignoring auth dependencies
Landing options rely on non-auth screens, so ensure at least one valid non-auth destination exists.