Google offers the Firebase suite of application development tools, available free or at cost for higher degree of usages, priced flexibly accorded to features needed. The suite includes A/B testing and Crashlytics, Cloud Messaging (FCM) and in-app messaging, cloud storage and NoSQL storage (Cloud Firestore and Firestore Realtime Database), and other features supporting developers with flexible mobile application development.
$0.01
Per Verification
OneSignal
Score 8.3 out of 10
N/A
OneSignal’s omnichannel customer engagement platform offers push notifications, email, in-app messages, and SMS. OneSignal’s automated customer Journeys and one-off campaigns allow users to create messaging strategies that convert, inform, and retain audiences, with little to no coding required for setup.
Look Firebase is a complete platform that includes a Push notification/InApp space. We had a lot of troubles while implementing Firebase: sometimes we thought it was ready until we tried to attach an image for Push notifications. This being said, the developers had to review …
In my opinion, OneSignal documentation / API is more friendly [than] Firebase. Maybe because Firebase is already "too big," but OneSignal is focused on one solution that giving our notification through to our customer. In that case, OneSignal is chosen by our company. Several …
Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.
Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.
I think One Signal is very well suited for mobile app owners who want to be in touch with their user base more easily by sending push notifications and in-app messages. I'm not sure how well that works for SMS messaging as I haven't yet tried it. I wouldn't necessarily recommend it if your in-apps are very rare.
Analytics wise, retention is extremely important to our app, therefore we take advantage of the cohort analysis to see the impact of our middle funnel (retargeting, push, email) efforts affect the percent of users that come back into the app. Firebase allows us to easily segment these this data and look at a running average based on certain dates.
When it comes to any mobile app, a deep linking strategy is essential to any apps success. With Firebase's Dynamic Links, we are able to share dynamic links (recognize user device) that are able to redirect to in-app content. These deep links allow users to share other deep-linked content with friends, that also have link preview assets.
Firebase allows users to effectively track events, funnels, and MAUs. With this simple event tracking feature, users can put organize these events into funnels of their main user flows (e.g., checkout flows, onboarding flows, etc.), and subsequently be able to understand where the drop-off is in the funnel and then prioritize areas of the funnel to fix. Also, MAU is important to be able to tell if you are bringing in new users and what's the active volume for each platform (Android, iOS).
Attribution and specifically multi-touch attribution could be more robust such as Branch or Appsflyer but understand this isn't Firebases bread and butter.
More parameters. Firebase allows you to track tons of events (believe it's up to 50 or so) but the parameters of the events it only allows you to track 5 which is so messily and unbelievable. So you're able to get good high-level data but if you want to get granular with the events and actions are taken on your app to get real data insight you either have to go with a paid data analytics platform or bring on someone that's an expert in SQL to go through Big Query.
City-specific data instead of just country-specific data would have been a huge plus as well.
Is still in development: we know OneSignal is still in development and sometimes it takes longer to create or fulfill certain features.
Payment: payment menu is not at the glance, [and] is just difficult sometimes to find -it is a minor issue.
Send to certain custom segments through specific OneSignal IDs; you can do it though API doing a GET call with tools like Postman. If this can be done from OneSignal it would be great.
Firebase functions are more difficult to use, there are no concepts of triggers or cascading deletes without the use of Firebase functions. Firebase functions can run forever if not written correctly and cause billing nightmares. While this hasn't happened to us specifically it is a thing that happens more than one realizes.
I give an 8 in this question mainly for 2 reasons: the products even if they look like complete and are highly customizable and usable, they are still missing some logical features. For example, send messages to a list of users - now days you can do it with postman and get calls. A second example is App messaging that is still in development and has many opportunities.
Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.
Their customer support has been top-notch. They are able to assist you in getting through any problems that you may have and respond in a very timely manner. I've dealt with them on 4-5 instances over the years and my issues were always resolved within a matter of a few business days.
Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.
In my opinion, OneSignal documentation / API is more friendly [than] Firebase. Maybe because Firebase is already "too big," but OneSignal is focused on one solution that giving our notification through to our customer. In that case, OneSignal is chosen by our company. Several years after that, Firebase announced it supported [the] iOs platform too but our company already using OneSignal to our notification provider.
Makes building real-time interfaces easy to do at scale with no backend involvement.
Very low pricing for small companies and green-fields projects.
Lack of support for more complicated queries needs to be managed by users and often forces strange architecture choices for data to enable it to be easily accessed.