Skip to main content
AMiSi Mobile Starter gives you the production foundations for an Expo Router app in an Nx and Bun workspace. Start with authentication, app locking, onboarding, subscriptions, analytics, notifications, theming, reusable UI, a local Configurator, and portable AI guidance already structured for you.

Start with the Quickstart

Install the workspace, configure your environment, and run the mobile app.

Explore the architecture

Understand the app, package, adapter, and tooling boundaries before you build.
Follow the Quickstart before changing native or service configuration.

​
What ships

Expo mobile app

Native iOS and Android flows for sign-in, email verification, PIN and biometric setup, onboarding, tabs, modals, and app unlock.

Adapter-based services

Firebase auth and analytics, RevenueCat subscriptions, OneSignal or Expo notifications, and mock adapters for supported domains.

Shared packages

Eleven shipped packages for analytics, auth, chat, config, core utilities, translations, notifications, security, subscriptions, theme, and UI.

Local Configurator

Edit Expo app settings and selected product configuration with diff previews and atomic apply operations.

Nx generators

Local feature, adapter, and screen generators for repeatable workspace scaffolding.

Portable AI guidance

Tool-neutral agents, skills, workflows, task templates, and the shared verification gate.

​
Core stack

  • Expo 56, React Native 0.85, React 19, and Expo Router
  • Nx 22 with Bun 1.3 workspaces
  • TypeScript, Zod, Jest, and Biome
  • Gluestack UI with shared @amisi-mobile-starter/ui and @amisi-mobile-starter/theme packages
  • Uniwind and NativeWind-compatible styling configuration
  • Firebase, RevenueCat, OneSignal, and Expo native integrations

​
Understand the boundaries

  • Route files live under apps/mobile/app.
  • App composition and access gating live in the mobile app.
  • Reusable domain and platform behavior lives in the packages that are present under packages/.
  • Environment access is centralized in @amisi-mobile-starter/config.
  • Provider-specific SDK usage stays inside adapter modules.
Read Architecture overview before adding a route, service, or package.

​
Start here

1

Run the app

Install dependencies, pull development environment values, and create a native development build with the Quickstart.
2

Configure the product

Review the configuration layers, then update app identity, branding, service adapters, and EAS environments.
3

Learn the runtime flow

Read Navigation and access control and Onboarding flow.
4

Use public package APIs

Browse the package reference and component reference before importing internal files.

​
Production note

The starter includes production-oriented building blocks, but you must replace project identifiers, native service files, API keys, app-store credentials, legal content, and product-specific screens before release. Run the repository verification and Mintlify validation workflows after every customization.