React 19 in React Native: what changed and what to watch

React 19 made its way into React Native, and unlike some upgrades this one is more "pleasant refinements" than "relearn everything." Still, a major React version in your mobile app is worth understanding before you bump it, because a few changes touch patterns you use every day and a couple will surface real warnings on upgrade.

Here's what's relevant if you build with React Native specifically, leaving aside the web-only bits.

The quality-of-life wins#

ref as a regular prop. You can stop wrapping components in forwardRef just to pass a ref down. In function components, ref can be a normal prop now. A lot of the boilerplate around forwarding refs to a child TextInput or animated view goes away:

// before: forwardRef ceremony
// after: ref is just a prop
function FancyInput({ ref, ...props }) {
  return <TextInput ref={ref} {...props} />;
}

forwardRef still works, so nothing breaks immediately, but new code gets simpler and you can clean up old wrappers over time.

The use hook. A new way to read resources like context (and promises) more flexibly, including conditionally, which the old hook rules didn't allow. In a mobile app the most immediately useful bit is more ergonomic context consumption. It's additive - you don't have to rewrite anything to benefit later.

Better error handling and cleaner ref callbacks. Ref callbacks can return a cleanup function now, which tidies up a pattern that used to be awkward. Small, but it removes a class of "where do I clean this up" questions.

The thing that'll actually show up: stricter behavior#

The change most likely to surface in your app isn't a feature, it's React 19 being stricter and noisier about things that were always a bit wrong. Effects, refs, and certain lifecycle edge cases get clearer warnings. On upgrade you may see new console warnings about patterns that "worked" before - usually they're pointing at a genuine latent issue, not a regression.

Treat the upgrade as a chance to read those warnings rather than silence them. Most are quick fixes and each one is React telling you about something that was already subtly off.

Doing the upgrade#

The realities, from doing it:

• React 19 comes with a React Native version, so this is part of an RN upgrade, not a standalone npm install react@19. You move React Native forward and React comes along at the version that RN release pinned. Don't try to mismatch them.
• Check your major dependencies for React 19 support before upgrading - navigation, animation, state libraries. The ecosystem moved reasonably quickly, but a lagging library is the usual source of upgrade pain, same as every RN bump.
• Expect warnings, budget time to triage them. Not crashes, generally - warnings. But ignoring them defeats the point.
• Test on real devices, both platforms. Always, but especially across a React major.

Should you rush?#

There's no fire here - React 19 isn't a security deadline. But it's the direction the framework is going, the ref-as-prop and use ergonomics are genuinely nice, and staying within a version or two of current keeps every future upgrade smaller. I'd fold it into your normal React Native upgrade cadence rather than treat it as a special event: when you're moving RN forward anyway, take the version that brings React 19, read the new warnings, and clean up what they flag.

The headline is that this is one of the gentler React majors for mobile. The features are additive, the breaking edges are mostly stricter warnings about things you'd want to fix anyway, and the boilerplate reduction is a small daily pleasure once you're on it.