Why do we need the client side?

Answered

Comments

2 comments

  • Avatar
    Gayview Mahat

    Am I correct that you are referring to Pushwoosh SDK as the "client side"?

    Generally, you can send notifications via Pushwoosh to your application without making any changes in the code / implementing SDK. However, it's not reliable:

    • there might be some discrepancy on how your code and our SDK process the received push, which can result in incorrect display of the notification;
    • many Puswhoosh features just won't work without SDK;
    • you would have to keep a list of push tokens on your backend.
  • Avatar
    Brian Watts

    --> there might be some discrepancy on how your code and our SDK process the received push, which can result in incorrect display of the notification;

    When the push is received, the server is polled for more complete information anyway -- we don't even need the payload, just the trigger event

    --> many Puswhoosh features just won't work without SDK; Can you list this please? Or at least indicate which features WILL work if that is easier

    --> you would have to keep a list of push tokens on your backend. We are doing that anyway.

    I guess this boils down to -- why use PushWoosh at all? I am experimenting with it because I am concerned that as we do not have experience delivering tens of thousands of push notifications at once, and it is difficult to test these conditions, we might benefit from handing the delivery to a third part with such experience. Therefore, the only thing we need the app for is the push delivery -- everything else is taken care of.

    If you think that we would not benefit from using PushWoosh under these circumstances, please say so.

Please sign in to leave a comment.