> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use cases

> Landing pages, waitlists, portfolios, dashboards, internal tools, CRMs, SaaS MVPs, and more — how to build them in Mythex.

# Use cases

Mythex is for **apps and websites** you can preview in the browser and [publish](/publish/overview) to a public link.

Each guide below is a thin, shippable slice: a starter prompt, the usual build loop, and honest limits (for example app login and payments are [bring-your-own](/recipes/integrate-any-api)).

If you already know the niche, you can also start from a [template prompt](/features/website-templates) at [mythex.ai/templates](https://mythex.ai/templates).

## Stack and language

You do **not** have to use a specific language. The starter prompts below assume a normal web app (default is **Vite + React + TypeScript + Tailwind**). If you care about the stack, say it in the first message:

* **Front end:** Next.js, static HTML, or keep the default Vite + React
* **API / backend:** Node, [Python](/guides/python-backend), C#, Java, and similar — ask for a **Dockerfile**; [publish](/publish/how-to-publish) deploys the container to Fly
* **Both at once:** a website plus an API in one project — [multi-service preview](/features/multi-service)

See [How the tech is chosen](/features/templates) and [API backends](/guides/api-backends).

**Today this is web.** [Phone / mobile apps are coming soon](/introduction/what-you-can-build) (not App Store / Play submit yet). Mythex is not a general-purpose IDE for every language — it is an app builder with a real workspace.

## Websites

<CardGroup cols={2}>
  <Card title="Landing page" href="/use-cases/build-a-landing-page">
    Hero, features, FAQ — preview, polish, publish.
  </Card>

  <Card title="Waitlist" href="/use-cases/build-a-waitlist">
    Capture emails with a form and optional database.
  </Card>

  <Card title="Portfolio" href="/use-cases/build-a-portfolio">
    Work grid, about, contact — personal or studio.
  </Card>

  <Card title="Booking page" href="/use-cases/build-a-booking-page">
    Appointments for a salon, consultant, or small shop.
  </Card>

  <Card title="Store or catalog" href="/use-cases/build-a-store">
    Product listings; payments only if you connect a provider.
  </Card>
</CardGroup>

## Apps & tools

<CardGroup cols={2}>
  <Card title="Dashboard" href="/use-cases/build-a-dashboard">
    KPI cards, charts, and list pages.
  </Card>

  <Card title="Internal tool" href="/use-cases/build-an-internal-tool">
    Replace a painful spreadsheet with a team UI.
  </Card>

  <Card title="Admin panel" href="/use-cases/build-an-admin-panel">
    Dense tables, search, and edit drawers.
  </Card>

  <Card title="Simple CRM" href="/use-cases/build-a-crm">
    Contacts, deals, pipeline — not Salesforce sync.
  </Card>

  <Card title="Client portal" href="/use-cases/build-a-client-portal">
    A place for clients to see status, files, or requests.
  </Card>

  <Card title="SaaS MVP" href="/use-cases/build-a-saas">
    Marketing page + one core feature you can demo.
  </Card>

  <Card title="AI inside your app" href="/use-cases/build-an-ai-app">
    Chat or summaries with your own provider keys.
  </Card>
</CardGroup>

## The same loop every time

1. **Describe** the product in plain language (workflow, not a feature dump)
2. **Preview** on desktop and the phone-size frame
3. **Iterate** in **Build** — use **Plan** before big changes
4. Add a [database](/features/database) or [uploads](/features/storage) when data must persist
5. Run [App Testing](/features/app-testing) (`/test`) on the happy path
6. [Publish](/publish/how-to-publish) a public URL

See [From idea to live app](/getting-started/idea-to-live-app) for the full journey.

## Related

* [What you can build](/introduction/what-you-can-build)
* [Quick start](/getting-started/quickstart)
* [Effective prompts](/prompting/effective-prompts)