Skip to main content
You can start an app yourself from the Apps page, or ask an AI coworker to build one for you. Either way, you need a role that can create apps: Owner, Admin or Editor.

​
Create an app from the Apps page

1

Open the Create App dialog

Go to Apps in the sidebar and click Create App.
2

Name your app

Type a Name, up to 50 characters. Pick something short and clear, like “Chargeback Tracker” or “Sales Pipeline”. You can rename the app later.
3

Check the app URL

Vybe fills in App URL from the name. Edit it if you like. The line under the field shows the full address, for example chargeback-tracker-acme.vybe.build.
4

Click Create App

Vybe shows “Creating your app…” and then opens the app editor on the Preview tab.

​
App URL rules

The app URL uses lowercase letters, numbers and hyphens. Vybe checks it as you type:
You can’t change an app’s URL after you create it. Renaming the app later changes its name, not its URL.

​
Ask an AI coworker to build an app

You can ask any AI coworker to build an app, in Slack or in the coworker’s Chats in Vybe:
Build an app where the sales team can log discount requests and managers can approve or reject them. Show pending requests first.
The coworker:
  1. Creates the app. The chat shows a Created app step with the app’s name. In Vybe, a card under it links to the app editor.
  2. Writes the code. While it works you see a step labelled Coding: …, which becomes Coded: … when it’s done.
In Vybe, the app’s preview opens next to the chat when the coworker creates the app and after each coding step. On a phone, tap Open preview to see it and Back to chat to return. If the preview crashes after you’ve sent a message, Vybe asks the coworker to fix it, with the same limits as in the app editor. See When the app shows an error. The coworker picks the app’s name and URL. You’re recorded as the app’s creator, so you control its access settings. The new app is linked to the coworker, so you can keep asking it for changes, data or a publish. You can also open the app editor and continue there. The coworker checks your permissions, not its own. If your role can’t create apps, it tells you that you don’t have permission to create apps in this organization.
Connect the integrations the app needs before you ask. The coworker can’t connect an integration for you while it codes.

​
What Vybe sets up for a new app

When you create an app, Vybe sets up:
  • A starter app. A working Next.js project with a home page that reads “Let’s build”. The AI replaces it with what you ask for.
  • A database. The app’s own PostgreSQL database, empty and ready for tables. See App data.
  • Background jobs. Everything the app needs to run scheduled and background work. See Background jobs.
  • Your brand. If your organization has a Brand Theme (Settings → Organization → General), its colors, logos and fonts are applied to the starter app, and the AI follows them. The theme is applied when the app is created. If your brand changes later, ask the AI to update the app.
  • An icon. Vybe generates an icon for the app in the background. The app card shows a placeholder until it’s ready.
  • A first conversation. The app’s chat opens with a conversation named “Creating your app”.
  • A preview. A private development copy of the app, shown in the Preview tab.
You can’t create an app while your organization is out of credits. See Plans and credits.

​
Write a good first prompt

Your first prompt shapes the whole app. Describe what the app is for, who uses it, what data it works with and what people do on each screen. Compare:
Make a dashboard.
with:
Build a customer support dashboard. Show open tickets in a table with columns for customer, subject, priority, status and age. Add a search bar and filters for priority and status. Let support reps change a ticket’s status from the table. Add a chart of tickets resolved per week at the top.
The first prompt makes the AI guess the data, layout and features. The second gives it enough to build the right thing.

​
What to include

  • The goal and the people. “A tool for the finance team to review expense reports.”
  • The data. Name the records and their fields, and how they relate. “Each project has many tasks. A task has a title, status (todo, in progress, done), assignee email and due date.”
  • Where data comes from. The app’s own database, a connected integration, a data query or an external database. “Pull deals from HubSpot.” See Connections.
  • What people do. Create, edit, approve, filter, export.
  • The layout. “A sidebar with Dashboard, Requests and Settings pages.” “A two-column layout with filters on the left.”

​
Start with the core, then build up

You don’t need every detail in the first prompt. Get the core working, then add one feature at a time:
1

Describe the core

Build a project tracker with a sidebar listing projects and a main area showing the selected project’s tasks.
2

Refine one part

Add a status badge to each task: green for done, yellow for in progress, grey for todo.
3

Keep iterating

Let me sort tasks by due date, and add a button that opens a form to create a task.
Small steps are easier to check, and each one gets its own checkpoint you can go back to. See Version history.

​
Prompt templates

Fill in the brackets to get started:
  • Records to manage: “Build a [resource] management page. Show [resource]s in a table with columns for [fields]. Add search, filters for [fields], and buttons to create, edit and delete [resource]s.”
  • Dashboard: “Create a dashboard showing [metrics] from [data source]. Add summary cards at the top for [KPIs], a [chart type] chart for [metric], and a date range filter.”
  • Form workflow: “Build a [workflow] form with fields for [fields]. Save submissions to the database and show a confirmation. Make [fields] required.”
  • Data import: “Create a page where people can upload a CSV with columns [columns]. Show a preview table and save the rows to the database when they confirm.”
You can attach screenshots or mockups to your prompt. The AI uses them as a reference for layout and style.

​
Next steps