Native modules concept in React Native - Build, Publish & Deploy

Build & Publish - Native modules concept

Performance Impact

Using native modules in React Native lets your app run heavy tasks directly on the device's native code (Java/Kotlin for Android, Swift/Objective-C for iOS). This improves speed and responsiveness because native code runs faster than JavaScript for certain operations.

However, calling native modules too often or passing large data between JavaScript and native code can slow down your app and cause frame drops below 60fps, making animations and interactions feel laggy.

Memory usage can increase if native modules hold onto resources without releasing them properly, which may lead to app crashes on low-memory devices.

💻

How to Optimize for 60fps

• Minimize the number of calls between JavaScript and native code. Batch data or events when possible.
• Use asynchronous native methods to avoid blocking the JavaScript thread.
• Release native resources promptly to avoid memory leaks.
• Profile your app using React Native's performance tools and native profilers (Android Studio Profiler, Xcode Instruments).
• Keep native module code efficient and avoid heavy computations on the main UI thread.

Impact on App Bundle Size and Startup Time

Adding native modules increases your app's binary size because you include extra native code and libraries. This can add a few megabytes depending on the module complexity.

Startup time may increase slightly if native modules initialize during app launch. Lazy loading native modules when needed can reduce this impact.

Keep native modules focused and avoid including unused native dependencies to keep your app size small and startup fast.

iOS vs Android Differences

• iOS: Native modules are written in Swift or Objective-C and integrated via the React Native bridge. iOS requires careful memory management and uses ARC (Automatic Reference Counting).
• Android: Native modules use Java or Kotlin. Android apps use the JNI bridge. Android devices vary widely in performance and memory, so testing on multiple devices is important.
• Debugging native modules differs: Xcode is used for iOS, Android Studio for Android.
• Permissions and lifecycle events may differ, so native modules must handle platform-specific behaviors.

Store Review Guidelines and Requirements

• Apple App Store: Native modules must comply with Apple's Human Interface Guidelines and privacy rules. Avoid private APIs and ensure proper permission usage.
• Google Play Store: Native modules must follow Google Play policies, including proper use of permissions and no background abuse.
• Both stores require apps to be signed with valid certificates for native code.
• Ensure native modules do not cause crashes or excessive battery drain, as this can lead to app rejection.

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

It is likely that native modules are initializing heavy tasks on the main thread during startup, blocking UI rendering. Another cause could be frequent synchronous calls between JavaScript and native code delaying the UI thread.

Check if native modules are loading unnecessary resources at launch or if there are memory leaks causing slowdowns.

Optimizing native module initialization and using asynchronous calls can help reduce load time and improve responsiveness.

Key Result

Native modules speed up React Native apps by running code natively, but require careful optimization to maintain 60fps, manage memory, and keep app size small. Platform differences and store rules must be followed for smooth publishing.