Apple is not defending browser engine choice

Re:Apple is not defending browser engine choice by the_gipsy on Friday June 24, 2022 @03:37AM (#31858767)

I wanted to give the iPhone another try. But the web is just so so unusable. No way to install adblockers or real extensions in general. No push notifications. Just one single engine.

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by girvo on Friday June 24, 2022 @03:40AM (#31858784)

You can install Ad Blockers, I use 1Blocker on iOS. It’s not as powerful as uBlock Origin obviously, but it does a more than good enough job by making the web browsable again at least.

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by jandorn on Friday June 24, 2022 @03:43AM (#31858805)

I use a AdGuard Pro, StopTheMadness and a DDG for years now. I don’t miss anything as far as I know. You also have a choice of “different” browser that might offer more.

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by viktorcode on Friday June 24, 2022 @09:37AM (#31861598)

Either you are trolling, or you are that singular kind of user site marketers dream about, who actually want to enable push notification and receive their spam.

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by chunkyguy on Friday June 24, 2022 @03:41AM (#31858794)

Push notifications have finally landed with iOS 16

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by agust on Friday June 24, 2022 @05:43AM (#31859582)

iOS 16 is not out yet, and Apple stated that Push notifications won't come before 2023. So no, Push notifications have not landed (yet).

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by philliphaydon on Friday June 24, 2022 @03:41AM (#31858796)

The ad blockers in iOS work fine. I don’t want browser bloat on my iPhone. And I don’t want to be forced to install shitty chrome cos devs are like “oh we can’t make it work in safari”.

Until chrome stops being the IE of the early 2000s I don’t want other browsers on iOS.

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by js4ever on Friday June 24, 2022 @03:45AM (#31858816)

Maybe it's because so many things are either not working (web rtc, push), intentionally broken (PWA), or not available at all on safari.

From my point of view, safari is the IE of modern times.

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by masswerk on Friday June 24, 2022 @04:38AM (#31859121)

> So many things intentionally broken (PWA)

Mind that PWA are, as it now, as Mozilla has pulled out, pretty much a Chromium-only thing.

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by resoluteteeth on Friday June 24, 2022 @06:58AM (#31860012)

Only on desktop

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by dmitriid on Friday June 24, 2022 @05:46AM (#31859592)

> intentionally broken (PWA)

People keep saying at as this is the truth.

1. There's no such thing as PWA. It's an umbrella term for nearly a dozen different standards

2. I think push notifications were the only ones missing from iOS Safari, so what exactly is "intentionally broken"?

[ Parent | on HN ]

Re:Apple is not defending browser engine choice by the_gipsy on Friday June 24, 2022 @09:12AM (#31861213)

Push notifications is THE most important feature preventing companies from building webapps instead of multiple native apps. This is not a coincidence, as native apps bring revenue and drives platform establishment. Push notifications have been available on Android for a decade.

As a user, this is really disappointing, especially when apple boast about "putting the user first" in matters of privacy. Native apps are much more privacy invasive than webapps.

[ Parent | on HN ]