> 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-mobile-app.md).

# Build a mobile app

A complete example of building a cross-platform mobile app with GenVibe.

We'll build a **workout logger** for iOS and Android.

## 1. First prompt

Say "mobile app" so GenVibe scaffolds React Native + Expo:

> Build a mobile workout logger app. Bottom tab bar with two tabs: Log and History. On Log, I can pick an exercise, enter sets and reps, and save. History shows past workouts grouped by date. Clean, modern mobile design.

GenVibe builds the app and shows it in a **phone frame** preview.

## 2. Iterate

> Add a "+" button to create a custom exercise.

> Show a weekly summary card at the top of History with total workouts this week.

> When I save a workout, show a quick confirmation toast.

## 3. Persist data

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

> Use Supabase to store workouts so they sync and persist, with email login so each user sees only their own data.

## 4. Test interactions

Use the device-frame preview to tap through tabs, add entries, and check navigation. For the real feel, open the **QR code** in the preview toolbar and scan it with **Expo Go** to run the app on your own phone with live reload.

## 5. Ship to the stores

Click the **Android icon** in the preview toolbar to build an installable **APK** (to try on a phone) or an **AAB** (to publish on Google Play) — see [Android builds](/features/android-builds.md). You can also export to [GitHub](/integrations/github.md) and run the build yourself.

{% hint style="success" %}
Building real mobile apps from a prompt is GenVibe's standout feature — and it's on the free tier.
{% endhint %}


---

# 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-mobile-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.