A lot iPhone apps already use React. There’s a sample of a few on the React Native site: https://reactnative.dev/showcase. It’s almost certain that you have at least one React Native app installed on your phone :)
I’m not sure what being able to run different browsers has to do with Electron, as Electron doesn’t run on mobile at all.
Sites already misbehave in Safari because there’s so many Safari-specific bugs. It’s similar to IE6 in that sites often need Safari-specific hacks to make them work properly.
Technically React DOM doesn’t need a browser either - it works fine with Node.js + jsdom for example, or really any JS engine. Tests written using React Testing Library don’t use a browser. There’s also React Server Components, and React can be used to render non-HTML content too.
Why would someone use React DOM on iOS when React Native exists, though? That’s the part I don’t understand. The core concepts are the same between the two, and you can share a large amount of code between a React web app and a React Native mobile app (even moreso if you use react-native-web for the web app).
It’s only React now. But misguided developers WILL also package Chrome if given the chance.
And maybe it’s not Safari making the sites misbehave, maybe it’s Google pushing arbitrary features via their Chromium/Chrome ownership and developers optimising for them instead of adhering to actual standards?
Will they? It’s possible to do on Android but I’ve never heard of anyone doing it. Cordova on Android uses the Android web view component rather than ship its own copy of Chromium. Of course Android web view is now Chrome so it’s less likely that you would have difficult compatibility problems that would make you want to ship your own browser engine.
A lot iPhone apps already use React. There’s a sample of a few on the React Native site: https://reactnative.dev/showcase. It’s almost certain that you have at least one React Native app installed on your phone :)
I’m not sure what being able to run different browsers has to do with Electron, as Electron doesn’t run on mobile at all.
Sites already misbehave in Safari because there’s so many Safari-specific bugs. It’s similar to IE6 in that sites often need Safari-specific hacks to make them work properly.
React Native and React are different. React Native does not use a web browser.
Technically React DOM doesn’t need a browser either - it works fine with Node.js + jsdom for example, or really any JS engine. Tests written using React Testing Library don’t use a browser. There’s also React Server Components, and React can be used to render non-HTML content too.
Why would someone use React DOM on iOS when React Native exists, though? That’s the part I don’t understand. The core concepts are the same between the two, and you can share a large amount of code between a React web app and a React Native mobile app (even moreso if you use react-native-web for the web app).
It’s only React now. But misguided developers WILL also package Chrome if given the chance.
And maybe it’s not Safari making the sites misbehave, maybe it’s Google pushing arbitrary features via their Chromium/Chrome ownership and developers optimising for them instead of adhering to actual standards?
I agree with your reasoning. I refuse to use chrome. Even at work I use it only for the sites that are non functional.
I still think this is a good thing and hope they do keyboards next because fuck do I hate swipe typing on iPhone.
If you can get used to the idea of carrying a brick, maybe have a look at Clicks Keyboard.
It is, though. You can build a modern web app and it’ll work fine in Chrome, work fine in Firefox, but have weird issues in Safari.
Will they? It’s possible to do on Android but I’ve never heard of anyone doing it. Cordova on Android uses the Android web view component rather than ship its own copy of Chromium. Of course Android web view is now Chrome so it’s less likely that you would have difficult compatibility problems that would make you want to ship your own browser engine.