React Native 0.81: Key Updates for Android 16, iOS Builds, and Deprecations
Welcome to the latest release of React Native! Version 0.81 brings essential updates, including full support for Android 16 (API level 36), notable deprecations, and experimental improvements for iOS development. This version is packed with stability fixes and features to help you build modern, edge-to-edge apps. Below we answer the most common questions about this release.
What does React Native 0.81 mean for Android 16 compatibility?
Starting with this release, apps built with React Native will automatically target Android 16 (API 36). This means your app must embrace edge-to-edge rendering, as Google no longer allows opting out. To assist with this transition, React Native introduces a new Gradle property called edgeToEdgeEnabled, which lets you control edge-to-edge behavior on Android versions below 16. For Android 16 itself, the display is always edge-to-edge. This change also deprecates the built-in SafeAreaView component because it doesn't work well with edge-to-edge layouts. Additionally, the predictive back gesture is now enabled by default, so test your app's back navigation—especially if you use custom native code like overriding onBackPressed(). You can temporarily opt out if needed.
Why is SafeAreaView deprecated and what should I use instead?
The original SafeAreaView component was designed only for iOS and provided basic padding to avoid notches and rounded corners. It was never intended for Android’s edge-to-edge world and offers no customization beyond simple padding. In React Native 0.81, SafeAreaView is officially deprecated, and you'll see warnings in DevTools if your app still uses it. For future releases, the component will be removed entirely. The recommended alternative is the react-native-safe-area-context library, which works seamlessly across both platforms and supports custom insets, making it ideal for edge-to-edge designs. Migrating to this library ensures your app looks great on all devices.
How do the new iOS build improvements work?
React Native 0.81 includes an experimental feature that speeds up iOS builds through precompilation. By precompiled iOS builds, we mean that the build system can cache and reuse compiled code, reducing the need to recompile everything from scratch on each run. This is especially beneficial for larger projects where build times can become a bottleneck. While still experimental, this feature shows promise for significantly trimming development cycles. Developers can opt into it and help shape its stability by providing feedback. Over time, this could make React Native development on iOS much more efficient.
What is community-maintained JavaScriptCore support?
In line with earlier announcements, React Native 0.81 now ships with a community-maintained version of JavaScriptCore (JSC) as the default JavaScript engine for some platforms. Previously, maintaining JSC was done internally by Meta, but now the community takes the lead, allowing for more frequent updates and better alignment with modern JavaScript features. This change doesn't affect most developers directly—it's mostly about long-term maintenance and performance. The new JSC is provided as an npm package, making it easier to update separately from the core framework. It ensures continued support for platforms like Android where JSC is used, while also paving the way for future engine choices like Hermes.
What do I need to know about the 16 KB page size requirement for Google Play?
Starting November 1, 2025, all new apps and updates on Google Play must comply with a 16 KB page size for native binaries. React Native itself is already compliant with this requirement, but you should verify that any native code or third-party libraries you use also meet the standard. The same rule applies to apps targeting Android 15 and above. Failing to comply can lead to rejection during submission. To check your app, you can use tools like readelf to examine binary alignment. This change is part of Google’s push for better memory and storage efficiency on Android.
How does the predictive back gesture affect React Native apps on Android 16?
With Android 16, the predictive back gesture is enabled by default for apps targeting this API level. This means when users swipe from the left edge of the screen, they’ll see a preview of where they’re going. The BackHandler API in React Native should continue to work for most common use cases. However, if your app uses custom native code that overrides onBackPressed(), you may need to migrate to the newer OnBackInvokedCallback API or temporarily opt out using the AndroidManifest.xml flag. Thorough testing is essential, especially for apps with complex navigation or modal screens. The early preview helps users avoid accidental back navigation.
What about adaptive layouts for large screens?
Google now expects apps on Android 16+ to support adaptive layouts on large-screen devices, such as tablets and foldables. This means your UI should respond gracefully to different screen sizes and orientations. While it’s possible to opt out for now, this requirement will become stricter with Android 17. React Native’s flexible component model makes it easier to implement responsive designs using tools like Dimensions or libraries such as react-native-responsive-dimensions. Start testing your app on larger screens today to ensure a consistent user experience. Future versions of React Native may include built-in helpers for adaptive layouts.