6 ms·

Why would they belong in a platform-specific app but not in a standard-based web app? Because Apple can't get 30% out of it?

by agust 2y ago

L3viathan 2y ago
Because there's typically at least a minimum of safety checks before an app can go into the app store, whereas a website can do whatever it wants (and can).
- boweruk 2y ago
  Almost all of these APIs still require a user to approve their use in the browser for a given origin.
  - tgv 2y ago
    Next next next finish
wil421 2y ago
Because some of us lived through pop up hell and Microsoft’s lack of security as it relates to web browsers in the late 90s/2000s. Web apps should be as restricted as possible. Rich companies such as Epic, complaining about a 30% cut can cry me a river. Lock iOS down as much as possible and restrict/sandbox the web. iOS is the only internet connected computer I’ve had that didn’t get malware and/or a virus at some point. Unless you consider an Xbox/PlayStation a computer. https://medium.com/online-io-blockchain-technologies/the-evolution-of-internet-ads-the-rise-of-pop-ups-179fd7e5a3bb https://medium.com/online-io-blockchain-technologies/the-evo...
madeofpalk 2y ago
The web lacks intentionality that installed 'native' apps have. You search for a recipie and land on a random blog, executing untrustable code from a countless number of third parties, clicking "I agree" on that modal that says "LiveLaughLove blog and out 1382 partners value your privacy". Native apps have a much higher level of friction at multiple points that helps balance the higher level of access they get.
- agust 2y ago
  The APIs coming with a security or privacy risk are always gated by a permission prompt on the web (contrary to platform-specific apps). Safari has gone even further by only allowing some of them (e.g. Push notifications) for installed web apps. These APIs are also much more restricted than their proprietary-ecosystem equivalent. Overall, web apps having access to these features in Chrome are an order of magnitude safer than platform-specific apps.
isodev 2y ago
And would you build for all browsers or just your favourite "standard"? It doesn't matter how many layers we add, it will always amount to the same challenge when people use different systems. That's why it's generally better to target a solution with the least amount of abstractions to depend on. Build a native app, you depend on the OS. Build a PWA, you depend on the browser and the OS. As for the 30%, How long do you think it would be before Chrome decides to monetize their web apps? The Manifest v3 story was a hint, maybe not everyone got the memo.

Why would they belong in a platform-specific app but not in a standard-based web app? Because Apple can't get 30% out of it?

by agust 2y ago

Why would they belong in a platform-specific app but not in a standard-based web app? Because Apple can't get 30% out of it?

L3viathan 2y ago

Because there's typically at least a minimum of safety checks before an app can go into the app store, whereas a website can do whatever it wants (and can).

boweruk 2y ago
Almost all of these APIs still require a user to approve their use in the browser for a given origin.
- tgv 2y ago
  Next next next finish

wil421 2y ago

Because some of us lived through pop up hell and Microsoft’s lack of security as it relates to web browsers in the late 90s/2000s. Web apps should be as restricted as possible. Rich companies such as Epic, complaining about a 30% cut can cry me a river. Lock iOS down as much as possible and restrict/sandbox the web. iOS is the only internet connected computer I’ve had that didn’t get malware and/or a virus at some point. Unless you consider an Xbox/PlayStation a computer. https://medium.com/online-io-blockchain-technologies/the-evolution-of-internet-ads-the-rise-of-pop-ups-179fd7e5a3bb https://medium.com/online-io-blockchain-technologies/the-evo...

madeofpalk 2y ago

The web lacks intentionality that installed 'native' apps have. You search for a recipie and land on a random blog, executing untrustable code from a countless number of third parties, clicking "I agree" on that modal that says "LiveLaughLove blog and out 1382 partners value your privacy". Native apps have a much higher level of friction at multiple points that helps balance the higher level of access they get.

agust 2y ago
The APIs coming with a security or privacy risk are always gated by a permission prompt on the web (contrary to platform-specific apps). Safari has gone even further by only allowing some of them (e.g. Push notifications) for installed web apps. These APIs are also much more restricted than their proprietary-ecosystem equivalent. Overall, web apps having access to these features in Chrome are an order of magnitude safer than platform-specific apps.

isodev 2y ago

And would you build for all browsers or just your favourite "standard"? It doesn't matter how many layers we add, it will always amount to the same challenge when people use different systems. That's why it's generally better to target a solution with the least amount of abstractions to depend on. Build a native app, you depend on the OS. Build a PWA, you depend on the browser and the OS. As for the 30%, How long do you think it would be before Chrome decides to monetize their web apps? The Manifest v3 story was a hint, maybe not everyone got the memo.