# Apps inside a project

> A project can hold a Website, a Web app, a Mobile app and a Desktop app side by side — each with its own chat, files, preview, pages, server, and publishing, all sharing one CRM, team, domain, and cloud database.

Source: https://support.estage.com/platform-apps
Part of the ESTAGE Support help center (https://support.estage.com). Full knowledge base: https://support.estage.com/llms-full.txt

---

**A project is no longer one site.** A single ESTAGE project can hold a **Website**, a **Web app**,
a **Mobile app** and a **Desktop app** at the same time, and you switch between them from a
**switcher in the builder**.

Build the marketing site, the customer portal, the phone app and the program people install — once,
on one set of data — without wiring separate projects together by hand.

## Each app is a real, separate build

Ask the AI to change something and it changes **the app you have open**. Nothing bleeds into the
others.

| Per app | What that means |
| --- | --- |
| **Chat history** | Each app has its own conversation with the AI |
| **Files** | Separate codebases — a Next.js app is not your website's React build |
| **Live preview** | The preview follows the app you're in — a [desktop app](https://support.estage.com/platform-desktop-apps) opens on your own machine instead |
| **Pages list** | Each app has its own routes and folders |
| **Server** | The **Server** tab shows *that app's* machine, not the project's main one |
| **Publishing** | Publish each app independently, on its own schedule — a site to its domain, an app to its store or to an installer link |

Inspector edits, version history, and settings all follow whichever app you have open.

## What the apps share

The things that should be shared, are:

- The project's **[CRM](https://support.estage.com/crm) connection** — one customer list, one product catalog, one set of
  orders behind all of them.
- **[Team members](https://support.estage.com/project-settings-members)** and their [roles](https://support.estage.com/project-settings-roles).
- The project's **[domain](https://support.estage.com/domains)** — put each app on its own subdomain
  (`app.mysite.com`, `store.mysite.com`).
- The project's **[cloud database](https://support.estage.com/cloud)** — one backend, read and written by every app.

## Adding an app

On the project, add the target you want — a **Website**, a **Web app**, a **Mobile app** or a
**Desktop app** — and it appears in the switcher next to what you already have.

- [Mobile apps](https://support.estage.com/platform-mobile-apps) are part of the ESTAGE Atlas plan, and the card unlocks it
  in place if your account doesn't have it yet.
- [Web apps](https://support.estage.com/platform-web-apps) are billed per app: dev hours while you build, and a dedicated
  machine once you publish.
- [Desktop apps](https://support.estage.com/platform-desktop-apps) run on your own computer while you build them, and ship
  as a Mac or Windows installer people download.

> **Note**
>
> Creating a *new* project starts from a **"What are you building?"** chooser on the
> [dashboard](https://support.estage.com/workspace-dashboard) — Website, Web app, or Mobile app. Adding a second app to an
> existing project is the other route, and the only one for a Desktop app — same builder, one
> project.