Hacker News Reader

Comment by autoexec | Hacker News Reader

Apps can't just send notifications? If I had a mail client installed, couldn't the app just periodically connect to my mail server using my internet connection, see new mail was available, and then pop up a notification so I'd know?

That seems much more secure than having a third party collecting my passwords so they can connect to my mail server from their network using my password just to see if any new mail is there, read the messages, then send a notification to my phone to let me know about them.

I'm perfectly happy to trust Thunderbird enough to configure it to check my mailbox, but I wouldn't feel as comfortable handing my login information directly to Mozilla so that they can log into my mailbox whenever they feel like it. I guess Mozilla could push an update that collects my stored login credentials and do that anyway, but if they did I think there would be a lot of folks who'd protest.

View on HN

> If I had a mail client installed, couldn't the app just periodically connect to my mail server, see new mail was available, and then pop up a notification so I'd know?

Desktop mail clients do. Phone mail clients can’t, so you either check on a server, or don’t get notifications on time.

Mobile platforms seem a bit broken. Timer/alarm apps seem to be able to take actions and notify on a regular schedule, it is specifically scheduled network activity that's restricted?

yes mobile OSes will delay and group background activity especially if it involves network access. But we're talking minutes, not hours of delay... Some phones are very aggressive and the app will need to show a persistent notification to keep background polling working, though.

I've never used a mobile client that used a third party to monitor a mailbox, they all do polling as you suggest. I'm not sure the man in the middle approach it's as common as OP is implying here (for non-first party clients).

It's debatable whether those are considered push notifications. On one hand, it's pushing the notifications from one program on the device to another. On the other hand, it isn't pushing remotely from a server to the device.

This reminded me of Pointcast Networks. Ah, the 90s. :) https://en.wikipedia.org/wiki/PointCast https://www.youtube.com/watch?v=qCqwB6sruIQ

Those are not push notifications, but the push part isn’t the goal, notifications are. The point here is you simply can’t poll on a reliable schedule on mobile devices, so push is the way.

Mail polling doesn't require accuracy. The OS won't delay your polling timer more than 10 minutes in the most aggressive cases, which is perfectly fine.

I'm sure the third party you share your email just to get push notifications with isn't monitoring your mailbox to the second either...

They probably are. If they connect via IMAP, they can use the IDLE and/or the NOTIFICATION command to get notifications of new messages arriving. This is generally as prompt as it gets; the server doesn’t wait much before sending the notifications.

Given the shoddy "battery saving" behavior of various Android vendors, probably not. I have a phone collecting dust that was so bad in this regard that no matter of tuning and disabling battery optimizations would get notifications to work in all apps.

>Apps can't just send notifications?

They can but consider this: How would they know to send them?

If you are adding a provider only locally there's no way for the app to know to generate a notification if it doesn't have an IMAP idle connection open constantly or scheduled polling. If the app is shipped by the email provider (like gmail app for ios using a gmail account) they can send pushes without leaving connection open or polling.

The point of having your details with the app developer is that their servers will remain always connected to your email provierr and generate pushes that will go over Apple or Google's push network.

I can see it making sense if you're already using the mail servers of the company that made the app (gmail for example) since they already have unrestricted access to your login info and mailbox anyway.

I guess otherwise I'd rather it be my phone regularly polling my mail server over my connection than a third party regularly polling it using theirs. I can see it being a popular option for folks on expensive/very limited data plans though. It doesn't take a ton of bandwidth to poll a mail server, but checking every 5-10 minutes it could add up.

the OS won't let you do that reliably unless the user also keeps opening the app. background processing is heavily limited for the right reasons.

iOS does that, maybe, but Android doesn’t. The mail client I use on my Android phone notifies me in a timely fashion when new mail arrives, often in less than a second. It just uses IMAP’s IDLE command to wait for new mail. If the connection drops it can just open a new one.

"Android doesn't"

Does it occur to you that there are so many different variants of Android and they all do their own thing regarding background processes? It is so complicated that you can find websites like this https://dontkillmyapp.com/

That’s a fair point; I hadn’t realized how bad certain brands could be. The last Samsung phone I owned was from about 10 years ago, and it worked just fine. I replaced it with a Google Pixel last year when the 3G networks started getting shut down, and it works great too.

Reply on news.ycombinator.com