Mobile App Starter Kit — an Expo / React Native starting point

Engineering & Development

An Expo / React Native project with the chassis of a mobile app already wired up: expo-router routing, zod form validation, i18n, MMKV storage, a react-query data layer, Jest and Maestro tests, and an EAS build configuration; docker compose brings up a web preview.

Subscribe & download See how to start

SubscriptionUS$49 per month

Last run2026-11-02

In practice

Readiness4 / 5

What you need

Few changes needed3 / 5

Who it is for

Solo developers and small teams starting a new mobile app: people who want an Expo starting point with routing, styling, forms, state management, localisation, tests and EAS build already wired up, rather than wiring each of those up themselves from an empty project.

How to start

$ docker compose up -d --build

Browse the files

Files in the product repository at the pinned commit. A few house files are left out of the zip.

File overview228 paths

▸__mocks__5

@gorhom/
expo-localization.ts
moti.ts
react-native-gesture-handler.ts
react-native-keyboard-controller.ts

▸assets4

adaptive-icon.png
favicon.png
icon.png
splash-icon.png

▸cli7

README.md
clone-repo.js
index.js
package.json
pnpm-lock.yaml
setup-project.js
utils.js

▸docs55

.gitignore
README.md
astro.config.mjs
package.json
pnpm-lock.yaml
public/
src/
tsconfig.json

▸scripts3

genrate-apk-and-install
i18next-syntax-validation.js
init-env.sh

▸server1

static-server.js

▸src85

app/
components/
features/
global.css
lib/
translations/

▫ATTRIBUTION.md

▫Dockerfile

▫LICENSE

▫LICENSE-99LL

▫PRODUCT.md

▫QUICKSTART.md

▫README-project.md

▫README.md

▫SECURITY.md

▫app.config.ts

▫babel.config.js

▫claude.md

▫commitlint.config.js

▫compose.yaml

▫delivery-manifest.txt

▫eas.json

▫env.ts

▫eslint.config.mjs

▫jest-setup.ts

▫jest.config.js

▫lint-staged.config.js

▫metro.config.js

▫nativewind-env.d.ts

▫package.json

▫pnpm-lock.yaml

▫tsconfig.json

▫uniwind-types.d.ts

▫Config and hidden files 41

Latest passing run

Clone → Checkout → Toolchain → Build → Run live

Pre-purchase Disclosure

What you are buying

The source code of an Expo / React Native project for starting a new mobile app: routing, styling, form validation, localisation, local storage, the data layer and the login screen are already wired up, with tests and an EAS build configuration included; once docker compose has started, you can open the web preview in a browser.

Derived from an MIT-licensed open-source Expo template; the containerised web preview, the removal of upstream’s account and project identifiers, and the Traditional Chinese documentation are ours. Delivery is a frozen snapshot: one zip file, taken from the product repository at revision 63415d4.

Known limitations

What the container provides is a web preview (react-native-web), not a native iOS / Android app
A native build needs your own Xcode or Android Studio, or an Expo account for an EAS cloud build
The App Store and Play Store listing process, the account fees and the review are not within the scope of the delivery
The first start fetches over the network: it pulls the base image and connects to the npm registry to install dependencies
The demo content connects to third parties: the article list API points at dummyjson.com by default, and the demo images are hot-linked from unsplash.com
Pinned to the delivered snapshot; it does not follow upstream.

The liability cap, the scope of what is promised and the statutory floor are governed by the Terms of Service.

Vetting record

Everything below was checked against the pinned commit fd9b358. Every verdict carries its full reasoning, an evidence link and the checker; failures are published, not hidden — do not take our word for it, verify it yourself.

3 PASS2 WARN0 FAIL

Source ReviewPASS

The 81 TS/TSX files under src/ and the files under server/ were scanned: no eval / new Function / child_process; the only dangerouslySetInnerHTML is in src/app/+html.tsx (expo-router's own template injecting the background colour CSS for the web build, its content a constant string defined in that same file, not external input); the only outbound connections at runtime are for the demo — the article list API points at the public test service dummyjson.com, and the demo images are hot-linked from unsplash.com.

Script SafetyWARN

package.json has two install-time scripts: preinstall npx only-allow pnpm (which blocks installing with anything but pnpm, and reaches the npm registry to fetch only-allow) and prepare husky (which installs git hooks). Both are development toolchain convention and not malicious, but they are the "runs on install" kind, so this is flagged as uncertain; our container build installs with --ignore-scripts and does not trigger them.

RecencyPASS

The derivative repository is pinned at a specific commit (see the evidence link) and does not follow upstream.

LicensePASS

SPDX:LicenseRef-99LL-Product

Upstream is MIT: the LICENSE itself at the pinned commit fd9b358ed11913d2a49fd9ffa6582fe03ba130e7 was read word for word (the standard MIT text, Copyright 2021 Obytes), and the root LICENSE is kept verbatim; our sale terms = LICENSE-99LL (99LL product licence template v1). Upstream's account identifiers (the Expo owner and the EAS project ID) have been removed.

Dependency LicensesWARN

The licence file of every package was not opened and checked word for word one by one (there are a lot of dependencies), so the licence status is flagged as uncertain — an honest marking of how deep the check went, not a pretence of having checked every file.