Skip to main content

Tooling Checklist

Use this page as the short operational checklist for a serious React Native project.

Core stack​

  • React Native workflow chosen intentionally.
  • TypeScript configured and enforced in CI.
  • ESLint and formatter configured repository-wide.
  • Shared design tokens and UI primitives defined.
  • One navigation system documented.
  • Server-state strategy documented.

Delivery stack​

  • Reproducible local setup instructions.
  • CI pipeline for typecheck, lint, tests, and native builds.
  • Release credential ownership documented.
  • Crash and performance telemetry connected to release versions.
  • Staged rollout and rollback rules documented.

Quality stack​

  • Unit tests for domain logic.
  • Component tests for critical screens.
  • End-to-end tests for highest-value journeys.
  • Accessibility checks built into component review.
  • Performance budgets for startup and key flows.

Native capability stack​

  • Capability wrappers owned by the app.
  • Permission rationale and denial flows documented.
  • Sensitive data stored securely.
  • Platform-specific behavior documented explicitly.

Maintenance stack​

  • Dependency review cadence defined.
  • React Native upgrade cadence defined.
  • Incident response owner identified.
  • Production checklist updated after each release issue.

Canonical repository scripts​

Every project should have obvious commands for:

npm run start
npm run ios
npm run android
npm run lint
npm run test
npm run typecheck
npm run build

Not every workflow will use the exact same command names, but the purpose of each command should be universal across the team.

Exit criteria​

The project is well-instrumented when a new engineer can answer these questions quickly:

  • How do I run the app?
  • How do I add a screen?
  • How do I fetch data?
  • How do I integrate a native capability?
  • How do I test and release safely?

If the answers are obvious from the repository and this site, the documentation system is doing its job.