If you’ve shipped a React Native app on Fire TV with Vega OS, you’ve been building with React Native 0.72. We are excited to announce that React Native 0.83 support is now available starting with Vega SDK 0.24. The upgrade brings a lot of good stuff to your TV app:

• React 19 and the React Compiler, which memoises your components for you.
• Hermes v1, a faster JavaScript engine with ahead-of-time compilation
• React Native DevTools, with a built-in profiler and network inspector
• The latest versions of the libraries you rely on, plus new properties from CSS. 

In this post, we’ll cover the migration path from 0.72, show you how the Amazon Devices Builder Tools MCP (ADBT) does most of the heavy lifting for you, and go through the benefits you get from 0.83 in more detail. If you’d rather learn by doing, we’ve also built a hands-on workshop that walks you through the upgrade and lets you try each benefit on a demo app.

Going from 0.72 to 0.83 spans eleven React Native releases, but the good news is that as Vega developers you already have the biggest change from that period: React Native's New Architecture. Vega has run on the New Architecture from day one so there's no architecture migration to worry about.

There’s still plenty to change, though: dependency bumps, Babel and Metro config changes, renamed APIs, and libraries that need new Vega-specific versions. To make the move easier, we built an upgrade agent skill into the Amazon Devices Builder Tools MCP (ADBT), which plugs into your preferred AI coding assistant. The skill walks you through every change your app needs, grounded in Vega-specific knowledge for RN 0.83. Instead of a generic upgrade diff, you get a plan that knows about Vega packages, Vega build tooling and Vega gotchas.

Step 1: Get set up

• Update to Vega SDK 0.24. Run vega sdk list-remote and vega sdk install <version number> and pick the desired release, then check vega --version.
• Install ADBT into your workspace: npx -y @amazon-devices/amazon-devices-buildertools-mcp@latest init- context

Step 2: Work on a branch

Create a fresh branch (git checkout -b upgrade/react-native-0.83) so upgrade changes don’t mix with production work. 

Step 3: Run the upgrade helper

In your preferred agents, just ask: “Use the React Native Upgrade workflow from @amazon-devices/amazon-devices-buildertools-mcp to upgrade my application to RN83.”

The helper detects your current React Native version, validates your project and environment, loads the Vega 0.83 knowledge base, and generates a TODO file. Every change is prioritized with implementation steps, code examples, and file references.

The helper then walks you through the list one change at a time. Pick a change by number, review the guide, and either let the agent implement it or do it yourself and type complete. 

Step 4: Build, run and verify

Build and launch on the Vega Virtual Device or a Fire TV Stick, then check that the Metro output reports React Native 0.83, not 0.72.

Step 5: Turn on the good stuff

While running on 0.83 unlocks some of the benefits, other improvements are opt-in. Enable the React Compiler, then use DevTools to profile your busiest screens (more on this below).

If you are new to Vega OS creating a new app will default to 0.83. Additionally, all of our sample apps on AmazonAppDev GitHub are on 0.83, so you can clone one and start building on the latest supported version from day one. They’re also a handy reference when you’re upgrading your own app and want to see what a finished 0.83 project looks like.

Once you’re on 0.83, you get everything the React Native and React teams have built since 0.72: React 19 and the React Compiler, Hermes v1, a modern DevTools experience, and the latest versions of the libraries the community is building against. 

You can see each of the benefits below running on a demo app in our: 
👉 RN 0.83 upgrade workshop on GitHub

If you’ve built a focus-heavy TV screen, you know the drill: wrap the tile in React.memo, wrap every handler in useCallback, and keep the dependency arrays in sync. Miss one and every tile on the row re-renders on every focus change. The React Compiler does that memoisation for you at build time. 

In the workshop we put a render-count badge on each tile and stripped out all the manual memoisation. On React 18 every tile re-renders on every d-pad press. With the React Compiler switched on, only the two tiles that actually changed (the one losing focus and the one gaining it) re-render, with no memo and no useCallback in the source.

On four tiles that’s a nice demo but on a typical catalogue screen with 30+ tiles across several rows, it’s the difference between hundreds of wasted re-renders per second of navigation and a snappy d-pad.

Note: The upgrade bumps React to 19 but doesn’t switch the compiler on. It’s a separate Babel plugin (babel-plugin-react-compiler), and in a monorepo you’ll likely need a small custom Babel transformer, so Metro picks up the right babel.config.js. 

RN for Vega 0.83 ships Hermes v1, which adds ahead-of-time compilation and type specialization. The biggest wins land on numeric tight loops, recursive calls and string-heavy parsing, which covers a lot of the work a TV app does: parsing large catalogue JSON, sorting and filtering rows, and layout math.

Upstream, the React Native team measured Hermes v1 on Expensify, a large real-world app. On a low-end Android device, they saw bundle load time 3.2% faster and time to interactive 7.6% faster (0.82 release notes). Do note that the improvements strongly depend on the details of your apps, so measure your own.

In the workshop we benchmark a 240×240 matrix multiply (three nested numeric loops, the shape Hermes v1 is built to win on) on both versions.

Note: Compare the trend direction, not the absolute numbers, and always use release builds on the same device. The Vega Virtual Device shares your Mac’s CPU, so for numbers that reflect what your users will see, run on a real Fire TV Stick. 

If you want to go deeper than a micro-benchmark, use ADBT’s performance analysis capability. It runs the KPI Visualizer on your app, then analyses the Perfetto traces against Vega’s KPI targets for Time to First Frame (TTFF), Time to Fully Drawn (TTFD), UI fluidity and key input latency, and pinpoints the CPU hot functions behind any slowdowns. Try asking your agent: “Can you help me debug and fix the Time to First Frame issue in my Vega app?”

On 0.72, debugging on Vega meant the standalone react-devtools flow, and seeing network traffic meant reaching for Charles Proxy or Flipper. On 0.83 you press j in Metro and get React Native DevTools in your browser, with:

• Components. Inspect the tree and look for the Memo ✨ badge that confirms the React Compiler optimized a component.
• Profiler. Record a focus traversal and see exactly which components rendered on each commit.
• Network. Inspect fetch requests, headers, payloads and timings with no proxy and no patching.

Note: You’ll need to forward the Metro port first (vega device start-port-forwarding -p 8081). The Vega 0.24 DevTools docs cover the full setup.

Libraries move to their latest major versions. The upgrade brings the libraries most TV apps depend on up to versions built for React 19, including React Navigation, Gesture Handler, Reanimated 4, Lottie, SVG, Screens and Fast Image. You’ll find the full list, with versions, on the Supported Libraries and Services page.

Expo modules come along too. A set of Expo packages, including expo-image, expo-linear-gradient, expo-file-system, expo-linking and expo-localization, are available for 0.83. That makes it easier to share code with an Expo-based Fire OS, Android TV or Apple TV app. A few Expo packages haven’t been stabilized for 0.83 yet, so check the release notes before you upgrade.

Styling catches up with CSS. RN 0.83 includes Yoga 3, a newer version of React Native’s layout engine, plus a set of CSS-aligned style properties. These are especially useful for focus states on TV:

• boxShadow for focus glows and card depth, with no platform workarounds
• outline for focus rings that don’t shift the layout, because outlines don’t take up space
• filter for effects like blur(), grayscale() or brightness(), for example to dim unfocused tiles
• mixBlendMode for blending artwork and overlays

⏫  Upgrade your app with ADBT

Open your Vega project in your AI coding assistant and ask: Upgrade my Vega app from React Native 0.72 to 0.83

🛠️  See the benefits for yourself

Work through the hands-on workshop to try the React Compiler, React Native DevTools, Hermes v1 and the new styling properties on a demo app. 

👉 Start the RN 0.83 upgrade workshop on GitHub

🗣️ Tell us how it goes

If you hit friction during the upgrade, we want to hear about it. Share feedback through the ADBT feedback flow or come and chat with us on the Amazon Developer community forums. 

📝 Not ready to upgrade yet? Your RN 0.72 app will continue to work through 2027, however, we do recommend migrating to 0.83 as soon as you can, so your users get the benefits sooner.