News for hackers. Stuff that matters.

A comment on Apple declined to implement 16 Web APIs in Safari due to privacy concerns. Parent comment

Re:Apple declined to implement 16 Web APIs in Safari due to ... by osrec on Monday June 29, 2020 @08:19PM (#23685118)
It's even easier to block a web app - just don't visit its web address.

A native app sits on your device, executing all kinds of code, sometimes without your knowledge. With PWAs, the code is more or less open source - all the JS is there for you to inspect - even after obfuscation, you can see the network requests being made in the dev tools of any browser.

[ Parent | on HN ]
Re:Apple declined to implement 16 Web APIs in Safari due to ... by breakfastduck on Tuesday June 30, 2020 @04:22PM (#23694358)
I appreciate that and maybe didn't make my point as best as I could.

My point was essentially that you can run a native app without internet access most of the time (and can easily block the app making calls out by switching the internet off or blocking the calls its making) but a web app you have absolutely no control over, you just have to not use it.

[ Parent | on HN ]
Re:Apple declined to implement 16 Web APIs in Safari due to ... by osrec on Tuesday June 30, 2020 @05:11PM (#23694830)
That's not true with PWAs. You can have PWAs that operate offline. The problem is that not enough web developers know how to build good offline-only PWAs. But trust me, they're coming!
[ Parent | on HN ]