Folder Structure of a React Native App

Introduction

React Native is a powerful framework for building mobile applications using JavaScript and React. As you dive into developing with React Native, it’s essential to understand the structure of a typical React Native project. Each folder and file has a specific purpose, and knowing their roles will help you manage and navigate your project more efficiently. This article provides a comprehensive overview of the folder structure of a React Native app, focusing on the contents and purposes of the main directories: the root directory, the android/ folder, and the ios/ folder.

Root Directory

The root directory of a React Native project contains essential files and folders that manage the project’s dependencies, configuration, and entry point.

Key Files and Folders

  • node_modules/: Contains all the dependencies and sub-dependencies installed via npm or yarn. Typically, you won’t need to touch this folder directly.
  • package.json: Lists your project dependencies, scripts, and other metadata. It’s crucial for managing project dependencies and scripts.
  • package-lock.json or yarn.lock: Locks the versions of dependencies installed, ensuring consistency across different environments.
  • index.js: The entry point for your React Native app, usually registering the main component of the app.

Core Folders

  • android/: Contains the native Android code and configuration files, necessary if you need to write or modify native Android code.
  • ios/: Contains the native iOS code and configuration files, essential for writing or modifying native iOS code.
  • app/ or src/: Often the main folder for your JavaScript/TypeScript code, such as components, screens, and services. This is where most of your app’s code resides.

Common Subfolders (inside app/ or src/)

  • components/: Reusable UI components, helping to organize and reuse UI elements across different parts of the app.
  • screens/: Components representing different screens or views, making it easier to manage navigation and individual screens.
  • navigations/: Navigation configuration and components, used to define the app’s navigation structure.
  • assets/: Images, fonts, and other static assets, keeping all static resources organized.
  • redux/ (if using Redux for state management): Actions, reducers, and store configuration for managing the global state of the application.
  • styles/: Common styles used across components and screens, helping maintain a consistent design and simplifying style management.

Configuration and Utility Files

  • .babelrc or babel.config.js: Babel configuration file, defining how Babel transpiles your code.
  • .eslintrc.js: ESLint configuration file, setting up linting rules for your project.
  • .prettierrc: Prettier configuration file, configuring code formatting rules.
  • metro.config.js: Configuration file for the Metro bundler, the JavaScript bundler used by React Native.
  • .gitignore: Specifies which files and directories to ignore in your git repository.

The android/ Folder

The android/ folder contains all the native Android code and configuration files necessary to build and run your React Native app on an Android device or emulator.

Key Files and Folders

  • build.gradle: The top-level build file where you can add configuration options common to all sub-projects/modules.
  • gradle.properties: Configuration properties for the Gradle build system.
  • gradlew and gradlew.bat: Scripts to run Gradle commands on Unix-based and Windows systems, respectively.
  • settings.gradle: Specifies the project’s modules, including any external libraries or additional modules your project might depend on.

Subfolders

app/

  • build.gradle: The build file for the app module, containing configurations and dependencies specific to your app.
  • src/: Contains the source code for the Android part of your app.

    • main/:
    • AndroidManifest.xml: Describes essential information about your app to the Android build tools, the Android operating system, and Google Play.
    • java/: Contains Java or Kotlin source files, including MainActivity.java or MainActivity.kt, the entry point of the app.
    • res/: Contains app resources such as layouts, drawable files (images), strings, and other XML files used by the app.
    • assets/: Stores raw asset files needed by your app, such as fonts or other binary files.
    • jniLibs/: Contains precompiled native libraries (.so files) that your app depends on.

gradle/

  • wrapper/: Contains files to help with the Gradle build system.

    • gradle-wrapper.jar: A JAR file for the Gradle wrapper, allowing you to build your project without requiring users to install Gradle.
    • gradle-wrapper.properties: Specifies the version of Gradle to be used and other properties.

The ios/ Folder

The ios/ folder contains all the native iOS code and configuration files necessary to build and run your React Native app on an iOS device or simulator.

Key Files and Folders

  • Podfile: Specifies dependencies for the iOS part of your React Native app, managed by CocoaPods.
  • Podfile.lock: Locks the versions of the dependencies specified in the Podfile, ensuring consistency across different environments.
  • <ProjectName>.xcworkspace: A workspace file generated by CocoaPods that you use to open your project in Xcode.
  • <ProjectName>.xcodeproj: The Xcode project file containing your app’s project settings and information.

Subfolders

<ProjectName>/

  • AppDelegate.m or AppDelegate.swift: Manages application-level events and states, the entry point for the iOS app.
  • Info.plist: Contains configuration information for the app, such as bundle identifier, app name, permissions, and other settings.
  • Assets.xcassets/: Contains the app’s image and icon assets.
  • Base.lproj/: Contains the main storyboard or launch screen file (LaunchScreen.storyboard).
  • main.m or main.swift: The main entry point for the app, setting up the application object and the application delegate.
  • Supporting Files/: Contains additional resources and configurations, such as entitlements and bridging headers (if using Swift).

Conclusion

Understanding the folder structure of a React Native app is crucial for efficient project management and development. Each folder and file has a specific role, from managing dependencies and configurations to containing the code and resources for both Android and iOS platforms.


Discover more from Coursity

Subscribe to get the latest posts sent to your email.

Leave a Comment

Your email address will not be published. Required fields are marked *

Discover more from Coursity

Subscribe now to keep reading and get access to the full archive.

Continue reading

Scroll to Top
Jamb 2025 march 15 question and answers /march 15 jamb 2025 expo question.