@S1m Thanks 🤗 It's still "staging" (where the link pointed to), not yet "production", though. Merge to the latter will follow later.

Asking the specialist: the pages on UnifiedPush (that would especially be this chapter: staging.izzyondroid.org/docs/d…) are fine as they are – or would you suggest any changes on them?

Push Notifications - IzzyOnDroid

alternatives to the proprietary Firebase Cloud Messaging

^{staging.izzyondroid.org}

The push notif page looks good too!

If it was only on me, maybe I would order that way: periodic > push > implement constant connection

If periodic works great for the app, no need to implement anything else.
Then, using the push service is a quick (and efficient) solution - which may be enough to get instant notifs.
And finally the constant connection is great to give a solution that works out of the box too

But that's just a detail, and maybe biased too :)

@S1m Done: codeberg.org/IzzyOnDroid/websi… – thanks for your suggestion! 🤗 This also matches the order of best preserving resources, so double win.

(and yes, we renamed the repository, as the original name was a little misleading: the site is not hosted at .codeberg.page)

PushNotifications: change order, as recommended by S1m

As [recommended by S1m](https://infosec.exchange/@S1m/115497543036862856), changing the order of variants. Quoting the essential part: > If periodic works great for the app, no need to implement anything else.

^Codeberg.org