RSD has gone quiet — what can we do about it?

[MoOx]

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:

• SVG support — a significant gap across all platforms (feature) <svg> element #4 / Implement <svg> support #272
• StyleX dependency updates — RSD is still on 0.15.x
• Stronger TypeScript types
• Cross-platform virtualization patterns (Cross-platform virtualization #417)
• Accessibility gaps — incomplete role support on native ([a11y] role prop not fully supported on React Native #422)
• and many more interesting issues

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:

• @necolas — Is there anything you can share about your availability or plans for RSD going forward? Even a brief status update would help the community align.
• To the Meta / React Native team — Is RSD still part of Meta's roadmap? If internal priorities have shifted, would you be open to giving community members more ownership over the project?
• To everyone using or watching RSD — If you care about this project's future, now is the time to speak up. React to this discussion, share what you're building with RSD, and let's show that the demand is real.

The community is here and ready to contribute. RSD is too good of an idea to let it stall. ❤️

[Freddy03h]

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.
Could you share any updates on the current status of react-strict-dom, particularly regarding its internal adoption and future direction?

Thank you.

[yaminyassin]

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