Twitter.com's HTML, which is produced by React Native for Web, explained

Re:Twitter.com's HTML, which is produced by React Native for... by lemax on Thursday September 02, 2021 @01:09PM (#28394613)

React and React Native are separate tools, and they don't play with each other. You actually need to build two separate apps and you don't get much of any re-use. For example, you can't use Material UI for React in React Native, and you can't build a React component library and just pull it into React Native.

So if you want a fully cross platform React experience, you need React Native from the get-go and to compile it for web when you want web.

[ Parent | on HN ]

Re:Twitter.com's HTML, which is produced by React Native for... by jamesisaac on Thursday September 02, 2021 @01:28PM (#28394872)

This isn't really accurate. Presuming you're using react-native-web [1] (the most popular version of RN targeting the web, although there are others), it's essentially just a set of components and APIs, fulfilling RN's API, which sit on top of React DOM.

So anything you could do in React, you can also do in RNWeb, as it's a superset of React.

Of course, you'd need to use the RN components if you want to share code between web and native mobile. But there's nothing stopping you reaching a high degree of code re-use, and/or using React components for the web-only portion of a RNWeb project.

[1] https://github.com/necolas/react-native-web

[ Parent | on HN ]

Re:Twitter.com's HTML, which is produced by React Native for... by usrusr on Thursday September 02, 2021 @01:23PM (#28394797)

Almost holding my breath for the time we see a version of react native for web getting packaged into a container that mimicks a native mobile app. And back then I thought that I've seen it all when apps built with scalajs-react-native appeared on Android.

[ Parent | on HN ]