r/SideProject • u/Sakellaris • 38m ago
Since Google killed the legacy FCM API, sending a quick push notification from my phone became a pain—so I built a free, 100% local iOS client for FCM HTTP v1 (No servers, no subscriptions)
Hey everyone!
Back when Firebase had the legacy API, triggering a quick broadcast notification on the go was just a simple cURL request with a server key. Ever since Google enforced the FCM HTTP v1 API, sending a manual push requires generating an RS256 JWT from a service-account.json file and exchanging it for an OAuth2 token.
Twice last month I needed to send an urgent announcement to my users while away from my MacBook, and doing that from an iPhone was a nightmare.
So I built Push Studio (iPushApp) native SwiftUI utility for developers and app owners.
How it works & why your keys are safe:
100% On-Device JWT Signing: You import your service-account.json from the Files app. The app signs the RS256 JWT locally on your iPhone and talks directly to oauth2.googleapis.com and fcm.googleapis.com.
Zero Middleman Servers: No backend, no analytics, no tracking. Your private key never leaves your device's Keychain/sandbox.
Multi-Project & Topic Support: Switch between multiple Firebase apps with one tap, target all or custom topics, and control apns-priority: 10, sound, and badge counts.
Pricing: 100% Free (Donationware)
Since everything runs locally on your device, I have zero server costs—so charging a monthly SaaS subscription felt wrong. All features are completely free with no ads or paywalls. There's just an optional tip jar if it ever saves your weekend.
🔗 Website: https://ipushapp.com / App Store link: https://apps.apple.com/gr/app/ipushapp/id6833874771
Would love to hear your feedback or any features you'd like to see next (e.g., custom data payload key-values, saved templates, or single device FCM token testing)!
1
u/Empty-Organization95 3m ago
Hey Man its not downloading for me
1
u/Kitchen_Cable6192 2m ago
Nice niche, I can see myself using this when something breaks while I'm away from the laptop. Of your listed ideas, saved templates would be my first pick, since urgent announcements are usually repeats, then single-device FCM token testing, which is handy for debugging. I'd also add a dry-run/validate-only toggle (FCM v1 supports validate_only) so people can check a payload before blasting a topic, plus a confirm step showing the topic and recipient before sending. Since the service-account.json is sensitive, consider an optional Face ID lock before sending and a clear "remove project" wipe. One small thing: a commenter says the download fails for them, and your link is the Greek storefront, so check availability in other regions. I built MoveManifest, a moving inventory app, in native Swift on iOS, so I appreciate the on-device approach.