Android Push Notification System That Doesn't Route Through Google's Servers

api service real project •• multiple requests

Five years after UnifiedPush launched, only about 20 apps support it and Android still has no native mechanism for custom notification servers. Users on HN and privacy forums explicitly wish Android supported specifying self-hosted notification servers. ntfy works well as infrastructure but the ecosystem adoption is stuck because app developers have no incentive to support an alternative protocol when Firebase is free and easy.

builder note

Don't build another push server. Build the adoption layer. A drop-in Android library that detects UnifiedPush distributors and falls back to Firebase transparently would let app developers support both with zero effort. The bottleneck is developer friction, not infrastructure.

landscape (3 existing solutions)

The infrastructure works (ntfy is solid). The protocol exists (UnifiedPush). What's missing is the adoption flywheel. App developers won't support UP without users demanding it, and users can't demand it without apps supporting it. A library that makes UP integration a one-line addition to Android apps could break this chicken-and-egg problem.

ntfy Excellent self-hosted notification server but requires manual setup and each app must explicitly integrate it

UnifiedPush Good protocol standard but only ~20 apps support it after 5 years. No mainstream app adoption.

NextPush Clever Nextcloud integration for self-hosted push but requires Nextcloud, limiting audience

sources (3)

other https://f-droid.org/2026/01/08/unifiedpush-5-years.html "Five years of UnifiedPush and growing ecosystem" 2026-01-08

hn https://news.ycombinator.com/item?id=46954380 "Wish Android supported specifying additional servers to poll" 2026-03-25

other https://eugenemdavis.net/archives/2026-02-23-offline-notific... "Offline notifications with ntfy and UnifiedPush" 2026-02-23

push-notificationsdegoogleandroidprivacyunifiedpush