Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mobile-starter.amisi.ai/llms.txt

Use this file to discover all available pages before exploring further.

AMiSi Mobile Starter uses a layered configuration approach to manage app settings, branding, and environment-specific values.

​
Configuration Layers

The starter uses three main configuration layers:

​
1. App Configuration (app.json)

Located at apps/mobile/app.json, this is the primary Expo configuration file that defines:
  • App name and slug
  • Bundle identifiers (iOS/Android)
  • Icons and splash screens
  • Expo plugins
  • Platform-specific settings
  • EAS project ID
When to edit: When changing app identity, adding Expo plugins, or modifying platform-specific settings.

​
2. Product Configuration (amisi.config.json)

Located at the repository root, this file manages:
  • App identity (name, scheme, bundle IDs)
  • Branding assets (icon paths, splash screen)
  • Adapter selection (auth, subscriptions)
When to edit: When customizing the app for a specific customer or changing service adapters.

​
3. Environment Variables (.env)

Environment variables control runtime behavior:
  • API endpoints
  • Service API keys (Firebase, RevenueCat)
  • Feature flags
  • Debug settings
When to edit: When setting up different environments (development, preview, production) or configuring third-party services.

​
Quick Reference

What to ConfigureWhereGuide
App name, bundle IDsamisi.config.jsonApp Identity
Icons, splash screensamisi.config.json + assetsBranding
Build profilesapps/mobile/eas.jsonEAS Setup
Firebase servicesFirebase Console + config filesFirebase Setup
API keys, secrets.env + EAS SecretsEnvironment Variables
Service adaptersamisi.config.json + flagsAdapters

​
Configuration Workflow

  1. Customize app identity - Set your app name, bundle IDs, and scheme
  2. Update branding - Replace icons and splash screens with your assets
  3. Set up EAS - Initialize EAS and configure build profiles
  4. Configure services - Set up Firebase, RevenueCat, or other services
  5. Set environment variables - Configure API keys and environment-specific values
  6. Select adapters - Choose which service adapters to use (mock vs production)

​
Using the Configurator

The starter includes a web-based Configurator UI that provides a visual interface for managing configuration: 
bun run configurator:dev
The Configurator allows you to:
  • Edit app.json and amisi.config.json visually
  • Upload and manage branding assets
  • Preview changes before applying them
  • Generate environment variable templates
See individual configuration guides for detailed instructions.

​
Next Steps