Firestore notification scaling for FCM

Problem Context

Developers using Firestore + FCM for push notifications face a scalability dilemma. They need to store notifications efficiently for thousands of users, but Firestore’s 1MB document limit and write costs make it hard to scale. Their current approaches either require too many writes (per-user docs) or risk hitting document limits (array-based storage).

Pain Points

Users struggle with Firestore’s 1MB limit when storing large arrays of notification recipients, forcing them to either split data manually (error-prone) or accept failed writes. Per-user documents create excessive write costs, making the system unsustainable as their user base grows. Both approaches break at scale, leading to lost notifications and frustrated users.

Impact

Failed notifications mean lost user engagement, abandoned apps, and direct revenue loss. Developers waste hours debugging Firestore schema issues or paying for unnecessary writes. Startups risk scaling failures that could kill their product’s growth. The problem gets worse as user counts increase, making it a critical bottleneck for mobile apps.

Urgency

This is a mission-critical issue for any app relying on notifications. A single failed write can break the entire notification system, and manual fixes don’t scale. Developers can’t ignore it because their users expect reliable notifications—especially for news, alerts, or marketing messages that drive retention and revenue.

Target Audience

Mobile app developers using Firestore + FCM for push notifications, especially those with growing user bases (1K–100K+). This includes indie developers, startups, and small teams building consumer apps, SaaS products, or internal tools that rely on real-time updates. Any team that needs to send notifications to thousands of users will face this problem.

Solution Approach

A serverless middleware layer that automatically optimizes Firestore notification storage for FCM. It dynamically splits notifications into sub-collections to bypass the 1MB limit, batches FCM sends to reduce costs, and scales with the user base without manual intervention. Users integrate it via a simple SDK or API, and it handles the heavy lifting behind the scenes.

Key Features

1. Smart Batching for FCM: Groups notifications by recipient to minimize FCM API calls, reducing costs and improving delivery speed.
2. Auto-Scaling Schema: Adjusts storage structure as the user base grows, so developers don’t need to rewrite their Firestore schema.
3. Usage-Based Pricing: Charges per active user (e.g., $
4. 01/user/month), making it cost-effective for startups and scalable for growing apps.

User Experience

Developers integrate the middleware via a 5-minute SDK setup or API call. They continue using Firestore and FCM as usual, but notifications are now stored and delivered efficiently at scale. The tool handles all optimizations in the background, so they don’t need to think about schema limits or batching. They see fewer failed writes, lower costs, and reliable notifications—even as their user base grows.

Differentiation

Unlike manual workarounds (separate docs or arrays), this solution automatically scales without breaking. It’s cheaper than over-provisioning Firestore writes and more reliable than native Firestore + FCM setups. The proprietary schema optimization logic ensures it works seamlessly with existing apps, while usage-based pricing makes it accessible for startups.

Scalability

The middleware grows with the user base. For 1K users, it might use a simple sub-collection structure; for 100K+, it dynamically adjusts to distribute load. Pricing scales too (e.g., $20/mo for 1K users, $100/mo for 10K), so costs stay predictable. Users never need to migrate or rewrite their Firestore schema—it just works as they grow.

Expected Impact

Developers save hours of debugging time and avoid costly Firestore write limits. Apps see fewer failed notifications, leading to happier users and better retention. Startups can scale confidently without worrying about notification system breakdowns. The solution pays for itself by reducing FCM costs and preventing revenue loss from broken notifications.