Future of React Native Web & How we can help

[blazejkustra]

Hi @necolas 👋

First of all, thank you for all the work you’ve put into React Native Web over the years. Its impact on the ecosystem has been huge. As React Native continues to evolve, there are naturally some gaps that have started appearing in RNW, which many teams (including ours) still depend on daily.

I’ve noticed this myself while working with RNW in various projects, and I previously contributed to a couple of issues:

• Exporting types #1684
• Alert: implementation #1026
• Image.resolveAssetSource doesn't work correctly in RNW #1666

I wanted to reach out because I wasn’t sure about the best communication channel for discussing the current and future state of RNW. I know you’ve been focusing mostly on react-strict-dom lately (which looks awesome) but there are still tons of people relying on React Native Web in production.

My question is if you'd be open to more community help with maintaining RNW?
Things like reviewing PRs, implementing missing bits, or taking any of the maintenance load. I’d personally love to help, and I know others would be interested too.

Let me know what you think, and if there’s a better place for this kind of discussion! 🙌

[Dovakeidy]

In case you missed it, @necolas already answered the question in detail here .

Quoting Necolas about PRs:

I will continue to review PRs and merge fixes. But I don't expect to put significant time into major development initiatives.

[necolas]

Hi, yes open to adding maintainers from RN partners like SM & Expo. Let's figure out details in the React discord?

[ericpoulinnz]

@blazejkustra @necolas was there any outcome from the discussion on Discord? I would love to see more development here as moving away from RNW in my production apps will be far too large a job for my team right now. Thank you both, appreciate everything you have done here @necolas and your offer @blazejkustra !