I'm evaluating Pushwoosh for my chat service which has iOS and Android client apps.

We are planning to use Pushwoosh via only REST APIs such as createMessage, registerDevice or unregisterDevice from server side of our service. In other words, We don't use your SDKs from our client apps at all.

Is it OK? Or, do you have any prerequisites about use of your client SDKs?

asked 13 Jan '17, 09:09
kohei's gravatar image


edited 13 Jan '17, 09:44


Please note that while you may actually avoid integrating the SDK and register the devices remotely via API, Pushwoosh strongly discourage users from doing so.

There are quite a few disadvantages in not using Pushwoosh SDK. The main one is the impossibility to track when FCM/APNs/etc. changes the push token of a device, which means that some of your users would not receive their notifications.

The overall reliability of the system would be lower: for instance, there might be a discrepancy in how your code and SDK process the received push, which will result in incorrect display of the notification or not receiving the push at all.

Of course, there is nothing wrong with NOT using the SDK. Needless to say that in this case you are solely responsible for the data accuracy.

permanent link
answered 16 Jan '17, 05:16
Oleg%20Zhukov's gravatar image

Oleg Zhukov

edited 16 Jan '17, 05:16

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 13 Jan '17, 09:09

question was seen: 646 times

last updated: 16 Jan '17, 05:16