Replies: 9 comments 15 replies
-
|
Hi, I’m a solo developer working on a cross-platform application. I’ve had a React Native app in production for 9 years, along with its PWA counterpart using React Native Web for the past 4 years. Cross-platform development is essential for me. From my perspective, solutions like react-strict-dom, which push cross-platform capabilities further, are key to making it realistically possible to bring applications to less dominant platforms such as macOS, Windows, Horizon, or visionOS. Without this kind of approach, it becomes very difficult to seriously consider supporting those platforms. I strongly align with the vision behind react-strict-dom, which I believe is a step in the right direction and potentially an important part of the future of React Native. That said, I’ve become a bit concerned about the project given the lack of updates in recent months. I’m also aware that the project lead and main contributor is no longer at Meta. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
What's really concerning is the lack of a roadmap and updates from meta around the project. React Native has made strides in getting web capabilities and this project really needs to be taking advantage of them |
Beta Was this translation helpful? Give feedback.
-
|
After a bit of pushing from my side we eventually migrated our 130kLOC app/web to RSD. We absolutely love it, but I'm deeply concerned about the non responsiveness of the devs. Even just a "yep this is still alive" from @necolas would be great for my blood pressure lol. |
Beta Was this translation helpful? Give feedback.
-
|
I'm the tech lead for an enterprise design system. We have two separate libraries (one for web/React and one for mobile/RN). We've been making strides internally to make the eventual move to a single RSD based design system by aligning our interfaces and sharing utilities, icons, and theme configuration between ecosystems. We're even moving our web ecosystem (for the whole company) to StyleX. But we're also starting to become concerned that progress has slowed down here, Discussions/Issues are going unanswered, and that PR's are stacking up. Has Meta abandoned this effort? What can the community do to help keep this project moving forward? |
Beta Was this translation helpful? Give feedback.
-
|
poke @SamChou19815 since you recently committed in this repo |
Beta Was this translation helpful? Give feedback.
-
|
Since I gave the cross-platform react talk I feel a bit responsible so I’ll chime in. Know that I haven’t worked at Meta for a year now so none of this is official.
I think a community oriented future for RSD is technically possible, but I don’t know about all the corporate politics involved. I have contributed on and off to StyleX in the year since I left and as long as there’s someone working internally, it possible to get PRs merged. If the community did enough of the work, just getting PRs merged should be easier than more active development. |
Beta Was this translation helpful? Give feedback.
-
|
Lol I just went to the react native for web repo, seems abandoned (last commit 7months) ago, maintainer strongly recommends to use his new thing, react strict dom. Come here, last commit also 7 months ago, also abandoned. To have one person be the maintainer of such important repos is a little questionable |
Beta Was this translation helpful? Give feedback.
-
|
@martinbooth since you merged PRs recently, could you give us some insights ? |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately some of the people responsible for driving RSD have left meta which does mean the rate of development is slower. That said, the project is not abandoned and within meta we're building new products with it. I work on one of those teams and RSD is an important dependency for us, so I will be stepping up to try and get these PRs reviewed/feedback and also bring it up internally that the community would be interested in contributing/keeping this project alive as I believe that would benefit all of us. I am working my way through reviewing other PRs, but some of them will take me a little while as they're pretty big. As for meta sunsetting facebook/instagram apps on the quest.. That would be news to me (and I used to be on the IG quest team). The facebook quest app definitely makes heavy use of RSD and IG quest was never a RSD customer until recently Finally, to address a couple of the points in the original post:
Thanks for raising this |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
React Strict DOM is one of the most promising approaches to cross-platform React development. The philosophy behind it — writing styled components using web standards that work on both web and native — is exactly what the ecosystem needs. I believe in this project and I want to see it thrive.
But I think we need to have an honest conversation about where things stand.
What I'm seeing
The last release (0.0.54) was in October 2025 — 6 months ago. Since then, PRs have been accumulating without review, several discussions remain unanswered, and important issues are sitting idle. Meanwhile, the community is still active: people are adopting RSD, asking questions, and trying to contribute.
What's at stake
There are foundational topics that need attention for RSD to reach its potential:
roleprop not fully supported on React Native #422)These aren't niche requests — they're blockers for broader adoption.
What I'd love to see happen
I'm not here to complain. I'm here because I want to help. A few questions for different people reading this:
The community is here and ready to contribute. RSD is too good of an idea to let it stall. ❤️
Beta Was this translation helpful? Give feedback.
All reactions