Review app details
By the end of this page you will know where to find every generated artifact for your app — its requirements, structure, data model, API, and roles.
Prerequisites
- An app that has started generating (The generation flow).
The workspace tabs
The app workspace has three top-level tabs, switchable with keyboard shortcuts: Code (⌘1), Preview (⌘2), and App Details (⌘3).
App Details is a composite panel with five sub-tabs, in order: Requirements, Graph, Data Plan, API Doc, and Roles.
Requirements
The requirements specification qRaptor generated from your prompt — see The generation flow for how you approve or reject it. Once approved, this sub-tab remains available as a reference for what the app was built to do.
Graph
The App Graph — a canvas of the app’s UI, Backend, and Shared nodes, showing how the app is structured end to end.
Data Plan
The Data Plan sub-tab shows your app’s data model — an ER-style view of tables, columns, and relationships that qRaptor generated to support your app.
If your app needs a schema change, describe it in the chat panel rather than editing generated code directly — qRaptor keeps the Data Plan, Graph, and code in sync.
API Doc
The API Doc sub-tab documents the OpenAPI contracts for your app’s backend, with a try-it explorer so you can call an endpoint directly from the docs view.
Roles
The Roles sub-tab lists the RBAC roles defined for your generated app (e.g. Admin, Staff) and, for each role, shows:
- Page Access — which pages the role can view, edit, or delete.
- Table Permissions — the same view/edit/delete breakdown, but per data table.
- Data Scope — how much of each table’s data the role can see (e.g. All records, or a scope restricted to the user’s own rows).
- Test Credentials — a ready-made email and password for that role, with copy buttons, so you can sign in and test as that role without creating an account by hand.
Test Credentials on this tab are what you use to sign in to the Preview of an authenticated app.
Common issues
- Data Plan doesn’t match what I asked for — Ask qRaptor to adjust it directly in chat; avoid editing the schema by hand mid-generation.
- API Doc missing an endpoint — The endpoint may not have been part of the approved requirements. Request it via chat, then re-check API Doc once the build completes.