9 ms·
> Since they broke VoIP background notifications, developers have no way to reliably perform silent delivery of information to device. Surely you mean fixed, n
by tomrod 6y ago
> Since they broke VoIP background notifications, developers have no way to reliably perform silent delivery of information to device.
Surely you mean fixed, not broken, as absolutely no one should be delivering information silently to a device they don't own.
- wizzwizz4 6y agoThe Apple philosophy is “give users zero agency” – and from that stance, yes, this is a fix. But I remember the days when a computer program was either a game, an extension of the user's will or the BIOS; by that philosophy, this should absolutely be possible. (But computers have been artificially complexified to the point that this isn't viable.)
- catlifeonmars 6y ago> an extension of the user’s will I quite like this particular viewpoint. I’m stealing this philosophy for the next time I am designing a CLI.
- Andrew_nenakhov 6y ago> as absolutely no one should be delivering information silently to a device they don't own. That's a very very very shallow thinking. You are advocating to break the internet. You are destroying every internet protocol that ever existed. They all silently deliver information to devices you likely don't own. Actually, we wouldn't need these dirty perversions with notifications if we had a proper background mode for apps. Like, you know, proper computers had for maybe 60 years.
- kitsunesoba 6y ago> Actually, we wouldn't need these dirty perversions with notifications if we had a proper background mode for apps. Like, you know, proper computers had for maybe 60 years. It's worth noting, however, that desktop and laptop PCs have a surplus of energy relative to mobile phones, so it's no big deal if there's a bunch of processes running in the background doing their thing… usually, anyway, because on PCs it's also shockingly common for background processes to misbehave and consume far more resources than they have any right to. Point in case, the daemon for my Logitech mouse will sometimes consume 120% CPU for no apparent reason for extended periods if I allow it to run. I could see an argument for extending background capabilities in iOS while also heavily also reducing their potential for bad behavior, though. For example, allowing apps to run in the background indefinitely, but on low power cores only with heavily capped CPU and memory consumption, along with a new Settings page that shows a list of persistent background processes and gives the user direct control over them.
- Andrew_nenakhov 6y agoI agree. User should decide, how he will use his battery power. If an app requires background running, it should be allowed to, with full control over data and battery used. That's all users need.
- TeMPOraL 6y agoOr, give people easy to use task manager that shows background processes, with big buttons labeled "kill", and "kill and keep down". Android doesn't have anything like it either. It's my number 1 complaint about smartphone experience ever since I bought my first one: the phone actively refuses to give user insight and control over what's running on their device.
- masom 6y ago> Android doesn't have anything like it either. Uh, it sure does through the applications section. You can see running services, which ones are taking battery, and stop/disable those as well.
- TeMPOraL 6y agoRecently, yes. Wasn't really the case for most of the lifetime of Android project, at least if my memory serves. Also even today, the application section is barely usable as it is. Contrast that with e.g. the task manager on Windows. It's not a pinnacle of UI, but it's easy to use, communicates necessary information, and gets the job done.
- grosswait 6y agoIn early android we had more insight and control over processes, but unfortunately we lost that supposedly due to abuse by apps (which seems highly likely)
- m-p-3 6y agoCan we stop making phones that are so thin that they struggle to be powered for a full day under moderate use?
- varenc 6y agoI’m with you. Story time: Years ago the Signal app would silently wake up in the background, upload 20MB+ of my contacts’ photos, and then shutdown and do it all over again every time I received a silent notification. Due to my membership in a few large groups this was very often. The result was gigabytes of cellar data usage in a week. Fortunately my experience was rare because I both had a lot of contacts with photos and I ran the desktop app. But it was infuriating to track down and it made me realize that silent wake ups were even possible on iOS. (Or used to be) I don’t know what the right balance is, but I think there should be some middle ground.
- Andrew_nenakhov 6y agoFun fact: Apple still allows signal, telegram, WhatsApp and few other high profile developers to use VoIP notifications without mandatory calling up VoiceKit. Because they can't work as smooth as users are used to they work with these new rules for notifications. So, no, nothing 'improved' in your Signal experience. At least, not yet. All developers are equal, but some are more equal than others.
- girvo 6y agoTo be honest, all developers have never been equal. At least not over the last 20 years that I’ve been paying attention.
- Andrew_nenakhov 6y agoOn deaktops, neither windows nor dlinux do not behave differently depending on developer's name. I see no reason why mobile devices should be any different. I wonder if there are grounds for anti-monopoly lawsuits.
- girvo 6y agoWindows absolutely does: it has a large collection of various hacks in place to detect specific applications to keep the running across newer versions of Windows. This is neat in a technical sense, but you’ve gotta be on Microsoft’s radar and worth it for them to put that sort of effort in for you. On top of that, the partner support you used to get from Microsoft if you were a developer they cared about was orders of magnitude more helpful and useful than what you’d get if you weren’t a preferred partner. Linux, you’re more correct I’d think.