Hacker News Reader

No one meads “scare screens”.

I’m. It sure what I think about this yet, but I’m pretty sure I’m going to land on “allowing less privacy aware browsers to run web “apps” with heightened privileges seems like a recipe for disaster.

Maybe in the long term ther is a way to do it well. But for now I’m not sure.

View on HN

Every app on iOS is sandboxed and the damage they can do is very limited. There's risks involved in opening up to third-party apps, and PWAs are only marginally more dangerous. Non-WebKit based browsers don't even exist today, this is not a real problem and won't be for some time.

The obvious solution for now is to enable WebKit PWAs and turn on PWAs for other as-yet uninvented custom browsers as they release, testing for privacy as they get released.

I think the pwa arch might be different. Running in the same app (safari) with multiple open screens, but with soft sandboxing like tabs have.

They would need new apis and architecture around PWA to support this for any browser I think.

Also, they are not allowed to have Safari-only OS features anymore due to DMA so allowing PWAs only in safari would be against the law

Reply on news.ycombinator.com