Get it running
Put the complete demo on a physical iPhone or Android phone.
The supported path is an Expo development build. Expo Go is useful for a quick look, but it cannot prove all of this starter's native behavior.
Ask your AI
Read AGENTS.md and agent-skills/get-it-running.md. Get this starter running on
my physical [iPhone / Android phone]. Use an Expo development build. Check Node,
pnpm, dependencies, and Expo Doctor first. Do not wire production providers.
Explain any account or device action before asking me to do it.What the agent will do
Verify Node 22.13+, Git, Corepack/pnpm, run pnpm install, and run
pnpm run doctor.
Ask you to sign in to Expo, then create a development build with EAS for iOS or Android.
Give you the EAS install link. Open it on the phone and install the build.
Run pnpm start, then open the development-server link or scan its QR with
the installed development app.
The underlying commands look like this:
pnpm dlx eas-cli@latest login
pnpm dlx eas-cli@latest build --profile development --platform ios
# or: --platform android
pnpm startEAS cloud builds do not require local Xcode for this flow. Apple device signing rules may still require an Apple developer path depending on the device and distribution choice; your agent should explain that before proceeding.
Optional Expo Go preview
pnpm start:goIf the currently available Expo Go cannot load SDK 57 or a native module, stop debugging that route and use the development build. Do not remove native dependencies to make Expo Go happy.
Success looks like this
- the Vela icon and splash appear,
- Continue as review demo opens the app without keys,
- Today, Scan, Coach, and Profile all render,
- saving a code edit triggers hot reload,
- camera, push, purchases, and biometrics are not called “verified” until their real adapters are wired and tested on the right build.