Apple doesn't allow other browser engines but it's on them.
None of these bug tech corps are in the right here, but MS is being more anti-competitive than most.
Apple doesn't allow other browser engines but it's on them.
None of these bug tech corps are in the right here, but MS is being more anti-competitive than most.
If I hadn't been paying attention, I would have thought that they were forcing me to install Edge too.
I’m not saying that’s what’s happening with GP’s experience with Teams, but just pointing out that when thinking about MS app behavior on any platform, it’s a variable that can be present in the corporate context which many “users” remain blissfully unaware of, or see it manifest as these weird rules and behaviors and not acting like other apps. But there can be an entirely different set of user stories at play beneath the surface.
So the correct iOS parallel is not Apple’s refusal to allow non-WebKit engines. But Apple’s hypothetical refusal to allow links to be opened in WebKit-flavored Firefox. Which, for the record, it does let you do.
To be precise: No, they don't. Their engines are based on the same codebase, but they still are running their own installed engines.
In contrast, Apple doesn't just refuse to allow non-WebKit engines. It requires everyone to use the pre-installed, Apple-provided engine. You can't use your own build of WebKit.