
PingBox
End-to-end notification system — external services POST to a FastAPI backend, which dispatches push notifications via FCM to an Android client. A local rule engine on the device routes taps directly to the target app, URL, deep-link, or activity, bypassing the PingBox UI entirely. Backend runs on Docker Compose with PostgreSQL, Redis rate limiting, and JWT + API key auth.
Gallery
Notes
Full-stack notification relay from external services to Android devices with smart routing.
Architecture
Three-tier: external sources → FastAPI backend (PostgreSQL, Redis, JWT auth) → Firebase Cloud Messaging → Kotlin/Jetpack Compose Android client.
Highlights
- Tapping a notification opens the target app directly, not PingBox — supports URLs, deep-links, package names, component names, and intent URIs
- Rule engine with wildcard tag matching and priority ranking
- Persistent local history via Room database
- Backend containerized with Docker Compose (PostgreSQL 16, Redis 7, Nginx)
- SHA-256 API key hashing, bcrypt passwords, Pydantic input validation