Webhookify Mobile
Real-time AI webhook notifications companion app
Agency
Nep Tech Pal Pvt. Ltd.
Category
android
Type
android
Status
published
Key Features
Discover the powerful features that make this project stand out.
Push Notifications
Instant push notification for every incoming webhook event with payload preview.
Instant Push Notifications
Get notified the moment a webhook arrives at your endpoint — <1 second delivery via Firebase Cloud Messaging.
Event History
Browse and search your full webhook event history from mobile.
Multi-endpoint Support
Monitor multiple Webhookify endpoints simultaneously.
Multi-Endpoint Support
Monitor multiple Webhookify endpoints simultaneously — switch between projects and environments with one tap.
Event Details
View full request headers, body, and response details in a mobile-friendly layout.
Silent Mode
Configure quiet hours so you don't get woken up by non-critical webhook events.
From Challenge to Solution
Discover how we transformed challenges into innovative solutions.
The Challenge
The Challenge: Webhook Monitoring Doesn't Stop When You Close Your Laptop
The original Webhookify web app was excellent for active debugging sessions — sit at your laptop, inspect incoming webhooks in real time, fix your handler. But developers also run webhooks in production environments where events arrive 24/7, often at unexpected hours.
A Shopify store owner who built a custom order processing webhook wants to know immediately if Shopify starts sending events that fail. A developer who just deployed new webhook handler code at 5pm and left the office wants to know at 7pm if the first real event succeeded or failed. A team running a critical Stripe payment flow needs someone to be alerted if payment webhooks stop arriving — which could indicate a misconfigured endpoint after a deployment.
Browser-based WebSocket connections die when the tab is closed or the laptop sleeps. Email notifications are too slow and get buried in inboxes. The only reliable 24/7 alerting mechanism for mobile-attached humans is push notifications — which is exactly what PagerDuty, OpsGenie, and Grafana Alerts all rely on for production incident alerting.
The technical challenges of building the mobile companion:
- Low-latency push delivery: A push notification that arrives 5 minutes after the event is nearly useless for debugging. Sub-second delivery required careful Firebase FCM configuration and backend publishing architecture.
- Cross-platform with single codebase: Building and maintaining separate iOS and Android codebases for a companion app was not justifiable. Flutter was the only viable option for a small team targeting both platforms.
- Battery efficiency: Background processes that keep the app 'alive' drain batteries. Push notifications via FCM avoid this — the OS handles delivery without the app needing to run in the background.
Our Solution
Solution: Firebase FCM-Powered Companion App Built with Flutter
We built a minimal, fast Flutter app focused entirely on doing one thing perfectly: delivering webhook event notifications to a developer's phone within 1 second of the event arriving.
1. Firebase Cloud Messaging Integration
When a webhook arrives at a Webhookify endpoint, the backend simultaneously stores it in PostgreSQL, publishes it to the Redis WebSocket channel (for browser users), and publishes a push notification via Firebase Cloud Messaging to all devices registered to that endpoint. FCM handles the complexity of delivery routing across iOS APNs and Android FCM transport layers — delivering notifications even when the phone is in deep sleep mode. Average end-to-end latency from webhook arrival to phone notification is under 800ms.
2. Flutter for Cross-Platform Efficiency
Flutter's single codebase compiles to native iOS and Android with near-native performance. The app is intentionally minimal — a list of endpoints, a notification feed per endpoint, and a detail view for each event. No unnecessary features. No bloat. The philosophy mirrors what Robinhood did for stock trading — strip away everything that isn't essential to create an experience that's fast and frictionless.
3. Notification Customization
Developers can configure notification behavior per endpoint: all events, failures only (4xx/5xx response codes), specific event types (by payload field matching), or silent capture. This granular control is critical for high-volume endpoints — a developer monitoring a Stripe production endpoint that fires 500 webhooks per day doesn't want 500 push notifications, but does want to know about failures immediately.
Technology Stack
The powerful technologies used to bring this project to life.
Django
Backend
Firebase
DevOps
Dart
Mobile
Flutter
Mobile