Project structure overview in React Native - Build, Publish & Deploy

Build & Publish - Project structure overview

Performance Impact

A clear project structure helps maintain smooth app performance by making code easier to manage and optimize. Well-organized files reduce bugs that can cause slow rendering or crashes. Proper separation of UI, logic, and assets ensures faster load times and better memory use, helping maintain 60fps frame rates for smooth animations.

Optimization Tips

Keep components small and focused in separate folders. Use lazy loading for screens and heavy assets to avoid blocking the main thread. Organize reusable components and utilities to prevent code duplication, which can bloat the app and slow down builds. Use clear naming conventions to speed up debugging and updates.

App Size and Startup Time

A tidy project structure helps control app size by making it easier to spot unused code and assets. Grouping images and fonts in dedicated folders allows for better compression and caching strategies. Avoid large monolithic files; split code into smaller chunks to improve startup time and reduce initial bundle size.

iOS vs Android Differences

React Native projects share most code, but native folders differ: iOS uses an Xcode project with Swift/Obj-C files, Android uses Gradle with Kotlin/Java files. Organize platform-specific code in separate folders (e.g., ios/ and android/) to keep the shared JavaScript clean. Be mindful of platform-specific assets and configurations.

Store Review Guidelines

Both Apple App Store and Google Play require apps to be stable and performant. A well-structured project reduces bugs and crashes, helping pass reviews. Follow guidelines for app size limits (Apple prefers under 200MB for over-the-air downloads). Keep sensitive info out of code and use environment files properly. Ensure accessibility and privacy compliance.

Self-Check Question

Your app takes 5 seconds to load this screen. What's likely wrong?

• Code is not split properly, causing large bundles to load at once.
• Heavy assets or components are loaded upfront instead of lazily.
• Project structure is messy, making it hard to optimize or debug slow parts.

Key Result

A clear and organized React Native project structure improves app performance, reduces bundle size, and eases platform-specific management, helping your app run smoothly and pass store reviews.

Practice

1. In a typical React Native project, where should you place your main app code for better organization?

easy

A. Inside the android folder

B. Directly in the root folder

C. Inside a folder named src

D. Inside the ios folder

Solution

1. Step 1: Understand folder roles

   The android and ios folders contain platform-specific native code, not app logic.

2. Step 2: Identify app code location

   App code is best organized inside a src folder to keep it separate and clear.

3. Final Answer:

   Inside a folder named src -> Option C

4. Quick Check:

   App code = src folder [OK]

Hint: App code goes in src folder, not platform folders [OK]

Common Mistakes:

• Putting app code inside android or ios folders
• Keeping all code in the root folder without organization

2. Which of the following is the correct folder name for platform-specific Android code in a React Native project?

easy

A. android

B. android_src

C. AndroidCode

D. androidApp

Solution

1. Step 1: Recall standard folder names

   React Native uses android as the folder name for Android platform code by default.

2. Step 2: Compare options

   Only android matches the exact folder name used by React Native.

3. Final Answer:

   android -> Option A

4. Quick Check:

   Android folder = android [OK]

Hint: Platform folders are named exactly android and ios [OK]

Common Mistakes:

• Using camelCase or underscores in platform folder names
• Confusing app code folder with platform folders

3. Given this React Native project structure:

myApp/
├── android/
├── ios/
├── src/
│   └── App.js
└── package.json

Where will the main app component be located?

medium

A. Directly in the root folder

B. Inside ios folder

C. Inside android folder

D. Inside src folder

Solution

1. Step 1: Analyze folder contents

   The src folder contains App.js, which is the main app component file.

2. Step 2: Understand platform folders

   The android and ios folders hold native code, not React Native components.

3. Final Answer:

   Inside src folder -> Option D

4. Quick Check:

   Main app component = src/App.js [OK]

Hint: Main app code lives in src, not platform folders [OK]

Common Mistakes:

• Assuming main app code is inside android or ios
• Looking for app code in the root folder

4. You see this error when running your React Native app: "Cannot find module './App'". Your project structure is:

myApp/
├── android/
├── ios/
├── app/
│   └── App.js
└── package.json

What is the likely cause?

medium

A. The package.json file is corrupted

B. The app code is inside app folder but should be in src

C. The android folder is missing App.js

D. The ios folder is empty

Solution

1. Step 1: Identify folder mismatch

   The app code is in app folder, but React Native expects it in src or root by default.

2. Step 2: Understand module resolution

   Since the code is not where expected, the bundler cannot find ./App module.

3. Final Answer:

   App code is inside app folder but should be in src -> Option B

4. Quick Check:

   App folder mismatch = module not found error [OK]

Hint: App code folder must match import paths exactly [OK]

Common Mistakes:

• Ignoring folder naming conventions
• Assuming platform folders hold app code
• Not checking import paths

5. You want to add a new feature to your React Native app. Which project structure change helps keep your code organized and maintainable?

hard

A. Create a new folder inside src for the feature components

B. Add all new files directly to the root folder

C. Put new feature files inside the android folder

D. Mix new feature files with existing files in ios folder

Solution

1. Step 1: Understand best practices for organization

   Keeping feature code inside src in dedicated folders helps maintain clarity and separation.

2. Step 2: Avoid mixing platform and app code

   Platform folders android and ios are for native code, not React Native components.

3. Final Answer:

   Create a new folder inside src for the feature components -> Option A

4. Quick Check:

   Organize features inside src for maintainability [OK]

Hint: Keep features inside src in separate folders [OK]

Common Mistakes:

• Adding app code to platform folders
• Cluttering root folder with many files
• Not grouping related files