Start here

You downloaded a folder of code. The fastest useful path is:

1. prepare your computer,
2. create a development build,
3. install that build on your phone,
4. explore the complete mock product,
5. rebrand first and connect providers later.

Docs link: https://mobile-starterkit.getdesign.md/docs

Bookmark it. The same guidance is available inside the kit, but this version is easier to browse and search.

1. Give the folder to your AI coder

Open the kit folder in Codex, Claude Code, Cursor, VS Code with an AI extension, Gemini, or another tool that can read and edit a local project. Send:

Get this project running on my physical phone. Read AGENTS.md and
agent-skills/get-it-running.md first. Use the supported Expo development-build
path. Do not wire providers or create paid accounts.

The agent will check Node, pnpm, install dependencies, and run Expo Doctor.

2. Build the development app

The complete path uses an Expo development build. Think of it as your own private version of Expo Go, built with the native modules this project needs.

You will need a free Expo account for the cloud build. Your agent should stop and ask before anything requires a paid Apple or Google developer account.

For a quick UI-only attempt, pnpm start:go may work in Expo Go. It is not the supported proof for purchases, push, biometrics, camera, or final native config.

3. Explore without API keys

On the sign-in screen, choose Continue as review demo. Walk this loop:

Onboarding → Today → Scan → Analyze demo meal → Coach → Activity → Profile

Also try all three paywalls, notifications, English and Spanish, light and dark themes, offline behavior, and account deletion. The demo must remain usable without Supabase, RevenueCat, or AI keys.

4. Make it yours before wiring services

Send this next:

Read AGENTS.md, DESIGN.md, DESIGN-DARK.md, FEATURES.md, and
agent-skills/make-it-yours.md. Ask me for my app name, target user, promise,
premium feature, and visual direction. Rebrand the mock product first. Preserve
all integration seams and keep English and Spanish complete.

This order matters. Provider dashboards, store product IDs, legal copy, app identifiers, and deep links should describe your product—not the Vela example.

5. Activate only what you need

When the mock product is right, move to Production integrations. The recommended order is identity and data first, then payments and product features, then observability and shipping.