Surely these amazing PWAs that Apple doesn't allow should exist there. The question about hard-not-hard to google.Īlways in discussions about Safari you will find someone complaining about "Apple crippling PWAs" and coming up with yet another random APIs that they absoluely need to finally make a great PWA.Īlways in these discussions I hint that Android is 70% worldwide market share, and has none of the perceived restrictions on PWAs. It has power-efficient AdBlocking API, it uses correct HW for rendering content and it is more memory-friendly.Īgain, and I can't stress this enough, Chrome and Chromium are developed by a company which main source of revenue is AdTech. Safari is in the same vein but even better and without any issues mentioned before. It's JS engine had issues, true, but despite that, it was a decent browser outperforming Chrome on many critical aspects of user experience. It used native system APIs for input integration, rendering, scroll and memory management, making it much faster and efficient especially on low power devices. "Please use Chrome to continue".įor example, despite Edge woes, the Trident-based version was markedly better looking, and better performing as long as the tabs count didn't get massive. Honestly, I'm appalled anyone would seriously consider this.Ĭhrome is taking over due to inertia and many websites targeting it as the one and only legal implementation of web standards, regardless of the actual spec. I can't imagine a world where this argument would be correct. But, that was a while ago-maybe it's gotten better. It's one of of several reasons that, while Android developent was probably easier even then at a hobbiest level than iOS was, it was a much bigger pain in the ass to support & develop for at any kind of scale. had no need to, since that never caused many problems. On iOS, we both couldn't bundle our own JS or browser engine (by policy) and. We encountered multiple real problems in the wild trying to use the built-in engine(s). IIRC we ended up bundling a JS engine to get around the worst of it, for what we needed-might have been a full browser we bundled, can't recall for sure. The result was that the only way to obtain non-crazymaking behavior and bug report loads on Android, if you needed a webview or even just a javascript engine, was to bundle your own thing. There were basically no guarantees at all. Not only might you not get a particular version of Chrome/Blink providing your webview-you might get any engine. Last time I developed mobile apps that depended on consistent webview functionality, Android went a step farther: Android vendors could replace the webview provider with something custom, and some did (Samsung, at the time, notably and impossible-to-ignore since they're huge).
0 kommentar(er)
