README.md

React Native Clean Architecture

A React Native scaffold with a clean architecture that is easy to understand.

Features

• 🚀 Expo 52
• 📁 Clean architecture. Layered file structure
• 🛡️ TypeScript bulletproof typing
• 🖌️ Code format: ESLint
• 🖌️ Commit format: CommitLint
• 🐩 Git hooks: Husky
• 💉 Dependency injection: Inversiland
• 🌍 I18n: expo-localization + i18n-js
• 🚢 Navigation: @react-navigation/native
• 🧰 State Manager: Mobx

---

📁 Project File Structure

⚠️ What makes the implementation of the clean architecture concept more difficult in my opinion is that since it is defined theoretically, each person implements it using different terminology or omitting/adding some layers or pieces to simplify it or continue to make it more complex.

For this reason, I think it is important to emphasize the documentation that accompanies the architecture to avoid obstacles with the rest of the people who are going to work with this system.

I briefly explain each of the four layers that make up clean architecture within the /src folder:

└── /src
    ├── AppModule.ts               # Dependency injection root module
    ├── /core                      # Core bounded context
    │   └── /presentation
    └── /post                      # Post bounded context
        ├── /domain
        ├── /application
        ├── /infrastructure
        └── /presentation

Domain

This layer contains all the enterprise business rules: entities, specifications...

Application

This layer contains the use cases of the bounded context.

Infrastructure

This layer contains the technical details (implementation) of the domain layer and third parties integrations.

Presentation

This layer contains the React Native source code: views and controllers (Redux Thunks).

References

• https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html
• https://jeffreypalermo.com/2008/07/the-onion-architecture-part-1/

---

Environment

Expo CLI loads .env files according to the standard .env file resolution and then replaces all references in your code to process.env.EXPO_PUBLIC_[VARNAME] with the corresponding value set in the .env files. Code inside node_modules is not affected for security purposes.

Development Environment

Create a .env file in the root of your project for development purposes:

EXPO_PUBLIC_API_URL=https://jsonplaceholder.typicode.com

Production Environment

Configure the .env.production file with the environment variables you want to use in production.

Run

Dev

yarn dev

Web

yarn web

Android

yarn android

iOS

yarn ios

---

Eject from Expo

expo eject

---

Support the project

☕️ Buy me a coffee so the open source party will never end.

YouTube | Instagram | Twitter | Facebook

godofprogramming.com