sjstulga

@sabreW4K3 @boredsquirrel What do you use instead?

@ICastFist
Yes, however the EU enacted new regulations to put a stop to that practice, so that Apple will be required to allow other browsers on their platform.

Disabling PWAs is how Apple has chosen to retaliate against those new regulations.

@bloodfart

I could be wrong, but I think you are simply mistaken because there should be absolutely no possible way for the PWA to install a browser engine onto your device? The user can first install the browsers of their choice, separately, and then install PWAs using that browser.

That would be a huge concern and really contradict the entire point and purpose behind PWAs as I understand them… I’ve been searching but can’t find anything like what you say. I’d love to see your source

@bloodfart

I’ve read through your comments and it seems like your primary concerns are:

1. you believe users “trust” apps and “distrust” websites, and PWAs trick a user into a false sense of trust, and the user’s personal feelings are somehow relevant to the security of the software

2. you believe that it is possible to bundle a browser engine, customized by the PWA developer, that will be installed with the PWA and the PWA will run inside of

I’m going to need a source on 2

@bloodfart @kilgore_trout

“WebKit’s sandbox profile on iOS is orders of magnitude more stringent than the sandbox for native iOS apps.” 😁 direct quote from Apple

https://assets.publishing.service.gov.uk/media/62277271d3bf7f158779fe39/Apple_11.3.22.pdf

@bloodfart @kilgore_trout
“when someone goes to a website, their guard is up. When they click on an app their guard is down.”

???

@bloodfart @kilgore_trout
“How is a piece of software that runs in the browser instead of directly in the os… less secure than a website?”

The question answered itself 😂