Home / Companies / Expo / Blog / Post Details
Content Deep Dive

Out with the old, in with the New Architecture (by default)

Blog post from Expo

Post Details
Company
Date Published
Author
Brent Vatne
Word Count
686
Company Posts That Month
10
Language
English
Hacker News Points
-
Post removed?
No
Summary

In SDK 53, the New Architecture will be automatically enabled for all projects, aligning with React Native's default settings, although users can opt-out if desired. This marks a continuation from SDK 52, where it was introduced for new projects, and as of April 2025, 74.6% of projects have adopted it. The New Architecture supports new React and React Native features, such as Suspense and advanced styling, which are not available in the legacy system. While most transitions are expected to be straightforward, larger apps with outdated dependencies may require more effort. The legacy architecture may be phased out by late 2025, compelling a shift to the New Architecture for continued upgrades. Libraries such as react-native-reanimated and @shopify/flash-list will exclusively support the New Architecture in future versions, enhancing performance. Despite previous issues during migration, many have been resolved, though some libraries like @stripe/react-native still lack full support. Developers encountering migration obstacles are encouraged to report them on GitHub with reproducible examples, and temporarily disable problematic features while exploring other potential issues. The transition signifies a move towards universal adoption, with the legacy architecture potentially becoming a distant memory.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.