798
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Mar 2024
798 points (99.0% liked)
Technology
35141 readers
202 users here now
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
founded 5 years ago
MODERATORS
Not to suggest you don't deserve to be paid more, but it feels like the issue would more be that the people paying for the site aren't instructing the people that develop it to make these accommodations.
Because I know plenty of devs that just straight up don't give a shit about accommodating low-end devices, regardless of what they're paid. It's like a point of pride almost.
Hell, that's the energy of the DontKillMyApp people: they just straight up think their app should use as many resources as it likes as long as it likes, and they shouldn't have to be considerate in development. Strain on device be damned.
I've seen some that straight up admit they don't even think the user should be able to kill an app process.
I know this isn't the main point of your comment, but DontKillMyApp is about much more than system resource management. It's about consistent behavior so that developers can program to a standard rather than a wild west of whatever a handset decides to do.
Either you write your app to accommodate every special case implementation of background execution requirements, or users get upset when the instant message isn't delivered and blame the app.
To make matters worse, many Chinese devices just kill everything in the background that's not on a hard coded whitelist. This is a failure of Android when it doesn't require consistent behavior. On these devices, applications that have a legitimate reason to run in the background just don't work correctly.
I think the situation is getting much better with recent Android versions.
Looking at Xiaomi's Miui here. My last phone was a Xiaomi one and it was great. It didn't take long for me to install LineageOS on it tho because Miui is horrible. It killed every app you had opened the second you switched to another one. Things like email verification codes were literally impossible to enter into an app because when you went into your mail app, copied the code and then went back into the app you wanted to enter it in, that app would have to start up again because it was already killed in the background.
Also, Miui itself used up like half my RAM without anything being opened and it was buggy as hell.
They do this because it pumps up those battery statistics but it harms the user experience which is much harder to test.