<\/span><\/h2>\nFor years, debugging has been a point of friction for React Native developers, often requiring a complex dance between the Flipper desktop application, Chrome DevTools, and various proxy settings. In version 0.73, the React Native and Hermes teams have prioritized internalizing and simplifying this workflow.<\/p>\n
One of the most immediate improvements is the introduction of Console Log History in Hermes. Historically, logs generated during the early stages of an app\u2019s lifecycle\u2014such as during initialization or the initial render\u2014were lost if a debugger was not already connected. Under the new system, Hermes captures all console.log()<\/code> calls in the background. When a developer connects a debugger, these stored logs are instantly transmitted to the Console tab. This behavior aligns React Native with the standard debugging experience found in modern web browsers, ensuring that critical boot-up errors or data states are never missed.<\/p>\nFurthermore, the release introduces a Technical Preview of a new, experimental JavaScript debugger. Designed to eventually replace Flipper as the default tool, this new debugger is built to open instantly and features a streamlined Chrome DevTools interface customized specifically for Hermes. This move signals a shift away from heavy, plugin-based debugging environments toward lightweight, purpose-built tools that interface directly with the engine.<\/p>\n
<\/span>Android 14 Support and the Shift to Kotlin<\/span><\/h2>\nAs mobile operating systems evolve, framework maintainers must keep pace with new security requirements and language paradigms. React Native 0.73 provides full support for Android 14 (API Level 34), codenamed "Upside Down Cake." This update allows developers to target the latest Android SDK, ensuring apps can leverage the newest platform features while remaining compliant with Google Play Store requirements.<\/p>\nTo support Android 14, the framework has upgraded its underlying build tools. The Android Gradle Plugin (AGP) has been moved from version 7.4.x to 8.1.x. This major version bump necessitates a transition to Java 17 as the minimum requirement for building Android applications. While this represents a breaking change for some legacy build environments, it brings React Native into alignment with the modern Android development ecosystem.<\/p>\n
In a move that reflects broader industry trends, Kotlin is now the recommended language for Android apps built with React Native. The default project template has been rewritten from Java to Kotlin. The team reports that the new MainActivity.kt<\/code> and MainApplication.kt<\/code> files are approximately 36% smaller than their Java predecessors, offering a more concise and readable entry point for native logic. To assist developers with this transition, the React Native Upgrade Helper and Android Studio\u2019s built-in conversion utilities have been optimized to handle the migration of existing .java<\/code> files to .kt<\/code>.<\/p>\n<\/span>The New Architecture: Realizing Bridgeless Mode<\/span><\/h2>\nSince the introduction of the New Architecture in version 0.68, the React Native community has been testing the New Renderer (Fabric) and the New Native Module System (TurboModules). However, even with these systems enabled, the "Bridge"\u2014the asynchronous communication layer between JavaScript and Native code\u2014remained active to ensure backward compatibility.<\/p>\n
Version 0.73 introduces Bridgeless Mode as an experimental feature. This mode allows developers to disable the creation of the bridge entirely. By removing this legacy layer, the framework moves closer to a fully synchronous, JSI-based (JavaScript Interface) communication model, which reduces overhead and improves startup times. <\/p>\n
To prevent the removal of the bridge from breaking existing ecosystems, the team is shipping a Native Module Interop Layer. This allows legacy modules to function within a Bridgeless environment, providing a bridge-like interface without the actual overhead of the old architecture. The Renderer Interop Layer, introduced in version 0.72, has also been updated to work seamlessly in Bridgeless Mode, ensuring that older UI components remain functional.<\/p>\n
<\/span>Metro Bundler and Stable Symlink Support<\/span><\/h2>\nA long-standing request from developers working in monorepo environments (such as those using Yarn Workspaces, Lerna, or Nx) has been robust support for symlinks. In version 0.73, symlink support in the Metro bundler is now enabled by default. <\/p>\nPreviously, resolving dependencies that were symlinked from other parts of a monorepo required complex workarounds or third-party tools. The new implementation represents symlinks deeply within Metro\u2019s internals, allowing them to work with "Fast Refresh" and incurring minimal performance overhead during the bundling process. This change significantly simplifies the configuration of shared codebases and improves the developer experience for large-scale enterprise projects.<\/p>\n
<\/span>Deprecations and the Path Forward<\/span><\/h2>\nWith the introduction of new tools comes the phased retirement of legacy features. React Native 0.73 marks the beginning of the end for the framework’s native integration with Flipper. The bootstrap code that wires up Flipper\u2019s core plugins is now deprecated and is slated for removal in the next major release. While Flipper will remain available as a standalone tool for native debugging, it will no longer be a "batteries-included" part of the React Native core.<\/p>\n
Similarly, "Remote JavaScript Debugging"\u2014the legacy mode that runs JavaScript inside a web browser\u2014is being deprecated. This mode was often criticized for causing inconsistent app behavior, as the JavaScript environment in a browser differs significantly from the Hermes or JSC environments on a mobile device. Developers are now encouraged to use Hermes for a consistent experience across all platforms, with Safari Developer Tools recommended for direct debugging of JavaScriptCore on iOS.<\/p>\n
The release also marks a change in how TypeScript types are handled. Following the move to first-class TypeScript support in version 0.71, the @types\/react-native<\/code> package is being deprecated for version 0.73. Developers are advised to migrate to the types shipped directly with the react-native<\/code> package to ensure the most accurate and up-to-date type definitions.<\/p>\n<\/span>Timeline and Project Chronology<\/span><\/h2>\nThe journey to version 0.73 has been defined by a series of incremental updates designed to stabilize the New Architecture:<\/p>\n
\nMarch 2022 (v0.68):<\/strong> Introduction of Fabric and TurboModules, the first public components of the New Architecture.<\/li>\nJanuary 2023 (v0.71):<\/strong> TypeScript becomes the default for new projects, simplifying the developer setup.<\/li>\nJune 2023 (v0.72):<\/strong> Introduction of the Renderer Interop Layer and initial experimental symlink support in Metro.<\/li>\nDecember 2023 (v0.73):<\/strong> Release of Bridgeless Mode and transition to Kotlin as the recommended Android language.<\/li>\n<\/ul>\nLooking ahead, version 0.73 will be the final release to support Android 5.0 (API Level 21). The upcoming version 0.74 will raise the minimum SDK requirement to Android 6.0 (API Level 23), allowing the framework to shed legacy compatibility code and further optimize performance.<\/p>\n<\/span>Industry Implications and Community Reaction<\/span><\/h2>\nThe release of 0.73 is seen by industry analysts as a move to solidify React Native\u2019s position in a competitive landscape that includes Flutter and .NET MAUI. By focusing on debugging ergonomics and monorepo support, Meta is addressing the "quality of life" issues that often drive developers toward alternative frameworks.<\/p>\n
The transition to Kotlin and the requirement for Java 17 reflect a broader push for modernization. While these changes require immediate effort from developers to upgrade their build pipelines, the long-term benefit is a more maintainable and secure codebase. The 36% reduction in boilerplate code for Android applications is a particularly strong selling point for developers who have historically found the native side of React Native to be overly verbose.<\/p>\n
Community feedback from early adopters of the New Architecture has been instrumental in the development of Bridgeless Mode. Library maintainers, in particular, are now entering a critical period where they must ensure their packages are compatible with the Interop layers to support the eventual sunsetting of the bridge.<\/p>\n
<\/span>Conclusion<\/span><\/h2>\nReact Native 0.73 represents a comprehensive update that balances the immediate needs of developers\u2014such as better debugging and Android 14 support\u2014with the long-term structural goals of the New Architecture. With over 2,259 commits from 68 contributors, the release underscores the continued vitality of the React Native ecosystem. As Bridgeless Mode matures and the community migrates toward Kotlin and modern build tools, the framework is well-positioned to remain a dominant force in mobile app development for years to come. Developers are encouraged to use the React Native Upgrade Helper to navigate the breaking changes and take advantage of the performance and productivity gains offered in this latest stable version.<\/p>\n","protected":false},"excerpt":{"rendered":"
The React Native core team has officially announced the release of version 0.73, marking a significant milestone in the framework\u2019s multi-year evolution toward a more robust and streamlined development environment. This update introduces a suite of improvements aimed at developer productivity, including a overhauled debugging experience, stable symlink support in the Metro bundler, and full …<\/p>\n","protected":false},"author":11,"featured_media":5887,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[21,4,1938,1937,661,5,340,324,3,1939,10,9,432,811],"class_list":["post-5888","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mobile-application-development","tag-android","tag-apps","tag-bridgeless","tag-debugging","tag-debuts","tag-development","tag-enhanced","tag-launch","tag-mobile","tag-mode","tag-native","tag-react","tag-support","tag-tools"],"_links":{"self":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/posts\/5888","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5888"}],"version-history":[{"count":1,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/posts\/5888\/revisions"}],"predecessor-version":[{"id":6299,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/posts\/5888\/revisions\/6299"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=\/wp\/v2\/media\/5887"}],"wp:attachment":[{"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5888"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5888"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lockitsoft.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5888"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}