> For the complete documentation index, see [llms.txt](https://docs.genvibe.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.genvibe.pro/getting-started/readme.md).

# Welcome to GenVibe

Build production-ready web and mobile apps from a single prompt.

GenVibe is an AI app builder. You describe what you want in plain English — or drop in a Figma design or a screenshot — and GenVibe writes the code, runs it live in a cloud sandbox, and lets you preview, edit, and deploy it. No setup, no local environment, nothing to install — and because the sandbox runs in the cloud, you can build from **any device: desktop, tablet, or phone.**

{% embed url="<https://www.youtube.com/watch?v=NCL9xErjHYw>" %}

## Why GenVibe

* **Prompt to app in seconds.** Describe an idea and watch a working app build itself, file by file, with a live preview.
* **Web&#x20;*****and*****&#x20;mobile.** Generate React, Vue, Svelte, and Angular web apps — or full **React Native + Expo** mobile apps you can preview in a device frame, or scan a QR code to run on your real phone.
* **Plan first, if you want.** For bigger ideas, switch on **Plan mode** and GenVibe asks a few questions and lays out a plan before it builds — you approve, then it goes.
* **Build from any device.** GenVibe runs in a cloud sandbox, so you can build and preview from a desktop, tablet, or phone — no install, no powerful machine required.
* **Your work is saved.** Projects auto-back up to the cloud — close the tab or switch devices and your apps and chat history are right where you left them.
* **Real code, not a black box.** Every file is editable in the built-in editor, and you can export to GitHub or deploy anytime.
* **Ship in one click.** Publish your app to a live `genvibe.app` link instantly — or connect your own custom domain on a paid plan (Netlify export is there too).
* **Design in, code out.** Turn a Figma file or a UI screenshot into a working app.
* **Backend included.** Connect Supabase for a database, authentication, and storage.

## Who it's for

* **Founders & makers** validating an idea without hiring a dev.
* **Designers** turning mockups into working products.
* **Developers** scaffolding and iterating faster than writing boilerplate by hand.

## What you can build

Landing pages, SaaS dashboards, internal tools, e-commerce storefronts, admin panels, mobile apps for iOS and Android, and more — all from natural language.

## Get started in 2 minutes

1. Go to [genvibe.pro](https://genvibe.pro) and sign in with Google.
2. Type what you want to build in the prompt box.
3. Watch it build, then keep chatting to refine it.

{% content-ref url="/pages/glIw8miPaQJaRKg24HYQ" %}
[Quick start](/getting-started/quick-start.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.genvibe.pro/getting-started/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.