Expo Mobile App Starter

A finished iPhone and Android app, built to be turned into yours by an AI coding agent. Out of the box it's Tally, an offline-first habit tracker: check in with one tap on any schedule (every day, weekdays, a few times a week, or every N days), keep streaks, see your history as a heat map, get reminders, and unlock Insights with a Pro subscription. You hand this folder to your agent, and it turns Tally into your app: a workout log, a plant-watering tracker, a medication reminder, a practice journal.

Built with:

• Expo SDK 57 (React Native 0.86, New Architecture) and Expo Router
• TypeScript (strict), SQLite on the phone (expo-sqlite) with numbered SQL migrations
• Local notifications (expo-notifications), haptics, JSON backups through the share sheet
• A purchases layer with a test store built in, ready for RevenueCat (and a release guard: store builds refuse the test store)
• Its own design tokens and components, light and dark themes, screen-reader labels and 44 pt touch targets everywhere

Using it with an agent

Open this folder with your coding agent (Claude Code, Codex, Cursor…) and describe the app you want. The agent reads AGENTS.md, asks you a few questions, then works in small, checked steps. It verifies its work with npm run check and takes screenshots of every screen it changes, in light and dark, at phone size.

The checks run on Windows, macOS and Linux with no phone, simulator, Xcode or Android Studio: the logic and database are tested on real SQLite, every screen is rendered in Jest and checked for accessibility, expo prebuild proves the native projects generate, and Playwright runs the main flows on the web version at phone size.

Running it yourself

You need Node 22.12 or newer (24 is tested). Then:

npm install
npm start            # scan the QR code with Expo Go on your phone, or press w for the web version
npm run check        # every check; ends with CODEPLATE CHECKS: PASS
npm run shots        # screenshots at phone size in shots/
npm run ios:shots    # on a Mac with Xcode: screenshots of the real app in the iOS Simulator, in shots/ios/

The checks find or install a browser for the screen tests themselves: Playwright's Chromium if it's there (npm run setup installs it), else your Chrome or Edge, else they download Playwright's Chromium once (about 150 MB). Set PW_CHANNEL=chrome (or msedge) to choose one.

To run on a simulator you need Xcode (macOS, for iOS) or Android Studio; to publish you need Apple and Google developer accounts, and EAS (Expo's build service) builds iOS apps without a Mac. docs/recipes/run-on-a-real-phone.md and docs/recipes/build-and-submit.md walk through both.

What's inside

• src/app/: the screens, one file per route: Today, Habits, Insights, Settings, a habit's page, the habit form, the paywall, the welcome screens.
• src/data/ and src/db/: the database (SQL migrations, repositories, backups) and the hooks the screens use.
• src/components/ and src/theme/: the components, the design tokens and the icon set.
• src/purchases/ and src/config/entitlements.ts: Pro, in one place.
• tests/: Jest (logic, database, screens, accessibility, contrast) and Playwright (flows at phone size).
• docs/: architecture, a customization map, and 15 step-by-step recipes, from renaming the core thing to submitting to the stores.

| Today | A habit | Insights | |---|---|---| | | | | | | | |

License

See LICENSE.md (CodePlate Pro License). You can use this code in your own apps, free or paid, with no credit needed. Every version you downloaded while your CodePlate plan included it stays yours. You can't resell or share the template itself.

The app icon, splash and interface icons are original and yours to ship (CREDITS.md). Third-party packages keep their own licenses:

• Expo, React Native and almost all other npm dependencies are permissive: MIT, ISC, BSD, Apache-2.0, BlueOak or 0BSD. SQLite is in the public domain.
• A few build tools differ, and none of them end up inside your app: lightningcss (MPL-2.0), the caniuse-lite browser data (CC-BY-4.0) and node-forge (BSD-3-Clause or GPL-2.0, your choice: pick BSD).

List the exact licenses with npm ls and each package's license field; the build-and-submit recipe covers an open-source notices screen.