Member-only story
React Native — Application architecture with Design pattern — corporate standards
This story will cover all the aspects of a cross-platform react-native framework based app’s architecture. This can be used for creating a boilerplate for creating your next awesome cross-platform mobile app.
I’ve also written a story for Industry standard React-Native App setup.
(https://medium.com/@saurabhshah23/perfect-react-native-application-setup-industry-standards-bd3cc623745e)
NOTE: For versions of react and other libraries, please refer before and after screenshots of “package.json”.
If you are creating a new application then, the prerequisite will be to create a react-native app using react-native-cli. Please refer to “https://reactnative.dev/docs/environment-setup” for steps to create a basic react native app and run it on emulator/device.
Overview of app architecture features:
This app will support all the major features required for a corporate application. It includes redux + thunk for centralized state, i18n for internationalization or multilingual support, react-native-testing-library for unit testing and paper for Material design component library.
You can skip any of them if it is not required in your application. They all are loosely coupled.
Agenda of this document is to cover details of:
✓ all the dependencies used by a react-native application
✓ reasoning behind each dependency
✓ dependency configuration
✓ app integration steps for each dependency, if any.
The document is divided in below 3 sections:
Section-1 ARCHITECTURE
“package.json” is the definition of react-native projects. This is how it looks after setup is completed for a react-native app as of “12-jun-2020”:
