Earlier quoted context omitted.
Afaik All 'browsers' in the app store have to be just a skin on top of Safari. Apple has rules against independent rendering code.
Calling it a 'skin on top of Safari' does not really do justice to all the hard work my team has been putting in Firefox for iOS. Apple gives you (limited) access to WebKit. Basically: a rectangular area on the screen that renders web content. To 'skin' it, you have to build a browser application around that. A complete application that handles tabs, user settings, sync, history, bookmarks, reader mode, anything that…
Maybe the term "skin" is not adequate, but IMO the features added by Chrome and Firefox on iOS are not that significant for the browsing experience compared to the "rectangular area". Thanks to Apple, WKWebView based browsers are always going to be second class citizens.
Personally I never understood why you decided to move to iOS. I think you should have stick to your guns.