| Hi! I'm the co-founder of OneSignal, a push notification and marketing automation service. Here are some of the batching mechanisms we support: 1. Sending to a list of devices based on push tokens, onesignal identifier, or your own customer identifers. 2. Sending to a segment that you create via our dashboard or API. Segments can combine filters such as device type, language, country code, activity in your application, or custom attributes you define 3. Sending to a list based on filters that you provide to our API "eg: Send to all devices that have launched my app in the last week" 4. Automated Messages - Automatically send messages to devices that match certain criteria (e.g. adding an item to their cart) In addition, we provide some useful quality-of-live features, including: * Idempotent notifications * Tracking when notifications are received by a device ("Confirmed Delivery") * Targeting notifications based on a user's interactions with previous messages * Very fast notification delivery Here's our API documentation for sending notifications: https://documentation.onesignal.com/reference/create-notific... We also provide client libraries for most popular programming languages: https://documentation.onesignal.com/docs/ruby-client-sdk These features are all available on our free plan. Our free plan has no limit on API calls, push tokens, or push messages. It's designed to be equal to or better than Firebase's notification console and FCM API in most dimensions. We also have paid features that provide deeper message analytics, marketing automation features, and other channels (email & sms). Please feel free to reach out to me directly if you have questions or need help migrating over: george[@]onesignal.com |