> 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/guides/build-web-app.md).

# Build a web app

A complete example of building and shipping a web app in GenVibe.

We'll build a **SaaS landing page with a waitlist form**.

## 1. First prompt

> Build a modern SaaS landing page for a product called "Inboxly" — an AI email assistant. Include a hero with a headline and call-to-action, a features section with three cards, a pricing section with two tiers, and a footer. Add a waitlist form that collects an email address.

## 2. Refine the look

> Use a dark theme with a purple accent color.

> Make the hero headline bigger and add a subtle gradient background.

> Add logos of "trusted by" companies as grayscale placeholders.

## 3. Make the form work

Connect [Supabase](/integrations/supabase.md), then:

> Use Supabase to store waitlist emails, and show a "You're on the list!" message after submitting.

## 4. Polish for mobile

> Make sure everything looks good on mobile — stack the feature cards and shrink the hero text on small screens.

## 5. Publish

Click **Publish** for a live `genvibe.app` link in one click — or connect a custom domain on a paid plan. You can also deploy to Netlify.

{% content-ref url="/pages/cHGLDu0PBlw8uuOobBoF" %}
[Deploying your app](/features/deployment.md)
{% endcontent-ref %}

## Recap

You went from one sentence to a deployed, working landing page with a real backend — using only chat. The same loop scales to dashboards, tools, and full apps.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.genvibe.pro/guides/build-web-app.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.