Skip to content

Initialize your backend provider

AppLaunchKit uses separate configuration mechanisms for different setups. Based upon your requirements, configure the apps accordingly.

Firebase Setup

To use Firebase as your provider, follow these steps:

  1. Create a new project in the Firebase console.
  2. Enable Firestore, Storage Buckets and authentication with email.
  3. Once you have created the project and enabled the required services, you will receive credentials. Place these credentials in your .env.development file, following the format specified for Firebase.
  • To setup the firebase for native, add the apps ios and android to the project in the firebase console.
  • You will then recieve the files google-services.json for android and GoogleService-Info.plist for ios which you need to place in the frontend/apps/expo directory.

Supabase Setup

To use Supabase as your provider, follow these steps:

  1. Start the local server from the backend directory by running the command npm run supabase:start.
  2. After starting the server, you will receive credentials. Place these credentials in your .env.development file, following the format specified for Supabase.

REST API Setup

To use a custom REST API as your provider, follow these steps:

  1. Start the local server from the backend directory by running the command npm run express:dev-docker.
  2. Once the server is running, you will receive credentials. Place these credentials in your .env.development file, following the format specified for REST API.

Adding Credentials to .env.development

After obtaining your credentials from the respective providers, add them to your .env.development file. Ensure that you follow the correct format for each provider to avoid any configuration issues.

Note that the .env.development files for Next and Expo are located in their respective folders:

  • For Next: frontend/apps/next/.env.development
  • For Expo: frontend/apps/expo/.env.development

Add your credentials to the corresponding file based on your application setup.

Example formats for each provider can be found in the respective documentation, but generally, you will need to add variables such as API keys, project IDs, or database URLs.

Remember to keep your credentials secure and do not commit them to your version control system.