Yup. "2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript."[0]

[0] https://developer.apple.com/app-store/review/guidelines/#sof...

Firefox (and all browsers on iOS) is just a wrapper around the Safari engine, because of Apple rules. On Android and desktop (including MacOS) it's fully custom.

Not just Webkit - it's a Safari WebView in disguise (pretty decent disguise though, I use it daily myself). Apple doesn't allow any other type of browser on iOS.

Firefox on ios is pretty handicapped vs on Android. Like most things it's a tradeoff. Also the javascript engine isn't nearly as fast as the one for Safari on ios. That said I still use firefox there because i sync everything on firefox, also because of the built in night mode which is close enough to darkreader for my usage.

Firefox on iPhone is a wrapper around Safari.

Webkit is not safari. It doesn't use the same ui or bookmarks for example.

It is, in fact, Safari. As another commentor noted, it's an instance of Safari Webview, not just webkit. The only thing you control when developing third-party apps is the UI/UX.

> an instance of Safari Webview,

there is no "Safari Webview" -- GP is being pedantic but he is right here. WKWebView is not Safari, anymore than Chrome was Safari before it forked off into using Blink. WebKit != Safari

Chrome had its own build of WebKit with custom patches even before Blink - in no way comparable to embedding Apples build made for Safari.

Obviously, but I don’t see what that has to do with my comment? Browser engines are still not the same thing as browsers.