NotifyBridge

Product Introduction

1. Definition: NotifyBridge is a lightweight backend-as-a-service (BaaS) platform specifically designed for IoT (Internet of Things) and DIY hardware projects. It provides a REST API webhook endpoint that enables microcontrollers and single-board computers to send mobile push notifications without requiring complex client-side SDKs or server infrastructure.
2. Core Value Proposition: NotifyBridge exists to eliminate the significant development overhead associated with implementing mobile push notifications for embedded systems. Its core value is providing the "absolute easiest way" for makers, hobbyists, and developers to get real-time alerts from hardware like ESP32, Arduino, and Raspberry Pi to iOS and Android phones using a single HTTP POST request, bypassing the need for heavy Firebase configurations, platform-specific certificates (APNs/FCM), or custom backend servers.

Main Features

1. Simple REST API Webhook: The product's central feature is a single, well-documented HTTPS endpoint (POST https://notifybridge.mindeon.net/v1/messages/send). It accepts a JSON payload containing an API token, user key, device code, and message. This design minimizes firmware footprint, as developers only need a basic HTTP client library, freeing flash memory on resource-constrained microcontrollers for core application logic.
2. Dual-Mode Application Architecture: NotifyBridge operates through two distinct user interfaces within its mobile app: Studio Mode for creators and Subscriber Mode for end-users. Studio Mode allows makers to generate and manage API tokens, create project-specific device nodes with unique codes/QR codes, and audit notification logs. Subscriber Mode lets non-technical users scan a QR code to subscribe to alerts, configure quiet hours, and view a persistent notification history, enabling seamless sharing of hardware projects.
3. Device & Project Management: The platform provides organized project isolation. Makers can generate unique device_code identifiers for each hardware unit (e.g., "MS-ABCD-EF12"), which are decoupled from the master api_token. This allows for secure sharing of device-specific QR codes without exposing the primary API key, enabling scalable management of multiple IoT devices and projects from a single account.

Problems Solved

1. Pain Point: It solves the complexity and time cost of integrating mobile push notifications into DIY electronics and IoT prototypes. Traditionally, this requires setting up a server, managing Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) certificates, and implementing platform-specific SDKs—a process that is prohibitive for quick prototyping and hobbyist projects.
2. Target Audience: Primary users are IoT makers, smart home hobbyists, hardware tinkerers, and developers working with ESP32, Arduino, Raspberry Pi, or similar platforms. Secondary users are "subscribers" like family members, friends, or operational staff who need to receive alerts but lack technical expertise.
3. Use Cases: Essential for scenarios requiring immediate remote alerts from autonomous hardware: smart home security (open doors, motion sensors), environmental monitoring (greenhouse temperature/humidity, soil moisture), 3D printer status notifications, server/network monitoring (SSH login alerts, downtime), and remote sensor telemetry for low-battery warnings or system failures.

Unique Advantages

1. Differentiation: Unlike full-stack IoT platforms (e.g., Blynk, Adafruit IO) or generic notification services, NotifyBridge is hyper-focused on doing one thing well: sending simple push notifications. It avoids feature bloat, complex dashboards, and mandatory user accounts for subscribers. It contrasts with direct FCM/APNs implementation by removing all certificate management and backend coding.
2. Key Innovation: The "QR code subscription" model is a key innovation. It allows hardware creators to generate a shareable, device-specific QR code. Anyone can scan it with the NotifyBridge app to instantly start receiving pushes, achieving zero-friction user onboarding without accounts, emails, or passwords, which is unique for a notification service targeting hardware projects.

Frequently Asked Questions (FAQ)

1. How does NotifyBridge work with an Arduino without Wi-Fi? NotifyBridge requires the hardware device to have IP connectivity (via Wi-Fi, Ethernet, or cellular) to perform the HTTP POST request. For Arduinos without built-in networking, you must use an add-on shield (like an ESP8266 or Ethernet shield) to handle the network connection and webhook call.
2. Is NotifyBridge free to use for my IoT project? Yes, NotifyBridge offers a free tier that includes 3,000 push notifications per month, which is sufficient for many hobbyist and prototyping use cases. For higher volumes, the platform offers non-expiring notification credits via one-time purchases, unlike typical subscription models.
3. How secure is the NotifyBridge API for sending alerts? Security is based on API token and device code authentication. The api_token authenticates your project, while the device_code specifies the target. Communication occurs over HTTPS. The platform emphasizes a privacy-focused design with no tracking, data leaks, or ads, keeping payload data minimal and transient.
4. Can I send notifications to multiple phones from one ESP32? Yes. When you generate a device in Studio Mode, a unique device_code is created. Any number of people can subscribe to that specific device code by scanning its QR code in the Subscriber Mode of the app. A single API call from your ESP32 will then broadcast the alert to all subscribed mobile devices.
5. Where can I find example code for ESP32 or Raspberry Pi to use NotifyBridge? NotifyBridge maintains an open-source repository on GitHub (github.com/mindeon/NotifyBridge-Devices) containing ready-to-use firmware examples and code snippets for popular platforms like ESP32 (Arduino framework), Arduino, and Python (for Raspberry Pi), providing a quick-start for integration.