We’re happy to announce early access for React Native 0.83 for Vega OS-based Fire TV devices. The recently released SDK v0.24 brings better tooling (React Compiler and React Native DevTools), updated capabilities (for example, style props such as filter and boxShadow) and libraries. This release also improves performance during development (Metro bundler) and for end users (app startup).
What’s New
- AI-Powered Upgrade: Amazon Devices Builder Tools offers an MCP server that can assist you in upgrading from RN 0.72 to RN 0.83 (see “How To Migrate” below).
- React 19: RN 0.83 bundles React 19.2, which improves how suspended components are handled during concurrent rendering, and adds better resource preloading. On Vega, concurrent rendering is now enabled by default, giving smoother interactions during complex UI transitions.
- Performance and layout improvements: Metro bundler now starts approximately 15x faster, apps show improved time-to-first-screen thanks to Hermes V1, and new Yoga layout capabilities align more closely with CSS.
- Density-Independent Pixels (DIP): RN 0.83 for Vega adopts DIP for layout units, so a single style specification renders at a consistent physical size across devices with different screen densities. This aligns Vega with the convention used on other React Native platforms including Fire OS. See the migration guide for how to update existing styles.
- New components and APIs: RN 0.83 introduces new style props (boxShadow, filter, mixBlendMode) that enable new features such as image blurs and blending as well as shadows around view components.
- JS stable APIs: As first introduced in RN 0.80, the JavaScript API is moving towards stability by locking down deep imports (they now produce errors when used) and by providing a strict TypeScript API. This new API will make apps more future-proof.
- React Native DevTools: With Hermes’s CDP support, RN 0.83 provides better debugging as well as network and performance tabs as part of a new desktop app, reducing the need to set up separate tools such as Charles Proxy.
- DevEx tooling improvements: RN 0.83 introduces the React Compiler (which automates memoization), adds support for custom Metro resolvers, and delivers more reliable Fast Refresh.
- Library support: Most libraries have been updated for RN 0.83, as you can see in the list of supported libraries. Refer to the detailed information for each of the libraries to see what’s new for each individual library. A limited set of libraries are scheduled for the next SDK release.
How To Migrate
We encourage developers to migrate to RN 0.83 at their earliest convenience. The migration delivers a better developer experience, an upgraded user experience, and closer alignment with any codebase you may have on non-Vega devices.
- The dedicated migration page for React Native 0.83 provides you with the prerequisites and detailed steps for the two available upgrade paths: AI-assisted (using the Amazon Devices Builder Tools MCP server) or manual. AI-assisted migration offers an interactive mode where you remain in control. Please review the Known Issues section of the SDK 0.24 release notes before starting your migration.
- You can make use of new developer tools in RN 0.83 (specifically React Native DevTools). Existing Amazon tools (e.g. KPI Visualizer, VVD, Amazon Devices Builder Tools) support RN 0.83 without major change.
Coming soon: Improved headless task support (a development-only workaround is available today), and additional libraries (e.g. expo-image and expo-font).
FAQ:
Can I use SDK 0.24 for both RN 0.72 and 0.83?
Yes, SDK 0.24 supports both RN 0.72 and 0.83. We encourage you to upgrade to SDK 0.24 even if you plan to stay on RN 0.72 for now: Amazon tooling such as VVD will continue to evolve with new capabilities irrespective of RN release.
When do I need to migrate to RN 0.83? Will my 0.72 apps continue to work?
RN 0.83 is in early access, and RN 0.72 remains supported into 2027. That said, RN 0.72 will not receive new features. Staying on RN 0.72 means missing the developer-productivity and user-experience improvements RN 0.83 delivers, including the React Compiler, React Native DevTools, and Density-Independent Pixels. We encourage you to plan your migration as soon as possible.
What is the effort required for migration in manual and AI-assisted mode?
Many partners have told us that manual RN upgrades can take anywhere between a week and a month. Based on initial partner testing, AI-assisted code migration can be done in less than one day, although this does not include testing. Nonetheless, your app and the agent you use may influence the actual outcome. We have made sure that the most popular agents (for example Claude, Codex, Copilot, Cursor and Kiro) can be used so that your workflow is not disrupted. We are looking forward to developer feedback so we can address any remaining issues.
Are there more breaking changes coming?
RN 0.83 has several breaking changes compared to RN 0.72, and these all come with SDK 0.24. For your future planning, you should assume the following:
- Experimental SDK-preview APIs introduced during Open Beta will be retired in an upcoming SDK release. You should migrate off them before the retirement window.
- Future SDK releases will pick up new upstream React Native versions and their associated breaking changes. Vega bundles these into a single annual uplevel rather than shipping incremental breaks, so migration planning happens on a predictable yearly cadence.
How does React Native for Vega compare with stock RN and RN tvOS?
We have worked with many partners to align their Vega codebase with apps for other devices including Fire OS. We see React Native 0.83 as an important step to close the gap with React Native available for other platforms. This has meant some breaking changes such as Density-Independent Pixels; we have also ported improvements from recent versions of React Native tvOS that will improve the user experience on TV devices (for example, separation of accessible and focusable and improved performance with fewer re-renders).