Welcome to the latest release of React Native! Version 0.81 brings important enhancements, including official support for Android 16 (API level 36), experimental faster iOS builds through precompilation, and the deprecation of the built-in SafeAreaView component. This update also introduces a community-maintained JavaScriptCore option and several stability fixes. Below we answer your top questions about what this means for your projects.
What are the major highlights of React Native 0.81?
React Native 0.81 focuses on four key areas:
- Android 16 support – Apps now default to targeting API level 36, with mandatory edge-to-edge display and predictive back gestures enabled.
- SafeAreaView deprecation – The legacy iOS-only component is deprecated; migrate to
react-native-safe-area-contextfor cross-platform safe areas. - Community-maintained JavaScriptCore – JSC support is now maintained by the community, ensuring future compatibility and updates.
- Experimental precompiled iOS builds – Faster builds on iOS by precompiling certain native modules, reducing incremental build times.
These changes improve performance, Android readiness, and developer experience. See the sections below for detailed guidance.
How does Android 16 support affect existing React Native apps?
With Android 16 (API level 36), Google mandates that apps render edge-to-edge with no opt-out. React Native 0.81 updates the default target SDK to 36, so your app will automatically adopt this behavior. To help you manage the transition, a new Gradle property edgeToEdgeEnabled lets you toggle edge-to-edge on devices running Android versions below 16. Additionally, predictive back gestures are enabled by default; the BackHandler API should work as usual, but if you override onBackPressed() in native code, you may need to migrate or temporarily opt out. Google also expects adaptive layouts for large screens starting with Android 16, though you can opt out for now. Finally, all native binaries must comply with the 16 KB page size requirement by November 1, 2025; React Native is already compliant, but verify your third-party libraries.
Why is SafeAreaView deprecated and what should I use instead?
The SafeAreaView component was originally iOS‑only and limited to simple padding. It does not support Android’s edge-to-edge requirements and offers no customization. In React Native 0.81, it is officially deprecated and will be removed in a future version. You will see warnings in DevTools if you still use it. The recommended replacement is react-native-safe-area-context (or similar libraries). This community package works on both iOS and Android, provides hooks and components for safe area insets, and integrates smoothly with edge-to-edge rendering. Migrating now will ensure your app looks its best on all devices, especially with Android 16’s mandatory edge-to-edge mode.
What is community-maintained JavaScriptCore support?
As announced earlier, JavaScriptCore (JSC) for React Native is now maintained by the open-source community. Previously, Meta directly managed JSC integration, but the community has taken over to keep it up‑to‑date and compatible with newer Android versions. This change does not affect the default JavaScript engine (Hermes is still recommended) but ensures that developers who rely on JSC continue to receive updates and fixes. In React Native 0.81, the JSC support remains available and works as before, but it is now labeled as community‑maintained. If you use JSC, you should monitor its repository for future releases and potential deprecation notices.
How do experimental precompiled iOS builds work?
Experimental precompiled iOS builds aim to speed up development cycles by precompiling certain native modules. Instead of recompiling all native code on every change, React Native 0.81 stores precompiled artifacts for frameworks like Yoga and Folly. When you rebuild, only the changed parts are recompiled, reducing incremental build times significantly. This feature is opt‑in and still experimental, so you enable it via a new configuration flag. Early tests show a noticeable improvement, especially for large projects. Be aware that some edge cases may require clearing caches. To try it, follow the documentation in the React Native repository; feedback is welcomed to help stabilize the feature for future releases.
What is the edgeToEdgeEnabled Gradle property for?
The new edgeToEdgeEnabled Gradle property gives you control over edge-to-edge rendering on Android versions that support it but are below API 36. When set to true, your app will render edge-to-edge on Android 15 and earlier, matching the behavior mandated by Android 16. This is useful for testing and gradual migration. If you set it to false, your app will keep the previous behavior on older versions, but remember that Android 16 will override this setting. The property is defined in android/gradle.properties and can be toggled per build variant. We recommend enabling it early to test your UI with system bars and notches, then adjust your layout using react-native-safe-area-context.
When will SafeAreaView be removed, and how do I migrate?
A specific removal date has not been announced, but React Native 0.81 marks the deprecation. The component will likely be removed in a future major version (e.g., 0.82 or 1.0). To migrate:
- Install
react-native-safe-area-contextfrom npm. - Replace
<SafeAreaView>with<SafeAreaProvider>and<SafeAreaView>from the library. - Use the
useSafeAreaInsetshook for custom insets. - Test your app on both iOS and Android, especially on devices with notches or under edge-to-edge mode.
The library is well-documented and actively maintained. After migration, you can remove all legacy SafeAreaView imports to clear deprecation warnings and future-proof your codebase.