An introduction into push notifications, why we want it on Linux, and an overview over the current options.

What is it?

push refers to the service pushing notifications to the client immediately when they available.

pull refers to the client regularly pulling the service for newly available notifications.

Why do we want it?

As communication is a very important feature for (Linux) phones, instant notifications for (web) calls and messages in your favorite apps is usually desired.

What is the problem?

Technically, push notifications are usually realized by an open TCP connection. As they time out at some point, they need to be refreshed regularly. When every app creates their own connection, the device wakes up very often and consumes a lot of energy. This renders mobile devices with very limited battery pretty much unusable.

A much more energy saving way to handle this is a single connection which all applications can use for notifications. This allows the device to save a lot of energy as it can stay in sleep mode most of the time.

In the remainder of the post, we will refer to this single common push service.

What is the current state?

UnifiedPush

An open standard, UnifiedPush, is currently evolving. It contains different distributors (for example ntfy.sh and NextPush on NextCloud) and a lot of Android apps are already using it.

On Linux, the situation does not look as good:

Not much really happened since then.

WebPush

As one needs internet to communicate anyways, using the mobile websites seems like a viable option. With the Progressive Web Apps standard and the Push API standard, all necessary building blocks are in place.

Ubuntu Touch (UBports)

Ubuntu Touch Clickable apps support push notifications. Unfortunately only a very tiny fraction of apps is available in Ubuntu Touch as it is missing Flatpak support (the team is open to add Flatpak, if someone comes up with a good enough implementation, though).

Where do we go from here?

How can we drive this forward as a community? Feedback, ideas and comments are welcome - please reply on Mastodon!