[GH-ISSUE #825] [Feature Request] Support multi-user awareness in ntfy-android #581

New issue

Open

opened 2026-05-07 00:25:35 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:25:35 +02:00

Owner

Originally created by @OneDeuxTriSeiGo on GitHub (Jul 28, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/825

💡 Idea

Android provides a mechanism for marking a service, receiver, or provider to only run on user 0 and for all requests to that service, receiver, or provider to be routed to the one on user 0 rather than within the current user [1].

If ntfy was to take advantage of this, users who segregate their apps between user profiles (as is common with GrapheneOS for example) would be able to still keep one ntfy distributor locally and one connection back to the ntfy server rather than requiring one instance per user.

💻 Target components

Android App.

I may be able to eventually try writing up a PR implementing this functionality but it'll likely be a decent while before I do so.

https://source.android.com/docs/devices/admin/multiuser-apps

Originally created by @OneDeuxTriSeiGo on GitHub (Jul 28, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/825  :bulb: **Idea**  Android provides a mechanism for marking a service, receiver, or provider to only run on user 0 and for all requests to that service, receiver, or provider to be routed to the one on user 0 rather than within the current user [1]. If ntfy was to take advantage of this, users who segregate their apps between user profiles (as is common with GrapheneOS for example) would be able to still keep one ntfy distributor locally and one connection back to the ntfy server rather than requiring one instance per user. :computer: **Target components**   Android App. ---- I may be able to eventually try writing up a PR implementing this functionality but it'll likely be a decent while before I do so. 1. https://source.android.com/docs/devices/admin/multiuser-apps