Re:Integrate PWAs into Native Sharing UIs with Workbox
by chii on Thursday January 09, 2020 @06:17AM
(#22000228)
and i'd turn that off, since auto-update allows apps to remove features that i may want to keep by using the old version.
[ Parent
| on HN ]
Re:Integrate PWAs into Native Sharing UIs with Workbox
by me551ah on Thursday January 09, 2020 @06:48AM
(#22000393)
Auto-update allows app developers to add new features and fix bugs. And these are much more likely reasons for an update than removing a feature.
Re:Integrate PWAs into Native Sharing UIs with Workbox
by chii on Thursday January 09, 2020 @11:30PM
(#22008302)
therefore, i have to spend time to read the update changelog, and make a decision to update.
If it was possible to rollback, then i would be inclined to enable auto-update. Case in point - i used to really like the youtube app on android, but newer versions have usability issues, poor video playback on 2x speed (this didn't happen on an even older phone on the old version of the app). And i cannot get the old youtube app version, even if i try to factory reset (it's literally removed from the OS image when i updated android).
It's these reasons, plus more, that i distrust auto-updating.
Re:Integrate PWAs into Native Sharing UIs with Workbox
by Fnoord on Thursday January 09, 2020 @06:52AM
(#22000421)
Like old uTorrent? Riddled with security issues? You're better off with the latest version, or with security backports (these are generally FOSS apps, or vendor supported proprietary software). If an application removes features you wish to keep, and there's an interest in such in the community, a fork generally happens (with FOSS). For proprietary software, there's something like OldVersion.com or APK Mirror. Either way, when developers don't listen to their users, it is time to quit being a user.