Skip to content

Apps inside a project

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.

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

Per appWhat that means
Chat historyEach app has its own conversation with the AI
FilesSeparate codebases — a Next.js app is not your website’s React build
Live previewThe preview follows the app you’re in — a desktop app opens on your own machine instead
Pages listEach app has its own routes and folders
ServerThe Server tab shows that app’s machine, not the project’s main one
PublishingPublish 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.

The things that should be shared, are:

  • The project’s CRM connection — one customer list, one product catalog, one set of orders behind all of them.
  • Team members and their roles.
  • The project’s domain — put each app on its own subdomain (app.mysite.com, store.mysite.com).
  • The project’s cloud database — one backend, read and written by every 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 are part of the ESTAGE Atlas plan, and the card unlocks it in place if your account doesn’t have it yet.
  • Web apps are billed per app: dev hours while you build, and a dedicated machine once you publish.
  • Desktop apps run on your own computer while you build them, and ship as a Mac or Windows installer people download.