UIWebView 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.

WKWebView is out-of-process and has a JIT.

Ah, you're correct - not sure why I thought otherwise, especially when I touch WKWebView pretty often.

Perhaps you confused it with JavaScriptCore?

Hmmm, possibly. Either way thanks for the catch!

Printing 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).

> 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.

React-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.

React Native doesn't use a webview.