4 ms·
> progressive web apps (PWA) as packages that can be shipped via repositories Aah, wasn't aware this is possible now, thats cool. But raises the question of h
by openrisk 2y ago
> progressive web apps (PWA) as packages that can be shipped via repositories
Aah, wasn't aware this is possible now, thats cool.
But raises the question of how exactly to check and communicate to users what data are being collected.
With a PWA almost all of the code runs on the server. Even if that server is based on an open source project, there is no guarantee that there has been no modification (eg a plugin) that changes behavior.
Not sure there is a way to reconcile these demands in an automated way that doesnt ultimately fall back on trusting the developer.
- black_puppydog 2y agoI thought that the whole point of PWAs is that they can nearly all the logic and storage on-device?
- openrisk 2y agoIts very flexible, both ends of the spectrum are within the specification. One could force the "on-device only" by requiring no data exchange with the outside world but thats quite limiting too (and not trivial to check at upload time).
- idle_zealot 2y agoSo... like a normal app? Nothing stops native apps from mostly running on the server. In fact, many do. Social media, banking, heck, do maps apps even do offline routing, or do they just query a server for that usually?
- openrisk 2y agoyeah, its a very blurry line (like the overall separation and balance between client and server roles anyway).
- zo1 2y agoThere is way too much marketing and "evangelism" around PWAs that it's hard to pin down exactly what they are or what they want the term to encompass.
- daniel-s 2y agoIs that as big a problem for PWAs? These apps are still running in the browser so never have access to many parts of a phone a native app would.