fernandorojo

> If you were to do it all over again, would you think about building on native technologies instead?

Although it took a lot of effort, it was a new set of UI patterns for React Native, and it hadn't really been done well yet.

Where most RN teams go wrong is they never dip to native code. On the contrary, we wrote a lot of native code, both for our own packages and for updating RN core itself.

The benefits with React Native's composition model are hard to beat. For example, thanks to React's composition with hooks and components, we will likely be able to open source most of the problems we solved into an easy-to-consume library. Or at least that's the hope!

Yeah that's what we use (and we showed it in the patch in the blog post).

There was a bug on a particular iOS 26.2 beta, but it looks like it's already fixed

TIL a Cordova app won

Imagine being the first one!

I ultimately prefer React Native's composition model over SwiftUI.

Something that attracts me to RN is that it's easy to drop down to native. We use SwiftUI for a number of components under the hood. But for a full app, React Native felt better.

Our biggest usage of AI was actually a code review bot which lives on GitHub PRs. It reviews our code on every commit. It was originally an internal tool, but it's now Vercel Agent.

We also used v0 for prototyping ideas and designs for the native app.

For the live activities, we used expo-apple-targets. That helps bootstrap it, link assets, etc. The UI itself is SwiftUI. The hard part here was actually the server-driven events for the activities during the stream. Live activities can be annoying to work with using APNs.

You can just use Share.share() from react-native directly for the share sheet.

Checking on this Firefox issue now, thanks for sharing.

Overall, our focus right now is iOS, but we want to do Android at some point. Even though we used React Native, we also wrote a good amount of native Swift code under the hood to power native modules.

Interesting, that actually should work.

Are you on iOS 26.2 by chance? I'm currently investigating a regression on interactive keyboard dismissal specific to iOS 26.2.

Thanks for sharing, sorry about that. We had an issue on the backend with Apple sign in that we just fixed today. Mind signing out and back in to see if it's fixed?

Author of the blog post here. Happy to answer any questions.

This is cool. I hadn’t come across an objective measurement of accents before.

I’m fan of Daishi’s other work (like Zustand and react-hooks-global-state) so I’m intrigued to see this drop. As a longtime Next.js fan it’s cool to see simplified versions of new tech emerge.