Projects

A project is one app. One idea, one codebase, one chat with the agent. Most people start with one project, then add more as they build more apps. There's no limit on how many you can have on paid plans.

This page covers what you can do with projects from the dashboard.

Where your projects live

Go to Dashboard → Projects. You see a grid of cards, one per project. Each card shows:

• The project name.
• A thumbnail of the app's current screen (if there's one to show).
• When it was last edited.
• A star in the corner if you've starred it.

The most recently edited project sits at the top by default.

Starting a new project

Two paths.

From scratch

1. Click New project (top right).
2. A modal appears. Give it a name.
3. Click Create.
4. You land on the blank canvas. Describe your app to the agent.

The project is real. A real database, real file storage, real preview. From the moment you click Create.

From a template

If you'd rather start with a working app and tweak it, go to Dashboard → Templates instead. See Templates for the full flow.

Finding a project

Two ways:

• Search. A search box at the top of the projects page. Filters in real time as you type.
• Sort. A dropdown next to the search lets you sort by: Last edited, Created date, Name, Starred.

Starring projects

Click the star icon on any project card to favourite it. Useful when you have a lot of projects and want one-click access to a few.

Starred projects:

• Get a separate view. Go to Dashboard → Starred for just your starred projects.
• Sort first by default in the main list (toggle this in the sort dropdown).

Un-star by clicking the star again.

Renaming a project

Two places:

• From the project card: hover over the card, click the menu icon (three dots), pick "Rename." Type the new name, press Enter.
• From inside the project: click the project name in the top bar of the builder. Type the new name there.

The name is just a label. It doesn't change anything in the code or the URL. Rename freely.

Duplicating a project

Useful when you want to:

• Experiment with a big change without risking the original.
• Spin off a variation of an idea.
• Hand a clean copy to someone else.

From the project card menu (three dots), click Duplicate. The new project is a full copy: same screens, same data structure, same brand kit. The Supabase backend is shared - connectors are account-wide, so both projects read and write the same database. If you want the copy's data kept separate, ask the agent to set the duplicate up with its own tables.

Deleting a project

From the project card menu, click Delete. A confirmation dialog asks you to confirm by typing the project name.

What gets deleted:

• The project's conversations and chat history with the agent.
• The project's metadata inside Appsanic.

What doesn't:

• Your code on GitHub (if you exported there). That's in your GitHub account.
• Your Supabase data: that's in your Supabase account. You decide whether to delete the Supabase project too.
• Your published app: deleting an Appsanic project doesn't unpublish an app from the App Store or Play Store. Those listings are in your developer accounts.

Deletion is immediate and permanent. There's no recovery of the project itself. If you deleted one by accident, the parts that live in your accounts survive: if you exported to GitHub the code is intact there, your Supabase project keeps running, and a published app keeps running. You can create a fresh Appsanic project, point it at the same GitHub repo, and resume. What you can't get back is the conversation history, the in-Appsanic preview state, and the brand-kit attachment.

Sharing a project

Projects belong to your account, not to you personally. On Free and Pro you are the only person on the account, so you are the only person who can open them.

On Business, every team seat you create can open, edit, and build the account's projects. See Your Account & Team Seats.

Outside Appsanic you can also:

• Export to GitHub and add collaborators there. See Exporting to GitHub.
• Hand off the Supabase project to a teammate as a Supabase collaborator. They can manage data and users from the Supabase side while you keep building in Appsanic.

Limits

• Free plan: 5 template projects, no custom projects.
• Pro / Business: unlimited projects.

See Plans and Billing for the full plan breakdown.

Things worth knowing

• The project URL is its address inside Appsanic: appsanic.com/build/<project-id>. Bookmarkable; share-able only with people on your account (today).
• No auto-archive: inactive projects don't get cleaned up on you. They sit there as long as your account exists.
• Project metadata sync: if you change the project name in the builder, the dashboard card updates within a few seconds.

Under the hood (for engineers)

• Stored in the projects table, scoped to user via RLS.
• The dashboard grid is paginated cursor-style via /api/projects. First page is server-rendered; subsequent pages load on scroll.
• Sort/filter state lives in the URL (?q=...&sort=...) so a refresh keeps your view.
• Deletion cascades to the project's conversations on the Appsanic side. Uploaded assets are NOT deleted - the asset library is account-wide, so files stay available to your other projects. External resources (Supabase, GitHub) are untouched. By design.

Next

Read Conversations for how to organise multiple chats inside a single project, or Templates for starting from a working app.