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

# Use Cases

> Who uses Bilt and what they build

Bilt is used for building and shipping native mobile apps — from quick prototypes to production apps on the App Store and Google Play.

## By audience

### Founders and makers

**Goal**: Ship a mobile app without hiring developers or learning to code.

You describe your app idea in the [dashboard](https://bilt.me). Bilt's AI builds it, you refine through chat, and publish to the App Store — all from the browser.

**Example workflow**:

1. "Build a habit tracker with daily streaks and reminders"
2. Iterate on design and features through conversation
3. Enable Bilt Cloud for user accounts and data persistence
4. Submit to the App Store

### Product and design teams

**Goal**: Go from concept to working prototype in hours, not weeks.

Use Bilt for rapid prototyping, stakeholder demos, and MVPs. Share preview links for feedback. Export code when you're ready to hand off to engineering.

**Example workflow**:

1. Describe the product concept with detailed specs
2. Share preview links with stakeholders for feedback
3. Iterate based on feedback in real time
4. Push to GitHub for the dev team to continue

### Developers

**Goal**: Skip boilerplate and generate app scaffolds fast.

Use Bilt to generate the initial app structure, then export the React Native code and continue development in Xcode or your preferred environment.

**Example workflow**:

1. "Generate a social media app with feed, profiles, and messaging"
2. Connect GitHub to sync the code
3. Clone the repo and add custom native modules
4. Deploy through your own CI/CD pipeline

### AI agents

**Goal**: Build and deploy apps as part of automated workflows.

AI agents (Claude, Cursor, OpenClaw) use Bilt's [MCP tools](/docs/api-reference/overview) to create projects, send build instructions, and manage deployments — no human intervention required.

**Example workflow**:

1. Agent calls `bilt_create_project` with an app description
2. Agent sends feature requests via `bilt_send_message`
3. Agent monitors progress via `bilt_get_session`
4. Agent retrieves the preview URL when complete

## By use case

| Use case                     | Bilt suitable? | Notes                                           |
| ---------------------------- | -------------- | ----------------------------------------------- |
| MVP from an idea             | Yes            | Core use case — describe it, build it, ship it  |
| Production app for App Store | Yes            | Native iOS builds, full App Store pipeline      |
| Rapid prototype              | Yes            | Working app in minutes, shareable preview links |
| Internal business tool       | Yes            | Dashboards, operational apps, team utilities    |
| Agent-driven automation      | Yes            | Full MCP API for programmatic control           |
| Web-only product             | No             | Bilt builds native mobile apps, not websites    |
| Backend-only / API           | No             | Bilt handles mobile app UI and logic            |

## What Bilt is not for

* **Web-only products** — Bilt is for native mobile apps (iOS and Android)
* **Backend-only work** — The focus is app UI and logic; deep backend work may need custom code
* **Non-app workflows** — Bilt is specifically for building and deploying mobile applications

## Get started

<CardGroup cols={3}>
  <Card title="Dashboard quickstart" icon="bolt" href="/docs/quickstart">
    Build your first app
  </Card>

  <Card title="MCP quickstart" icon="plug" href="/docs/quickstart-mcp">
    Connect from an AI agent
  </Card>

  <Card title="Prompting guide" icon="sparkles" href="/docs/guides/prompting">
    Write better prompts
  </Card>
</CardGroup>