React Summit by GitNation is around the corner, and this one is looking dangerously packed. React Server Components, React Compiler, TanStack, AI tooling, Claude Code, Cursor, Expo, React Query, Redux… and a whole lot of beer! The kind of lineup where you open the schedule “just to check one talk” and somehow lose 40 minutes. Some names worth watching: Scott Tolinski Kadi Kraman Dominik Dorfmeister Mark Erikson Manuel Schiller Aleksei Petrov Mike Grabowski And a lot more people with dangerously strong opinions about how we should build frontends in 2026. React Summit is happening June 12 & 16, in Amsterdam and online. If you subscribe to The React Native Rewind, we'll be dropping a 15% latecomers discount code in Tuesday's newsletter. Or, if you're feeling impatient, just reply to the latest newsletter email with "I Want It", and we'll send it over early, just for you 😉 So, if you're in the React ecosystem and needed a suspiciously convenient excuse to subscribe to The React Native Rewind before conference season gets weird... This is probably it. 👉 reactsummit.com/ #ReactSummit #ReactJS #ReactNative #JavaScript #WebDevelopment #FrontendDevelopment #ExpoDev #SoftwareEngineering

Getting The Collapse onto Amazon Fire TV meant using a single @collapse/app package to run the same story branches on iOS, Android, and Fire TV. Then a scene loads, the voice narration plays on mobile, and on Fire TV that same line plays to a silent room. What we'd forgotten to tell the OS, and how we found it, is in the write-up. reactnativerewind.com/guides… #ReactNative #FireTV #VegaOS #AmazonDevices #MobileDev #AppDev #JavaScript #DevCommunity

A scene loads in our game. A line of narration is supposed to play. The Fire TV sits there in silence. No exception. No warning. Just nothing. We were porting The Collapse, our narrative decision game, from Expo to Amazon Fire TV. Audio on mobile runs through expo-audio. The instinct was to find the Vega equivalent. On mobile, audio is handled by expo-audio. Reaching for the Vega OS equivalent, we found something more interesting. 𝗩𝗲𝗴𝗮 𝗢𝗦 𝗮𝘂𝗱𝗶𝗼 𝗶𝘀 𝗮 𝗯𝗿𝗼𝘄𝘀𝗲𝗿 𝗔𝗣𝗜 The package is 𝗮𝗺𝗮𝘇𝗼𝗻-𝗱𝗲𝘃𝗶𝗰𝗲𝘀/𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝘄𝟯𝗰𝗺𝗲𝗱𝗶𝗮, a native implementation of the W3C HTMLMediaElement spec. The same model that runs (audio) and (video) tags in every browser since the HTML5 era, only it runs natively on a TV. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝘀𝗶𝗱𝗲? ➡️ 𝗛𝗧𝗠𝗟𝗔𝘂𝗱𝗶𝗼𝗘𝗹𝗲𝗺𝗲𝗻𝘁 𝗮𝘀 𝗮 𝗰𝗹𝗮𝘀𝘀: AudioPlayer is a TypeScript class, not a React component. You call new AudioPlayer(), initialize(), set src, listen for 'ended'. Anyone who has touched a browser (audio) tag will recognise every line. ➡️ 𝗠𝗦𝗘 𝗮𝗻𝗱 𝗘𝗠𝗘 𝗽𝗼𝗹𝘆𝗳𝗶𝗹𝗹𝘀: Media Source Extensions and Encrypted Media Extensions ship with the package, which is the spec stack behind HLS, DASH, and DRM in every modern browser. ➡️ 𝗦𝗵𝗮𝗸𝗮 𝗣𝗹𝗮𝘆𝗲𝗿 𝗿𝘂𝗻𝘀 𝗼𝗻 𝘁𝗼𝗽 𝗼𝗳 𝗶𝘁: Vega OS ships a Shaka build that uses this module as its media layer, the same Shaka that powers half the streaming apps on the web. ➡️ 𝗢𝗻𝗲 𝗲𝘅𝘁𝗿𝗮 𝗰𝗮𝗹𝗹 𝘃𝘀 𝘁𝗵𝗲 𝗯𝗿𝗼𝘄𝘀𝗲𝗿: An explicit await player.initialize is required before assigning src, because the native session underneath needs to be set up before the device will make a sound. 𝗪𝗵𝘆 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 Long-running media sessions are the actual job of a TV runtime. Browsers spent fifteen years working out streaming buffers, gapless playback, ad insertion, captions, and DRM. Vega OS borrowed the model from the web rather than inventing a new one. We didn't arrive at the package name by guessing. We asked 𝗔𝗺𝗮𝘇𝗼𝗻 𝗗𝗲𝘃𝗶𝗰𝗲𝘀 𝗕𝘂𝗶𝗹𝗱𝗲𝗿 𝗧𝗼𝗼𝗹𝘀, the MCP server that grounds AI coding agents in Vega OS's SDK-versioned docs, and it pointed straight at @amazon-devices/react-native-w3cmedia. A native API built on a W3C spec, shipped under an @amazon-devices/ scope, is exactly the kind of thing an agent gets right with SDK context and guesses at without it. One conversation, working audio. That's the difference between an AI coding agent with Vega OS context and one without. 👉 fandf.co/4udTV4f #ReactNative #Expo #AmazonFireTV #VegaOS #MCP #AIAgents #MobileDev #JavaScript #WebAudio #OpenSource This post was sponsored by Amazon. If you want to see how to actually monetise your existing code on their platform, check out Amazon Devices Builder Tools.

I got to meet the guys behind @ReactNativeRwd and they were super cool! Definitely check it out.

Jay Meistrich (@jmeistrich) has quietly built half of your app's performance layer. In this 7-minute interview, we ask him about life as a digital nomad after 15 years without a fixed address, Legend List 3.0, what's next for the Legend ecosystem, and how to orchestrate a swarm of AI agents. #ReactNative #LegendList #DigitalNomad #AIAgents #MobileDev #LegendState #ReactNativePerformance

👽🛸 love those aliens from rewind

Caught up with Petr Chalupa and Zarif Abdalimov at App.js in Kraków to talk about @react_prague and the community they've built. It was a pretty off-the-cuff chat, but a good one. Really interesting hearing how they got it off the ground and the energy they’re bringing to the React and React Native scene in Prague. Worth a watch if you want to see what a local dev community can look like. And if you’re anywhere near Prague, definitely check them out; they’re also looking for speakers, so it’s a nice opportunity to get involved with the community, too. #ReactNative #React #Expo #ReactPrague #JavaScript #MobileDev #DevCommunity #Meetup

If you are at App.js come say UFO 🛸

There are three hard things in computer science. 1️⃣ Cache invalidation 2️⃣ Naming things 3️⃣ Getting your PR reviewed before the heat death of the universe We can't help with the first two. But we made 20 memes for the third one. They're in the latest issue of React Native Rewind, which landed in your inbox this morning. If you're not subscribed yet, that's a you problem we can fix. Sign up, and we'll send them over in your welcome email. Never again will you stare at a "requested changes" notification from three days ago, wondering if you've been ghosted by your own team. 👉 reactnativerewind.com/

Take a look if building AR/VR inside the ecosystem has ever been on your wishlist.