<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>New Architecture on Codemagic blog</title><link>https://blog.codemagic.io/tags/new-architecture/</link><description>Recent content in New Architecture on Codemagic blog</description><generator>Hugo</generator><language>en</language><copyright>©Nevercode Ltd | All Rights Reserved | Codemagic is pending trademark of Nevercode Ltd.</copyright><lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0300</lastBuildDate><atom:link href="https://blog.codemagic.io/tags/new-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>React Native New Architecture and OTA Updates: What Teams Need to Know in 2026</title><link>https://blog.codemagic.io/react-native-new-architecture-ota-updates/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0300</pubDate><guid>https://blog.codemagic.io/react-native-new-architecture-ota-updates/</guid><description>&lt;blockquote>
&lt;p>This article is written by &lt;strong>Karl Suhajda&lt;/strong>&lt;/p>
&lt;/blockquote>
&lt;p>The React Native New Architecture is no longer optional. From React Native 0.82 onwards it is mandatory, the legacy architecture is gone, and every team still running it is now carrying technical debt that will need to be resolved.&lt;/p>
&lt;p>For most teams, the migration conversation quickly turns to tooling. Does our CI/CD pipeline still work? Does our crash reporter still integrate correctly? Do our analytics tools need updating? And for teams relying on over-the-air updates (OTA), does OTA delivery still work the same way after the migration?&lt;/p></description></item></channel></rss>