​

Adapter Configuration

​

Understanding Adapters

• Authentication - Mock or Firebase
• Subscriptions - Mock or RevenueCat
• Analytics - Mock or Firebase

• Develop without production services
• Switch providers easily
• Test with mock data
• Use different adapters per environment

​

Configuration Files

1. amisi.config.json - Adapter selection
2. packages/config/src/flags.ts - Feature flags to enable/disable services

​

Authentication Adapter

​

Available Adapters

• mock - Simulated authentication (development)
• firebase - Firebase Authentication (production)

​

Configure in amisi.config.json

{
  "auth": {
    "adapter": "firebase"
  }
}

​

Mock Adapter

{
  "auth": {
    "adapter": "mock"
  }
}

• No external dependencies
• Instant sign-in/sign-up
• Simulated user sessions
• Perfect for development

• No real authentication
• Data not persisted
• No password validation

​

Firebase Adapter

{
  "auth": {
    "adapter": "firebase"
  }
}

• Firebase project configured
• GoogleService-Info.plist (iOS)
• google-services.json (Android)
• Environment variables set

• Email/password authentication
• Social sign-in (Google, Apple, etc.)
• Password reset
• Email verification
• Multi-factor authentication

1. Follow Firebase Setup guide
2. Set environment variables
3. Enable authentication methods in Firebase Console
4. Rebuild native projects

​

Subscriptions Adapter

​

Available Adapters

• mock - Simulated subscriptions (development)
• revenuecat - RevenueCat (production)

​

Configure in amisi.config.json

{
  "subscriptions": {
    "adapter": "revenuecat"
  }
}

​

Mock Adapter

{
  "subscriptions": {
    "adapter": "mock"
  }
}

• No external dependencies
• Simulated products
• Instant purchases
• Simulated subscription status

• No real payments
• No App Store/Play Store integration
• Data not persisted

​

RevenueCat Adapter

{
  "subscriptions": {
    "adapter": "revenuecat"
  }
}

• RevenueCat account
• App configured in RevenueCat dashboard
• API keys set in environment variables
• Products configured in App Store Connect / Google Play Console

• Real subscription purchases
• Cross-platform subscription management
• Receipt validation
• Subscription analytics
• Webhooks for server-side events

1. Create RevenueCat account
2. Add your app to RevenueCat dashboard
3. Configure products in App Store Connect / Google Play Console
4. Link products in RevenueCat
5. Set environment variables:
   EXPO_PUBLIC_REVENUECAT_API_KEY=your-key
   
6. Rebuild native projects

• RevenueCat Getting Started
• Subscriptions Package

​

Analytics Adapter

​

Available Adapters

• mock - No-op analytics (development)
• firebase - Firebase Analytics + Crashlytics (production)

​

Configure with Feature Flags

const productionFlags: FeatureFlags = {
  enableAnalytics: true,
  enableCrashReporting: true,
  // ... other flags
};

const developmentFlags: FeatureFlags = {
  enableAnalytics: false, // Use mock adapter
  enableCrashReporting: false,
  // ... other flags
};

​

Mock Adapter

const developmentFlags: FeatureFlags = {
  enableAnalytics: false,
  enableCrashReporting: false,
};

• No external dependencies
• Silent (no-op)
• No network requests

• Developing locally
• Testing without analytics
• Running in Expo Go

​

Firebase Adapter

const productionFlags: FeatureFlags = {
  enableAnalytics: true,
  enableCrashReporting: true,
};

• Firebase project configured
• GoogleService-Info.plist (iOS)
• google-services.json (Android)
• Native build (not Expo Go)

• Firebase Analytics (GA4)
• Firebase Crashlytics
• Automatic screen tracking
• Custom event tracking
• User properties
• Crash reporting

1. Follow Firebase Setup guide
2. Enable feature flags
3. Rebuild native projects

• Analytics Package

​

Environment-Specific Configuration

​

Development

{
  "auth": {
    "adapter": "mock"
  },
  "subscriptions": {
    "adapter": "mock"
  }
}

const developmentFlags: FeatureFlags = {
  enableAnalytics: false,
  enableCrashReporting: false,
};

​

Preview

{
  "auth": {
    "adapter": "firebase"
  },
  "subscriptions": {
    "adapter": "revenuecat"
  }
}

const previewFlags: FeatureFlags = {
  enableAnalytics: true,
  enableCrashReporting: true,
};

​

Production

{
  "auth": {
    "adapter": "firebase"
  },
  "subscriptions": {
    "adapter": "revenuecat"
  }
}

const productionFlags: FeatureFlags = {
  enableAnalytics: true,
  enableCrashReporting: true,
};

​

Testing Adapter Changes

1. Update configuration files:
   • amisi.config.json
   • packages/config/src/flags.ts
2. Set environment variables (if using production adapters):
   • Firebase variables
   • RevenueCat variables
3. Rebuild native projects (if using Firebase or RevenueCat):
   bun run clear
   bun run prebuild
   
4. Restart development server:
   bun run start:clear
   
5. Test functionality:
   • Sign in/sign up (auth)
   • View products (subscriptions)
   • Navigate screens (analytics)

​

Adapter Initialization

​

Authentication

import { initializeAuth } from '@amisi/auth';

await initializeAuth({
  adapter: config.auth.adapter,
  options: {},
});

​

Subscriptions

import { initializeSubscriptions } from '@amisi/subscriptions';

await initializeSubscriptions({
  adapter: config.subscriptions.adapter,
  options: {
    apiKey: env.EXPO_PUBLIC_REVENUECAT_API_KEY,
  },
});

​

Analytics

import { initializeAnalytics } from '@amisi/analytics';

await initializeAnalytics({
  adapter: flags.enableAnalytics ? 'firebase' : 'mock',
  options: {
    enableAnalytics: flags.enableAnalytics,
    enableCrashReporting: flags.enableCrashReporting,
  },
});

​

Creating Custom Adapters

​

1. Implement the Adapter Interface

import { AuthAdapter } from '@amisi/auth';

export function createCustomAuthAdapter(): AuthAdapter {
  return {
    name: 'custom',

    async initialize(config) {
      // Initialize your service
    },

    async signIn(params) {
      // Implement sign in
      return null;
    },

    async signUp(params) {
      // Implement sign up
      return null;
    },

    async signOut() {
      // Implement sign out
    },

    async getSession() {
      // Get current session
      return null;
    },

    async cleanup() {
      // Cleanup resources
    },
  };
}

​

2. Register the Adapter

import { registerAuthAdapter } from '@amisi/auth';

registerAuthAdapter(createCustomAuthAdapter());

​

3. Use the Adapter

{
  "auth": {
    "adapter": "custom"
  }
}

​

Common Issues

​

Adapter Not Found

​

Initialization Failed

• Environment variables are set
• Config files are in place (Firebase)
• Native projects are rebuilt

​

Mock Adapter in Production

​

Best Practices

1. Use mock adapters for development - Faster iteration, no external dependencies
2. Test with production adapters before release - Catch integration issues early
3. Use environment-specific configuration - Different adapters per environment
4. Keep secrets secure - Use EAS Secrets for production API keys
5. Document adapter requirements - Make it clear what’s needed for each adapter

​

Next Steps

• Learn about Auth Package
• Learn about Subscriptions Package
• Learn about Analytics Package
• Configure Environment Variables