iOS Browser Choice

Last week, when I was discussing with some experienced web developers, I was surprised by one fact: iOS has no browser choice at all. Everything is Safari. You can download apps named Chrome, Firefox, or other names, but they are all just Safari shells. You browse the web on iOS, and it's actually Safari.

Maybe I should use the statement from the App Store audit guide: WebKit. I usually think that using the names commonly used by browsers to refer to them is clearer than using the underlying engine (at least the three major browsers currently have their own engines), but in this case, the engine is the key.

My feeling is: This is too bad. I had this expensive computer in my pocket and found it was extremely restricted in terms of the browser engine, which felt unfair. My Apple laptop doesn't have that limitation, and I hope it will never have.

Of course, there are many subtleties here. My Apple laptop also has restrictions and I can't install any system I want unless it goes through the official route. I also like some level of audit mechanism for iOS apps and sometimes even wish it was a bit stricter. For example, when I tried to download simple games for my kids, the games I ended up downloading were filled with inducing payments, ads and various dark modes, and I felt the developers should go to jail. I hope Apple doesn't allow this kind of junk to appear on the App Store at all. So, I also hope that the audit mechanism will be stricter and more relaxed.

But the bad thing about the lack of browser choice on iOS is not only the concept of the audit mechanism, but also the fact that WebKit on iOS is not outstanding. See Dave's article, which outlines some of the issues I empathize from the perspective of everyday web developers. And, since WebKit has few competitors on iOS, since Apple doesn't allow competition , the motivation to improve Safari is much lower than it should have been.

This is not like Google's AMP, if you really don't like it, you can either not use it on your own website or redirect yourself to other places on other websites. This choice is up to you.

However, I'm not as capable of talking about this as many others, so what I really want to do is point out some recent posts. Let me quote some of these...

Deeply discuss iOS engine selection—Alex Russell

This is not a theoretical problem; the need to redevelop features through a "wipe" to use mechanisms with less security and poor testing and analysis has led to serious security issues in alternative iOS browsers. Far from isolating responsible WebKit browsers from security issues, Apple's policy has created a veritable "bug farm" for projects that struggle in Apple's lack of WebKit capabilities and can safely and reliably provide high-fidelity capabilities on other platforms.

Of course, this is a serious problem for the argument that why Apple should be solely responsible for providing browser engine updates on iOS.

Chrome is the new Safari. The same goes for Edge and Firefox. — Niels Leeenheer

Both Safari and Chrome teams want to make the network safer and work hard to improve it. But they have different opinions on what the network should be.

Google focuses on improving the network by enhancing its network capabilities. Extend the relevance of the network beyond today’s possibilities. This also means allowing it to compete with native apps, which the Android team certainly doesn't always agree with.

Safari seems to focus on improving the current network. Make it a safer, faster, and more beautiful place. If you want more stuff, you can use an application to implement it.

<meta charset="utf-8"> Browser selection on Apple iOS: Privacy and Security - Stuart Langridge

Alternative browsers on iOS are not limited to WebKit, but also to the current version of WebKit in Safari. It is not even allowed to use different or newer versions of WebKit itself.

Even active users who struggle to get rid of browser choices that are forced to use actually have no choice; if they choose a different browser, they will still get the same browser. If people have demand for something, the market cannot provide it because competition is not allowed.

Briefing for the UK Competition and Marketing Authority on Apple's iOS browser monopoly and progressive web applications—Bruce Lawson

[…] These people at Echo Pharmacy, they not only have a great website, but they also have to build an app for iOS just because they want to send push notifications. And, perhaps ironically, given that Apple insists on doing this for security and privacy, that is, if I choose to install this app, I will also allow it to access my health and fitness data, my contact information, my identifier sensitive information, financial information, user content, user data and diagnostic information. And if I use PWA and have push notifications, I won't leak any of this data.

So we can see that despite Apple's claims, I can't recommend PWA as an equivalent experience on iOS just because of push notifications. But this not only harms existing businesses, but also hinders the development of future businesses.

I hear few people defend Apple's choice of using Safari only on iOS. Most of them are vague and unable to trust Google 's statement, focusing on privacy, performance, or both. All in all, no one wants this kind of lack of choice except Apple.

As far as I know, Apple has not issued any very clear explanation on this requirement. It would be great if you could hear these instructions, because maybe this way, whatever the reason could be solved.

We hear shocking technical news every day. I would love to wake up one morning and see the news that “Apple now allows other browser engines on iOS”. You will hear a faint sound from the air ! , because I've already shouted out loud in my office in Bend, Oregon, and you can even hear it from your home.

The above is the detailed content of iOS Browser Choice. For more information, please follow other related articles on the PHP Chinese website!