371–380 of 428 posts
Earlier quoted context omitted.
yeah this is what author hints at with "Push as a battery problem". Apps are limited by default in what they can do in the background due to this, so most apps are in a suspended state not making network calls when you are not using them. To avoid the app having to keep running this stuff is delegated to OS which tells the app, "hey I have a push for you wake up and handle it!" You can send pushes locally but because…
What you're describing seems reasonable, but it doesn't align with what I quoted, unless I'm missing something, which I very well could be. Having apps sleep and a daemon wake them to handle notifications doesn't require all of the notifications coming from Apple.
The single persistent connection is just to receive pushes, there is still some daemon controlled by apple in charged of dispatching to correct app.
Earlier quoted context omitted.
It's a consequence of having platforms instead of protocols. Suppose you want delivery notifications for your packages. The seller, by contrast, wants to spam you with marketing. If getting the notifications requires you to install their app, they're going to shovel any spam into it that they can, and then they're writing the code that runs on your device. Whereas if the software on your device is controlled by you a…
> But for that to actually work you need the software running on the client to be under the control of the user independent of which device or service ... In other words, you need the user of the software to pay for it's development. Since that won't happen ...
For some android phone brands delivery reliability is like 40-50%. Some brands are better (reaching 80%, still bad) some very bad (usually the chinese brands, for some reason).
And the user has no say in this. They can't say: deliver every notification without classification. Or "allow this app to wakeup whenever it wants". Everything is babysat by the great overseer, even if you write the app yourself for yourself.
Have fun writing a telephony app that receives only 50% of calls. :D
The article's point about leading with the fact rather than the brand point is useful. The notification payload I'm designing already leads with the concrete numbers.
Earlier quoted context omitted.
When they exist at all. Many apps that provide important notifications (like delivery tracking, drop-off time etc) put them under the same category as marketing stuff. You can't have just the transactional tracking, you have to opt-in for the marketing notifications as well.
The ridesharing apps are the most annoying about this. Yes I want to be notified when my uber driver is almost here to pick me up. No, I don't want a notification about yet another sale.
I am just looking for a fucking taxi.
Are there any VCs looking to give away a few billion dollars to disrupt the ossified, wasteful, poor customer experience taxi app market?
While I have slight worries about what it means for users if Apple and Google notification services go down/censoring, I do appreciate the features that they provide to me as an end user. So many apps use annoying and questionable marketing notifications that I'd say I have about 70% of app notifications disabled globally (because the app itself does not allow disabling notifications / has no granular control) . Howe…
Am I understanding correctly that iOS notifications have to go over apns unless on the same local network as the HA server? I do appreciate that android makes this possible for ha and signal (and others) in all cases, it should be up to the user to choose centralizing the connection vs. slightly worse battery life.
The question is, will it work over Tailscale/WireGuard? I'd assume so, but I've honestly never tested local pushes as I simply haven't needed them :)
The fact that they do not do this reveals that phone makers are sort of market makers between app makers and customers, creating an environment which, in a certain sense, is a neutral ground between these two types of "users."
“ None of this bites evenly. The editing falls hardest on broadcast and promotional push; the notifications people actually want tend to pass through untouched or amplified” So … mission accomplished then? This is pretty much how I would like it to operate.
[1] I know a few people whose phones constantly beep and flash numerous times a minute, and when on, the top is completely unusable because any notification dismissed is immediately replaced, obscuring those upper buttons again. I don't understand how they tolerate it.
Earlier quoted context omitted.
The biggest problem are apps that do both. For example, I want Uber to notify me when my driver has arrived, but I don't want it to notify me when they have a special 10% discount on my next 5 rides. It's not straightforward to block one but not the other.
If I order an Uber, I already know it is coming. I was the person who ordered it. This is how taxis worked for decades before smartphones existed. You phoned for a taxi, then remained vaguely aware that it would arrive shortly. The question is whether a single “it has arrived” notification is worth the surrounding noise: “driver accepted”, “driver is nearby”, “rate your driver”, “here’s 10% off your next ride”, and s…