React Native for Web

Expensify's @AndrewGable on cross-platform product development: "We're able to reuse 100% of our code...we make sure that [every] feature is going to work on web, mobile, and desktop...way more time shipping to our users" youtu.be/SYWIk9jFSp4?t=…

Tip: Chrome DevTools > Lighthouse visualizes what's in the JavaScript you ship with a Treemap 🔥 e.g. Bluesky uses React Native Web, MobX & Lodash. This tooling helps you understand what's unused, module sizes and if you have duplicate dependencies.

Amazing to see how fast BlueSky was able to get a v1 website and app built by a small team using Expo and React and RN. Makes such a difference when you can write once and put most of your energy into product instead of platforms.

@jamonholmgren If you use React Native for Web you're using Views built on divs. But there's a lot more to UIs than components, and that's where React Native is missing a lot of important features that already exist on web.

I’ve always said that React DOM should look like RN, not the other way around. Instead of divs web devs should be using Views

I’m a bit conflicted, to be honest.

3. Most developers are using React to target the web. Being able to run that code on native with only minor modifications is a huge upsell for React DOM and React Native. No rewrites or re-education needed. But no loss of flexibility for custom RN components either.

2. Designing proprietary cross-platform APIs is very long and difficult work. Implementing an existing cross-platform API should be faster to accomplish and easier for stakeholders to collaborate.

"React DOM for Native". Read the latest iteration of the RFC to reduce API fragmentation across platforms github.com/react-native-c…

Gabriel contributed many of the PRs responsible for bringing React DOM props and styles to React Native 0.71. Thanks for all the quality work!

React Native now supports more of the props, styles, and events found in React DOM. This is another step forward in making it easier to share code been native and web apps

Try the canary release of React Native for Web 0.19. Support for React 18, compatibility with DOM props, and a lot of API deprecations. github.com/necolas/react-…

Our team has been working on an experimental cross-platform pointer API for React Native this past year and we're excited to share our progress! Check out our post on motivations, benefits, and how to try it out. reactnative.dev/blog/2022/12/1…

The React Native RFC to reduce API fragmentation across platforms has had a major update. The proposal amounts to supporting a strict subset of DOM and CSS APIs. github.com/react-native-c…

Tell us how we can improve React Native! Now, more than ever, your feedback will influence the direction of React Native. Thank you 🙂 github.com/react-native-c…

React Native is on track to add support for 29 W3C props, including several aria-* props, thanks to contributions from the OSS community. Thanks to everyone who wrote patches to make this happen! github.com/facebook/react…

We're looking for the community to help us improve interop between React Native and React DOM component props and styles. Take a look at these issues for opportunities to contribute to this effort! github.com/facebook/react… github.com/facebook/react…

We're looking for the React community to help us improve interop between @reactnative and @reactjs component props and styles. Take a look at these issues for opportunities to contribute to this effort! github.com/facebook/react… github.com/facebook/react…

Please leave feedback on GitHub (not Twitter) for this RFC by the end of the week

React Native RFC: Reduce API fragmentation across platforms github.com/react-native-c…

If you had to design cross-platform React components & APIs from scratch, what would your design principles be and what would the user-facing API look like?