React Native Web exists [0]. But I agree, having parts be third party doesn't mesh well with being a complete framework for building apps (on whatever platform you need).
[0] https://github.com/necolas/react-native-web
In Using Flutter to build a native-looking desktop app for macOS and Windowsnecolas
react-native-web
JavaScript2015–2023
necolas / react-native-web
react-native-web
Cross-platform React UI packages
45Distinct people
51Mentions
0Explicit recommenders
22.2KGitHub stars
What to know before exploring
What it is
Cross-platform React UI packages
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- microsoft/react-native-windows · linked in 3 of the same discussions
- ptmt/react-native-macos · linked in 3 of the same discussions
- facebookarchive/react-360 · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year51 dated mentions
Observed mentions: 2015-09-17 14:29:41 UTC to 2023-01-31 20:46:17 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 12 | 1 | 11 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 14 | 0 | 14 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Development monorepo
This is the development monorepo for "React Native for Web" and related projects.
Structure
.github
Contains workflows used by GitHub Actions.
Contains issue templates.
packages
react-native-web
Contains the individual packages managed in the monorepo.
scripts
Contains Node.js scripts for miscellaneous tasks.
Tasks
build
Use npm run build to run the build script in every package.
Use npm run build -w <package-name> to run the build script for a specific package.
dev
Use npm run dev to run the dev script in every package.
Use npm run dev -w <package-name> to run the dev script for a specific package.
test
Use npm run test to run tests for every package.
More details can be found in the contributing guide below.
Contributing
Development happens in the open on GitHub and we are grateful for contributions including bugfixes, improvements, and ideas.
Code of conduct
This project expects all participants to adhere to Meta's OSS Code of Conduct. Please read the full text so that you can understand what actions will and will not be tolerated.
Contributing guide
Read the contributing guide to learn about the development process, how to propose bugfixes and improvements, and how to build and test your changes to React Native for Web.
Good first issues
To help you get you familiar with the contribution process, there is a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started.
Read the full README on GitHubWhat Hacker News says
5 sourcesThis 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
In Twitter.com's HTML, which is produced by React Native for Web, explainedAfaik twitter uses (some form of) react-native-web.
So I guess it's because: https://github.com/necolas/react-native-web/pull/556
Basically some browsers don't support display flex on certain elements like button, using a div instead of a button solves that issue.
Generally: I would suggest to use a button tag unless you run into issues (and know what you are doing).
I don't think using `<div role="button">` is perse worse as long as you implement all the behaviour and styling of the button element like focus, keyboard events and similar.
For juniors, buttons should be taught as the way to go, as with many things in web it's about understanding the pros and cons and knowing why you do something or not. If you don't have a lot of experience, stay away from reimplementing the button tag.
In Why does twitter.com use div role=button instead of button?React Native Web (https://github.com/necolas/react-native-web) is a nice solution for better cross-compatibility between React Native and React DOM.
React DOM is very coupled with DOM elements, so React Native Web abstracts away web-specific things, so that code is more sharable.
In Vue Native (2018)