Skip to main content

Create a New App

Apps are built through prompts rather than component-by-component assembly. This page covers how to create an app, what the editor contains, and the common UI patterns the AI can generate.

To start, click Create new app in App Builder and give it a name. To start from an existing app instead, use Copy app.

Order of operations​

Before writing your first prompt, make sure the foundation is solid:

  1. Define the app's goal in one sentence — what will users do with it?
  2. Confirm that the workflows and tables your app needs are stable and working.
  3. Run any new workflows at least once so App Builder knows their input and output shape.
  4. Open the Resources panel, add the relevant workflows and tables, and set a clear alias for each.
  5. Write a plain-language prompt — mention the resource alias, the app type, and the key fields to show.
  6. Review the preview, refine with focused follow-up prompts.
  7. Save to lock in the current state, then Publish.

The editor​

Once an app is created or opened for editing, you are in a build session. The editor has three main areas:

Notes​

A free-text scratchpad attached to the app. Use it to record the app's purpose, decisions made during development, known limitations, or instructions for the next person who edits it. Notes are not visible to end users.

Assets​

The Assets panel lists the static files attached to the app — images, icons, or other files the AI can reference in the generated interface. Upload files here before prompting if you want them included in the app's design.

Build Prompt​

The Build Prompt is where you describe what you want. Type a plain-language instruction and the AI generates or updates the app. Each prompt builds on the current state — you do not need to describe the entire app on every prompt, only what you want to change or add.

Connecting data​

Apps read and write data through the resources you connect. Open the Resources panel to add workflows and tables.

  • Workflows bind to the output of their final step.
  • Tables expose their columns directly.
  • Always give each resource a short, descriptive alias — this is the name you use in prompts. Saying "show data from orders_table" is clearer than "show the order data."

For full guidance on setting up resources, see Resources.

Common UI patterns​

The AI selects components based on your prompt. Common patterns include:

PatternWhen to use it
DashboardSummary information, grouped or charted on one screen
Search → DetailLet users search records and click to see full details
List with FiltersSortable, filterable record lists
FormCollect user input and save records via a workflow
TrackerOperational view surfacing records that need attention

Mention the pattern explicitly in your prompt — for example: "Build a search-to-detail view using supplier_table."

Role-based UI​

You can make parts of the app visible only to specific user roles:

  1. Define roles in the editor and attach Vince Platform roles or individual users.
  2. Specify role-specific behaviour in your prompts — for example: "Suppliers should only see their own orders."
  3. Save and test with accounts that have the relevant roles assigned.

For full details on configuring per-app roles, see In-App Roles.

Further reading​

Last updated on