Mobile App Boilerplate Documentation

A plain-words map of everything in the box, what is wired and working today, and what needs a key or an SDK before it runs.

Accept the GitHub invite and get the repository onto your computer, with a no-command-line path if you have never used git.

From a fresh clone to the app open in your browser with your own account on screen. Timed at under two minutes of commands.

The two .env files, what each key does, and why every paid integration runs green without one.

Point your coding agent at the repo once, so every request after this one starts with it already knowing where things go.

Ask Claude Code for a Notes screen, check its answer against four things, and see it running. About ten minutes, most of it the agent's.

Keep the included Hono and SQLite backend, or point the app at your existing Django, Rails, or Node API.

Put a screen behind a paywall with one component, and understand when Apple requires in-app purchase instead of Stripe.

Rename the app, change the colours and icon, and delete the demo screens so what is left is your product.

Custom JWT works out of the box. Clerk and Better Auth are adapter slots that need their SDK installed. Here is what each really costs.

Build and submit with EAS, ship JavaScript over the air with expo-updates, and deploy the backend if you are using it.

A when-you-need-X-read-Y map of the 9 guides and 27 recipes inside the repository, plus how updates reach you.