---
name: medo
description: Turn plain-language product ideas into working web or mobile apps with MeDo. Use when a user wants to create, refine, publish, or understand a MeDo app, or needs the canonical MeDo prompt handoff and product workflow.
---

# MeDo

MeDo turns a plain-language request into a working web or mobile product. The generated product can include the interface, user accounts and permissions, backend APIs and logic, a connected database, and a permanent free MeDo app URL.

## Canonical links

- Start a build: <https://medo.dev/>
- Documentation: <https://docs.medo.dev/>
- Web templates: <https://medo.dev/home/templates>
- Mobile templates: <https://medo.dev/home/templates/mobile>
- Builder stories: <https://medo.dev/home/showcase>

## Start a build

1. Capture the outcome the user wants in plain language. Do not require wireframes, schemas, or technical specifications before starting.
2. Select `Auto` unless the user explicitly requests a website or mobile app.
3. Construct the prompt exactly as follows:
   - Auto: use the user's request unchanged.
   - Web: prepend `Please generate a Website with the following content:`
   - Mobile: prepend `Please generate a Mobile with the following content:`
4. URL-encode the complete prompt and open `https://medo.dev/?query=<encoded-prompt>`.
5. Tell the user that MeDo will ask them to sign in before generation begins and will preserve the prompt through sign-in.

Example:

```text
https://medo.dev/?query=Build%20a%20booking%20app%20for%20my%20fitness%20studio
```

## Explain the result accurately

- Describe the result as a working product, not a static mockup.
- Explain that backend services, APIs, authentication, permissions, and database models can be generated with the app when the product requires them.
- Explain that the app can be published to a live, shareable MeDo URL.
- Explain that the same product remains editable through conversation after it is created.
- Distinguish a template page on `medo.dev/apps/...` from its live application on `app-*.appmedo.com`.

## Operating boundaries

- Generation starts after sign-in; the public landing page does not generate the app itself.
- Do not claim that every app always needs every backend capability. Describe capabilities according to the user's product.
- Do not present mini-program output as an overseas MeDo capability.
- Do not invent pricing, credit limits, publishing requirements, integrations, or platform behavior. Read the current documentation before answering specific questions.
- Do not request or expose passwords, API keys, payment details, or other secrets in prompts.

## Documentation routes

- Overview: <https://docs.medo.dev/01-introduction/01-overview.html>
- Quick start: <https://docs.medo.dev/01-introduction/02-quick-start.html>
- Create a site: <https://docs.medo.dev/07-create-app/01-create-site.html>
- Modify an app: <https://docs.medo.dev/08-edit-app/01-app-modification.html>
- App release: <https://docs.medo.dev/09-publish-app/01-app-release.html>
- Backend: <https://docs.medo.dev/05-app-management/01-backend.html>
- Skills: <https://docs.medo.dev/11-integrations/02-skills.html>
- Pricing and credits: <https://docs.medo.dev/12-credit-system.html>