Expo SDK 56: React Native 0.85, stable Expo UI, faster builds
Expo has released SDK 56, which bundles React Native 0.85 and React 19.2. It is a large release covering UI, build performance, native module authoring, routing and tooling.
An update added to the announcement flags a known Hermes V1 memory regression in SDK 56 that can affect apps using react-native-worklets and react-native-reanimated. It is fixed in SDK 57, which Expo describes as equivalent to a minor release, and Expo recommends upgrading to SDK 57.
Expo UI is stable
The Jetpack Compose (Android) and SwiftUI (iOS) APIs in Expo UI are now stable. Expo UI is part of the default create-expo-app template and is available in Expo Go. New universal components such as Host, Row, Column, Text, TextInput, Button, Switch and BottomSheet work across Android, iOS and web, although the web side is still experimental. Other additions include:
- Custom SwiftUI and Compose views and modifiers
- A
useMaterialColorshook - A
useNativeStatehook WorkletCallbackfor synchronous, flicker-free controlled text inputs
SDK 56 also adds drop-in replacements for libraries such as @gorhom/bottom-sheet, @react-native-community/datetimepicker, react-native-pager-view and @react-native-community/slider. In most cases only the import changes, but some props differ.
Faster builds and runtime
- iOS builds: Prebuilt XCFrameworks for complex Expo modules cut median clean iOS build times by about one minute (~16%) in Expo's measurements. To opt out, set
EXPO_USE_PRECOMPILED_MODULESto0. - Android builds: An experimental
android.usePrecompiledHeadersoption inexpo-build-propertiesapplies CMake precompiled headers to codegen output. - Android runtime: A new Kotlin compiler plugin replaces reflection in Expo Modules. Expo's benchmarks show roughly 40% faster cold starts.
- iOS runtime: Native modules now use Swift/C++ interop to talk to JSI directly, removing the Objective-C++ layer.
Writing native modules
Inline modules let developers write Kotlin and Swift modules directly inside the project, and they are autolinked during prebuild. The new expo-type-information package can generate TypeScript interfaces from Swift modules, with a watch mode. create-expo-module has been revamped and gains an addPlatformSupport subcommand and Windows support.
React Native 0.85 highlights
- Hermes v1 is now the default engine; opt out with
useHermesV1. - A new animation backend.
- An HTTPS Metro dev server.
- A minimum of Node.js v20.19.4.
Expo Router forks React Navigation
expo-router no longer depends on react-navigation, so most direct @react-navigation/* imports will not work alongside it without migration. Expo provides a codemod for this. New experimental features include:
- An Android
Stack.Toolbar - Stack v5 with Material-style headers and predictive back
- Streaming SSR on web
createStaticLoader/createServerLoader
Other changes
- Updates: Hermes bytecode diffing is now on by default. Expo reports diffed bundles averaging 58% smaller.
- Stable libraries: The redesigned
expo-calendar,expo-contactsandexpo-media-libraryAPIs are now stable, and so are iOS Widgets. - AI tooling: New projects ship with
AGENTS.mdandCLAUDE.md. - Expo CLI: It defaults to an on-demand filesystem and a native Node.js watcher, and supports TypeScript 6.
Breaking changes and requirements
expo/fetchnow replacesglobalThis.fetch; opt out withEXPO_PUBLIC_USE_RN_FETCH=1.copy()andmove()inexpo-file-systemare now async.@expo/vector-iconsis deprecated in favor of@react-native-vector-icons/*.- Minimum versions are now Xcode 26.4 and iOS 16.4. TypeScript moves to 6.0.3.
Expo Go for SDK 56 is not on the app stores. It can be installed on Android via Expo CLI, and on iOS via TestFlight or eas go.
Links
Source: expo.dev