The state of web browsing on the iPad has remained pretty stagnant over the years. Despite all the aesthetic and functional changes that came with the “series 26” refresh across the software portfolio, the underlying experience has remained more or less the same. That predominantly has to do with the fact that Apple wants every browser maker to use the same WebKit rendering engine as Safari on the iPad.
In a nutshell, developers have little to no control over modifying or controlling the WebKit engine, which means the best that they can do is make their browsers look slightly different, but not really offer any meaningful next-gen features or performance optimizations. It’s been nearly 20 months since Apple technically allowed developers in the EU block (and soon, in…
more
Source www.digitaltrends.com
Terms of use and third-party services. More here.