{"slug":"app-structure","title":"App structure","summary":"The App tab shows the app as it describes itself: the screens the assistant planned and built, the navigation tree, and shared components.","body":"Open **App** in the project panel. The list comes from the assistant's plan for the app, checked against the routes the source actually serves.\n\n## Screens\n\n- A **built** screen can be clicked to open it in the preview. The screen you are on is highlighted.\n- A **planned** screen is greyed out. The assistant listed it but has not built it yet. Ask it to build that screen.\n- A route the plan never mentioned still appears, so nothing that exists is hidden.\n\nScreens are disabled while the assistant is working, because it is driving the preview.\n\n## Structure\n\nThe navigation tree shows how screens are grouped: tabs, stacks, and the screens inside them. Use it to check that a screen is reachable from where you expect.\n\n## Components\n\nShared components are the pieces several screens reuse, such as a card or a header. Click one to open its file in **Code**.\n\n## When the structure disagrees with the plan\n\nWhile a turn runs, the tab says the structure is updating. After it ends, a warning lists anything the plan and the source disagree on. Ask the assistant to reconcile it, for example: \"The plan lists a Settings screen that doesn't exist. Build it and link it from Profile.\"","sectionSlug":"build","sectionTitle":"Build your app","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"preview","title":"Preview"},"next":{"slug":"design-tokens","title":"Design tokens"}}