Alternatives to Firebase Cloud Messaging logo

Alternatives to Firebase Cloud Messaging

OneSignal, Google Cloud Messaging, Firebase, Amazon SNS, and Kafka are the most popular alternatives and competitors to Firebase Cloud Messaging.
235
320
+ 1
15

What is Firebase Cloud Messaging and what are its top alternatives?

It is a cross-platform messaging solution that lets you reliably deliver messages at no cost. You can notify a client app that new email or other data is available to sync. You can send notification messages to drive user re-engagement and retention. For use cases such as instant messaging, a message can transfer a payload of up to 4KB to a client app.
Firebase Cloud Messaging is a tool in the Mobile Push Messaging category of a tech stack.

Top Alternatives to Firebase Cloud Messaging

  • OneSignal
    OneSignal

    OneSignal is a high volume push notification service for websites and mobile applications. OneSignal supports all major native and mobile platforms by providing dedicated SDKs for each platform, a RESTful server API, and a dashboard. ...

  • Google Cloud Messaging
    Google Cloud Messaging

    Google Cloud Messaging (GCM) is a free service that enables developers to send messages between servers and client apps. This includes downstream messages from servers to client apps, and upstream messages from client apps to servers. ...

  • Firebase
    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Amazon SNS
    Amazon SNS

    Amazon Simple Notification Service makes it simple and cost-effective to push to mobile devices such as iPhone, iPad, Android, Kindle Fire, and internet connected smart devices, as well as pushing to other distributed services. Besides pushing cloud notifications directly to mobile devices, SNS can also deliver notifications by SMS text message or email, to Simple Queue Service (SQS) queues, or to any HTTP endpoint. ...

  • Kafka
    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • SignalR
    SignalR

    SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization. ...

  • Pusher
    Pusher

    Pusher is the category leader in delightful APIs for app developers building communication and collaboration features. ...

  • MQTT
    MQTT

    It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium. ...

Firebase Cloud Messaging alternatives & related posts

OneSignal logo

OneSignal

302
420
122
A high volume push notification service for websites and mobile applications
302
420
+ 1
122
PROS OF ONESIGNAL
  • 28
    Free of cost
  • 22
    More parametrable
  • 16
    Simple and Easy To Use. Well Documented :)
  • 13
    Device to device
  • 11
    Simple
  • 9
    Great support
  • 8
    Many Platforms
  • 8
    Free
  • 4
    Flexibility in working with web, android and iOS
  • 3
    Phonegap / Cordova / Ionic starters
CONS OF ONESIGNAL
    Be the first to leave a con

    related OneSignal posts

    Lukas Bergamo
    CEO & Founder at ¹OnePlace · | 7 upvotes · 298.8K views
    Shared insights
    on
    OneSignalOneSignalFirebaseFirebase
    at

    At the beginning of the ¹OnePlace project, our team needed to decide which service to use to send bulk notifications to all users quickly and consistently. We tested some services without success and as we already used firebase we decided to implement in the beginning using Notifications by Firebase. We're having trouble updating the user's token to see if it has removed the app or not. This brought a working overhead and we were not sure if the notification had arrived at the destination. Today we use OneSignal, which did not bring reliability to the submitted notifications, nor do we need to bother with manual token updates. We ship approximately 500 thousand notifications with 100% delivery!

    OneSignal Firebase

    See more
    Yasmine de Aranda
    Chief Growth Officer at Huddol · | 6 upvotes · 131.5K views

    Hi there, we are a seed-stage startup in the personal development space. I am looking at building the marketing stack tool to have an accurate view of the user experience from acquisition through to adoption and retention for our upcoming React Native Mobile app. We qualify for the startup program of Segment and Mixpanel, which seems like a good option to get rolling and scale for free to learn how our current 60K free members will interact in the new subscription-based platform. I was considering AppsFlyer for attribution, and I am now looking at an affordable yet scalable Mobile Marketing tool vs. building in-house. Braze looks great, so does Leanplum, but the price points are 30K to start, which we can't do. I looked at OneSignal, but it doesn't have user flow visualization. I am now looking into Urban Airship and Iterable. Any advice would be much appreciated!

    See more
    Google Cloud Messaging logo

    Google Cloud Messaging

    85
    217
    18
    Simple and reliable messaging to reach over a billion devices.
    85
    217
    + 1
    18
    PROS OF GOOGLE CLOUD MESSAGING
    • 8
      Free
    • 5
      Scalable
    • 3
      Easy setup
    • 1
      Easy iOS setup
    • 1
      IOS Support
    CONS OF GOOGLE CLOUD MESSAGING
    • 1
      Reliability

    related Google Cloud Messaging posts

    Firebase logo

    Firebase

    31.7K
    27.1K
    1.9K
    The Realtime App Platform
    31.7K
    27.1K
    + 1
    1.9K
    PROS OF FIREBASE
    • 367
      Realtime backend made easy
    • 268
      Fast and responsive
    • 239
      Easy setup
    • 212
      Real-time
    • 188
      JSON
    • 132
      Free
    • 126
      Backed by google
    • 82
      Angular adaptor
    • 67
      Reliable
    • 35
      Great customer support
    • 30
      Great documentation
    • 25
      Real-time synchronization
    • 21
      Mobile friendly
    • 18
      Rapid prototyping
    • 14
      Great security
    • 12
      Automatic scaling
    • 11
      Freakingly awesome
    • 8
      Chat
    • 8
      Angularfire is an amazing addition!
    • 8
      Super fast development
    • 6
      Ios adaptor
    • 6
      Firebase hosting
    • 6
      Awesome next-gen backend
    • 6
      Built in user auth/oauth
    • 4
      Speed of light
    • 4
      Very easy to use
    • 3
      Brilliant for startups
    • 3
      Great
    • 3
      It's made development super fast
    • 2
      Low battery consumption
    • 2
      Free hosting
    • 2
      Cloud functions
    • 2
      Push notification
    • 2
      JS Offline and Sync suport
    • 2
      Free authentication solution
    • 2
      The concurrent updates create a great experience
    • 2
      I can quickly create static web apps with no backend
    • 2
      Great all-round functionality
    • 1
      Easy Reactjs integration
    • 1
      Easy to use
    • 1
      Free SSL
    • 1
      CDN & cache out of the box
    • 1
      Faster workflow
    • 1
      Google's support
    • 1
      .net
    • 1
      Serverless
    • 1
      Good Free Limits
    • 1
      Large
    CONS OF FIREBASE
    • 31
      Can become expensive
    • 15
      No open source, you depend on external company
    • 15
      Scalability is not infinite
    • 9
      Not Flexible Enough
    • 6
      Cant filter queries
    • 3
      No Relational Data
    • 3
      Very unstable server
    • 2
      No offline sync
    • 2
      Too many errors

    related Firebase posts

    Stephen Gheysens
    Senior Solutions Engineer at Twilio · | 14 upvotes · 615.9K views

    Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

    My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

    See more
    Tassanai Singprom

    This is my stack in Application & Data

    JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

    My Utilities Tools

    Google Analytics Postman Elasticsearch

    My Devops Tools

    Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

    My Business Tools

    Slack

    See more
    Amazon SNS logo

    Amazon SNS

    1.3K
    1.1K
    17
    Fully managed push messaging service
    1.3K
    1.1K
    + 1
    17
    PROS OF AMAZON SNS
    • 11
      Low cost
    • 6
      Supports multi subscribers
    CONS OF AMAZON SNS
      Be the first to leave a con

      related Amazon SNS posts

      Cyril Duchon-Doris

      We decided to use AWS Lambda for several serverless tasks such as

      • Managing AWS backups
      • Processing emails received on Amazon SES and stored to Amazon S3 and notified via Amazon SNS, so as to push a message on our Redis so our Sidekiq Rails workers can process inbound emails
      • Pushing some relevant Amazon CloudWatch metrics and alarms to Slack
      See more
      Manish Mishra
      Lead Consultant at Knoldus Software LLp · | 6 upvotes · 75.1K views
      Shared insights
      on
      Amazon PinpointAmazon PinpointAmazon SNSAmazon SNS

      Instead of Amazon SNS, which is currently being used to send outbound push notification and including SMS, we want to build the 2 Way SMS using Amazon Pinpoint. Just want to know about Pinpoint and any outstanding issues if we drop SNS since it does not support 2 Way and use Pinpoint for both incoming and outgoing flow.

      See more
      Kafka logo

      Kafka

      17.8K
      16.9K
      587
      Distributed, fault tolerant, high throughput pub-sub messaging system
      17.8K
      16.9K
      + 1
      587
      PROS OF KAFKA
      • 125
        High-throughput
      • 118
        Distributed
      • 88
        Scalable
      • 82
        High-Performance
      • 65
        Durable
      • 37
        Publish-Subscribe
      • 19
        Simple-to-use
      • 16
        Open source
      • 11
        Written in Scala and java. Runs on JVM
      • 7
        Message broker + Streaming system
      • 4
        Avro schema integration
      • 4
        KSQL
      • 3
        Robust
      • 2
        Suport Multiple clients
      • 2
        Partioned, replayable log
      • 1
        Flexible
      • 1
        Extremely good parallelism constructs
      • 1
        Simple publisher / multi-subscriber model
      • 1
        Fun
      CONS OF KAFKA
      • 29
        Non-Java clients are second-class citizens
      • 27
        Needs Zookeeper
      • 7
        Operational difficulties
      • 2
        Terrible Packaging

      related Kafka posts

      Eric Colson
      Chief Algorithms Officer at Stitch Fix · | 21 upvotes · 2.3M views

      The algorithms and data infrastructure at Stitch Fix is housed in #AWS. Data acquisition is split between events flowing through Kafka, and periodic snapshots of PostgreSQL DBs. We store data in an Amazon S3 based data warehouse. Apache Spark on Yarn is our tool of choice for data movement and #ETL. Because our storage layer (s3) is decoupled from our processing layer, we are able to scale our compute environment very elastically. We have several semi-permanent, autoscaling Yarn clusters running to serve our data processing needs. While the bulk of our compute infrastructure is dedicated to algorithmic processing, we also implemented Presto for adhoc queries and dashboards.

      Beyond data movement and ETL, most #ML centric jobs (e.g. model training and execution) run in a similarly elastic environment as containers running Python and R code on Amazon EC2 Container Service clusters. The execution of batch jobs on top of ECS is managed by Flotilla, a service we built in house and open sourced (see https://github.com/stitchfix/flotilla-os).

      At Stitch Fix, algorithmic integrations are pervasive across the business. We have dozens of data products actively integrated systems. That requires serving layer that is robust, agile, flexible, and allows for self-service. Models produced on Flotilla are packaged for deployment in production using Khan, another framework we've developed internally. Khan provides our data scientists the ability to quickly productionize those models they've developed with open source frameworks in Python 3 (e.g. PyTorch, sklearn), by automatically packaging them as Docker containers and deploying to Amazon ECS. This provides our data scientist a one-click method of getting from their algorithms to production. We then integrate those deployments into a service mesh, which allows us to A/B test various implementations in our product.

      For more info:

      #DataScience #DataStack #Data

      See more
      John Kodumal

      As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

      We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

      See more
      SignalR logo

      SignalR

      446
      1.1K
      122
      A new library for ASP.NET developers that makes developing real-time web functionality easy.
      446
      1.1K
      + 1
      122
      PROS OF SIGNALR
      • 28
        Supports .NET server
      • 19
        Real-time
      • 15
        Free
      • 14
        Fallback to SSE, forever frame, long polling
      • 13
        WebSockets
      • 8
        Simple
      • 8
        JSON
      • 7
        Open source
      • 5
        Ease of use
      • 5
        Cool
      CONS OF SIGNALR
      • 2
        Requires jQuery
      • 2
        Expertise hard to get
      • 1
        Weak iOS and Android support
      • 1
        Big differences between ASP.NET and Core versions

      related SignalR posts

      Shared insights
      on
      gRPCgRPCSignalRSignalR.NET.NET

      We need to interact from several different Web applications (remote) to a client-side application (.exe in .NET Framework, Windows.Console under our controlled environment). From the web applications, we need to send and receive data and invoke methods to client-side .exe on javascript events like users onclick. SignalR is one of the .Net alternatives to do that, but it adds overhead for what we need. Is it better to add SignalR at both client-side application and remote web application, or use gRPC as it sounds lightest and is multilingual?

      SignalR or gRPC are always sending and receiving data on the client-side (from browser to .exe and back to browser). And web application is used for graphical visualization of data to the user. There is no need for local .exe to send or interact with remote web API. Which architecture or framework do you suggest to use in this case?

      See more
      Pusher logo

      Pusher

      549
      1.3K
      233
      Hosted APIs to build realtime apps with less code
      549
      1.3K
      + 1
      233
      PROS OF PUSHER
      • 54
        An easy way to give customers realtime features
      • 40
        Websockets
      • 35
        Simple
      • 27
        Easy to get started with
      • 25
        Free plan
      • 12
        Heroku Add-on
      • 11
        Easy and fast to configure and to understand
      • 9
        JSON
      • 6
        Azure Add-on
      • 5
        Support
      • 5
        Happy
      • 4
        Push notification
      CONS OF PUSHER
      • 9
        Costly
      • 0
        Aa

      related Pusher posts

      Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

      See more
      Kirill Shirinkin
      Cloud and DevOps Consultant at mkdev · | 3 upvotes · 269.6K views
      Shared insights
      on
      MattermostMattermostPusherPusherTwilioTwilio
      at

      Recently we finished long research on chat tool for our students and mentors. In the end we picked Mattermost Team Edition as the cheapest and most feature complete option. We did consider building everything from scratch and use something like Pusher or Twilio on a backend, but then we would have to implement all the desktop and mobile clients and all the features oursevles. Mattermost gave us flexible API, lots of built in or easy to install integrations and future-proof feature set. We are still integrating it with our main platform but so far the team, existing mentors and students are very happy.

      See more
      MQTT logo

      MQTT

      394
      449
      5
      A machine-to-machine Internet of Things connectivity protocol
      394
      449
      + 1
      5
      PROS OF MQTT
      • 3
        Varying levels of Quality of Service to fit a range of
      • 1
        Very easy to configure and use with open source tools
      • 1
        Lightweight with a relatively small data footprint
      CONS OF MQTT
      • 1
        Easy to configure in an unsecure manner

      related MQTT posts