announcement: @expo web is dead. Expo will never tell it to you so I will save you the trouble. There is no need making code reuse work everywhere these days. The gap from native to web will always be there. Avoid it at all cost. That said universal apps have a new resurgence these days. How it goes now? You need to embrace the power of the web with frameworks like Vite. Add a thin agent skill to be invoked after a web feature development is done asking to build the feature again for mobile with the same internal API. That is the way.

@bidah @expo i think, a lot of time the point and target of "Expo Web" is missed (incl. here) and it's surprising to me b/c it really adheres well to the Expo and RN/x-platform philosophy in general Expo Web, and Expo in general for that matter, isn't about "build once, run everywhere"

@bidah @expo "Expo Web" as a target is just that, our ambition to make Web a great target for Expo. That explicitly means: - you won't necessarily use React Native Web in the future - you may not want react-strict-dom - you may not want to go "all the way" with a x-platform wrapper code

so "Expo Web is dead" is just disappointing clickbait that misses the mark. Instead, Expo will become a great web framework, regardless of other platforms, and in general, the simple idea here is: You shouldn't have to choose another framework for your web apps. (which drives any speculation on death ad absurdum)

@_philpl @bidah @expo Expo's web target gives the impression it's the equivalent but it's not. I don't doubt you guys will figure that out eventually, expo is awesome wouldn't choose anything else. And I can't wait for web to be a viable option for serious web applications.

@techstack404 @bidah @expo it's closer than some might thing, but yes, agreed, but either way, I just take a bit of issue with "Expo Web" is dead (as said in other replies) because it implies an "end" rather than a "start"