Manage Dynamic Environments in React Native: Simplifying Build Generation Process

Managing dynamic environments in a React Native application is essential for optimizing the build generation process and ensuring smooth deployment across various regions. This talk delves into the best practices and tools to handle this effectively, particularly focusing on environment variables and automation.

Environment variables are crucial for storing global values, such as API endpoints, that need to be accessed throughout the app. However, it is essential to avoid storing sensitive information in these variables as they can be easily decoded from the source code. Careful consideration must be given to what is stored in these environment files.

In React Native, tools like react-native-config are used to handle environment variables. For web applications, .env files are commonly utilized. These tools enable the storage and retrieval of environment-specific variables, facilitating smoother builds and deployments.

Our current project is a React Native application that supports multiple regions. From a single codebase, we generate two distinct apps, each catering to different regions. This results in four separate builds: two for Android and two for iOS. Managing these builds manually is time-consuming and prone to errors, making automation a necessity.

Benefits of App Center

1. Reduction in Build Generation Time: Automating builds eliminates the need for manual intervention, speeding up the process.
2. Consistency and Reliability: Automated builds reduce the potential for human errors, ensuring consistent and reliable outputs.
3. Enhanced Security: Centralized management of environment variables enhances security by minimizing exposure to sensitive information.
4. Scalability and Flexibility: The ability to manage multiple branches and environment variables allows for easy scalability and flexibility.
5. Speedy Delivery of Testing Builds: Quick and efficient delivery of testing builds to QA teams ensures timely feedback and iterations.

A significant challenge in our project was synchronizing backend and mobile deployments. Since the app review process by Google and Apple takes time, the app needs to be fully functional during this period. We tackled this by dynamically managing environment variables using AWS Secrets Manager.

By storing dynamic environment variables, such as API endpoints, in AWS Secrets Manager, we ensure that the app can seamlessly switch between QA and production environments without the need for additional builds. This approach allows the backend to be deployed first, followed by the frontend, ensuring that both are in sync and the app remains functional during the review process.

1. Merge Backend Changes to QA Branch: This ensures stability and prepares the backend for deployment.
2. Create Mobile Build from Main Branch: The frontend code is prepared for production.
3. Submit Build for Review: The app is submitted for review with the backend still pointing to the QA environment.
4. Merge Backend Changes to Main: Once the build is approved, the backend is deployed to production.
5. Dynamic Environment Handling: Using AWS Secrets Manager, the app fetches production environment variables without requiring a new build.