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.
OneSignal comes with a free plan and easy integration, unlike CleverTap which has a starting price of $200 per month and a difficult integration process. That is why we selected OneSignal instead of CleverTap.
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 …
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 …
OneSignal is the one that has more integrations with plugins, external API and that is completely free and easy to install. They have a very good UI with many options and they will never ask for money to use this service. You can have unlimited subscribers and you can send …
OneSignal is much more user-friendly, is free to use, and integrates with many more services. After the great redesign of OneSignal, it has become even better: easy localizations of the push, A/B tests and templates work great. Besides, there are a number of parameters you can …
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.
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.
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.
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.
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.