reboottime
commented
7 months ago The Optimal Workflow for React Native App Development
There are three workflows
- Expo managed workflow
- Expo bare workflow
- and React Native CLI workflow
Each workflow has its pros, cons and application situation. Bellow is the decision making table you can take a look
- Workflow chosen decision making table
| Approach | Pros | Cons | When to Use |
|---|---|---|---|
| Managed Workflow | - Easy to set up and work with - Quick and frictionless development - Minimal configuration required - Convenient for adding third-party packages - Can build cross-platform standalone apps |
- Limited control over native code integration - Some restrictions on customization |
- Rapid prototyping and development - Projects with standard requirements - When using many Expo features and third-party packages - When native code integration is not needed |
| Bare Workflow | - More control over the project - Can integrate custom native code - Still relatively easy to set up and work with - Convenient development experience - Can build cross-platform standalone apps |
- Requires more configuration compared to Managed Workflow - May not work with Expo Go app when using custom native code |
- Projects requiring custom native code integration - When more control over the project is needed - When some Expo features are still desired |
| React Native CLI | - Full control over the project - Can integrate any native code and customize as needed |
- More complex setup required - More configuration effort for third-party packages and native device features - Building apps locally may be limited (e.g., no iOS builds on Windows) - No built-in support for cloud builds |
- Projects with highly custom requirements - When complete control over the project is necessary - When Expo features are not needed - When experienced with native development |
Overview
This article give u a look and feel from build a react native app to publish the app to iOS App store.
Major content