this post was submitted on 20 Sep 2024
40 points (97.6% liked)
Open Source
31153 readers
274 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Does an alarm clock really need constant updates?
I don't get this fixation on constant updates. If an app works, and risks are trivial, then what updates are required?
This app doesn't have internet access, or storage access. I'd say risks are almost non-existant.
And even for apps with storage or network access, again, if the other layers of your security are in place, and an app has nominal risks, constant updates aren't necessarily required. Keeping in mind that changes bring errors too.
With new Android versions, permissions (sandboxing) and features change. Even a finished app needs development when new versions may break or alter the environment it expects.