Typography Gets Love and ScrollView Gets Smarter

Transcript

Hey there, React Native developers! Welcome back to another episode - it's January 18th, 2026, and I'm so excited to dive into today's changes with you. Grab your favorite beverage because we've got some really interesting updates that I think you're going to love.

So today we're looking at four solid commits that showcase something I really appreciate about the React Native team - they're not just shipping flashy new features, they're also taking care of the details that make our daily development lives better. And honestly, some of these "small" fixes are going to make a huge difference for folks who've been pulling their hair out over seemingly mysterious bugs.

Let's start with what might sound like a niche fix but is actually pretty significant. Petar Marinov tackled a font variant bug that was specifically affecting stylistic sets in the New Architecture on Android. Now, if you're not familiar with stylistic sets, they're these cool typography features that let you use alternate character designs in fonts - think different styles of numbers or fancy ligatures in coding fonts.

Here's what was happening: developers were upgrading to the New Architecture and suddenly their beautiful typography was breaking. The `stylistic-{num}` variants were just being ignored, which is super frustrating when you're trying to create polished user interfaces. Petar discovered that while the code could read these font variants, it wasn't properly passing them along to the rendering system. It's like having a translator who understands what you're saying but forgets to actually translate it!

The fix involved updating the conversion helpers to properly map these stylistic features. And I love that Petar included before and after screenshots using FiraCode - a font that developers absolutely adore for its stylistic features. That attention to a proper test case really shows they care about getting this right.

Now, here's something that's going to be a game-changer for a lot of Android developers. Johan Kasperi added a new prop called `scrollsChildToFocus` to ScrollView. This might sound simple, but it solves a really common pain point.

You know how when you tap on a TextInput inside a ScrollView, Android automatically scrolls to bring that input into view? Usually that's great, but sometimes it completely breaks your carefully crafted user experience. Maybe you're building custom scroll animations, or you're working with virtualized lists, or you just don't want focus changes to mess with your scroll position.

Well, now you can set `scrollsChildToFocus` to false and take full control. It's one of those props that seems small but gives you back so much control over your app's behavior. Johan connected this to some long-standing GitHub issues, which I always love to see - when the team directly addresses developer pain points that have been bubbling up in the community.

We also got some infrastructure love from Marco Wang with Flow type updates and a version bump to Flow 0.297.0. I know type system updates aren't the most exciting thing to talk about, but this stuff is so important for keeping our development experience smooth and catching bugs before they reach production.

These infrastructure commits might seem boring, but they're like changing the oil in your car - absolutely essential for keeping everything running smoothly. The Flow updates touch things like React DOM types, test renderer types, and various utility libraries that power our development workflow.

For today's focus, here's what I'd encourage you to check out: If you're using custom fonts with stylistic features and you've been having trouble with the New Architecture on Android, definitely test this fix out. And if you're building Android apps where focus management is important - especially if you're working with forms or complex scroll interactions - experiment with that new `scrollsChildToFocus` prop. It might solve some UX issues you didn't even realize you could fix.

That's a wrap for today! It's these kinds of thoughtful improvements that make React Native such a joy to work with. The team continues to listen to the community and make those quality-of-life improvements that really matter.

Keep building amazing things, and I'll catch you in the next episode!