Skip to main content

Use cases

Mythex is for apps and websites you can preview in the browser and publish 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). If you already know the niche, you can also start from a template prompt at 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, C#, Java, and similar — ask for a Dockerfile; publish deploys the container to Fly
  • Both at once: a website plus an API in one project — multi-service preview
See How the tech is chosen and API backends. Today this is web. Phone / mobile apps are coming soon (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

Landing page

Hero, features, FAQ — preview, polish, publish.

Waitlist

Capture emails with a form and optional database.

Portfolio

Work grid, about, contact — personal or studio.

Booking page

Appointments for a salon, consultant, or small shop.

Store or catalog

Product listings; payments only if you connect a provider.

Apps & tools

Dashboard

KPI cards, charts, and list pages.

Internal tool

Replace a painful spreadsheet with a team UI.

Admin panel

Dense tables, search, and edit drawers.

Simple CRM

Contacts, deals, pipeline — not Salesforce sync.

Client portal

A place for clients to see status, files, or requests.

SaaS MVP

Marketing page + one core feature you can demo.

AI inside your app

Chat or summaries with your own provider keys.

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 or uploads when data must persist
  5. Run App Testing (/test) on the happy path
  6. Publish a public URL
See From idea to live app for the full journey.