5 ms·
Yeah, that's how I am reading that. Given the headaches caused by Apple finally barring UIWebView (the basis of frameworks like Cordova) from new App Store sub
by bmj 7y ago
Yeah, that's how I am reading that.
Given the headaches caused by Apple finally barring UIWebView (the basis of frameworks like Cordova) from new App Store submissions beginning in April, I'm not surprised FB would do this. There is plenty of rumor-mongering that Apple is going to make it increasingly difficult for apps based on hybrid frameworks through the submission process.
- Klonoar 7y agoUIWebView was deprecated for years, everyone's had plenty of time to move to WKWebView, and it has nothing to do with React Native to boot. Apple legitimately doesn't seem to care about hybrid frameworks, they've been there since day one. Any time it's seemed like it got difficult Apple has backed down. The lack of JIT in WKWebView is probably the only thing that you could stretch here.
- saagarjha 7y agoWKWebView is out-of-process and has a JIT.
- Turing_Machine 7y agoPrinting still sucked pretty bad in WKWebView the last time I looked into it (which admittedly has been a year or two, so maybe that's been fixed).
- Turing_Machine 7y ago> Given the headaches caused by Apple finally barring UIWebView (the basis of frameworks like Cordova) Cordova (and derivatives, such as Ionic) have had WKWebView available for a long time now, I think since iOS 9. The Cordova team added a compile-time flag to force WKWebView in 5.1.0 (out since last November), and will be removing UIWebView altogether in 6.0.
- pier25 7y agoReact Native doesn't use a webview.
- fingerlocks 7y agoReact-native does not run in a webview. The JS binds directly to native elements. In fact, you can easily wrap any native code and make JS bindings to call it directly.