Android - Google Cloud Messaging (GCM)
iOS - Apple Push Notification Service (APNS)
WinPhone - Microsoft Push Notification Service (WPNS)
Web browsers (WebSocket and Push API)
Implemented and Documented Libraries
We have implemented and documented libraries that enable reception of push-messages on the client side for all the supported platforms, including:
- Web browsers
Push messages from other providers can also be received. Besides, there are demo applications with source codes for all platforms, as well as a corresponding testing environment based on a push server.
Registering Mobile and Web Application
- Automated registration based on device's unique ID
- Adding a phone number with or without SMS confirmation by user
- Assigning a customer ID to a registered device
Push messages can be sent with any registered ID. Push messages can be sent to all the applications with the same ID or to the last registered one only.
Basic-level push services do not guarantee delivery of messages. With our solution, your messages are fully protected against loss, and delivery is 100% guaranteed.
Your content will be delivered regardless of its size or type – your messages can include text of any size, as well as audio or video. With the file loading feature implemented at the level of libraries, our service does not limit the size of files, and provides for displaying the progress of loading.
Our solution is capable of acknowledging that a push message has been delivered or read. All the historic data related to any changes in message delivery statuses are stored.
Communication Channel Redundancy
- We back up push messages with SMS, and apply complex channel switchover policies based on delivery statistics and timeouts set up for different types of messages.
- Push messages can be backed up by other delivery channels, such as Viber or Telegram.
- We offer a technology to collect geolocation data which can be used for targeted push messaging.
- You can create your own POI’s or regions.
- You can receive messages from users of mobile or web applications and engage in chatting with them
- Incoming and outgoing messages can be grouped to make dialogs
- All customer communication sessions can be stored by individual customers
- Acknowledgement of reception of users’ messages is implemented at the server API level
We design connectivity solutions based on our customers' requirements
HTTP REST AP
Binary protocol based on Protocol Buffers
The performance of service is only limited by equipment and can be increased by adding hardware.
Minimal hardware requirements for 20,000,000 active devices and 2,000 push messages per second are as follows:
- Application server – 2 х ProLiant DL585 G7, AMD Opteron 4x2.5GHz 12cores, 130gb RAM. Disk system – 15k rpm x 8
- Database server – 1 x ProLiant DL385 G7, AMD Opteron 2x2.3GHz 16cores, 130gb RAM. Disk system – 1Tb 15k rpm x 48
- Delivery of push notifications to web browsers with the use of WebSocket or Push API
- Delivery of poll messages to active applications without sending push notifications; message displaying implemented at the level of libraries for mobile platforms and web applications
- Invisible service push notifications
- Simple push notifications without delivery and reading status data for the content included in the body of a message
- Support of Deep Linking
Web-based Service Management
- Control push notification parameters, set up delivery timeouts, select back-up channels based on message types, etc.
- Create targeted messages based on geolocation data, type of operating system, type of device, recipient sex and age, other data on a mobile application user
- Take advantage of statistics and reporting