Push notification strategy as a Framework

Question

Created Dec ’16

Replies 1

Boosts 0

Participants 2

I was curious if anybody had run across this situation and how you may have handled it. We developer a SDK (.framework) with a couple of features such as a chat window. We would like to offer our users the option for their app to receive push notifications when a new chat message arrives. The complication is that we are an SDK (via included .framework file) and therefore cannot interact with the app's capabilities or push notification certificate.

I feel that it would be very uncommon and unsafe to ask the customer for a copy of their push notification certificate to send pushes on their app's behalf (not sure if that would work anyways).

The only option I can think of currently is to develop an API that the customer's web back end couple implement where we would pass the desired contents of a push notification and their back-end would send the push on our behalf. Our SDK would provide methods to insert these pushes and act upon them.

Our back-end --> Customer's back-end via API --> Customer sends push --> App receives push --> App calls gotPushForSDK(data) and acts.

So, does anybody have a better idea for implementing an optional push capability strategy for a 3rd party SDK framework?

Thanks!

Mike

Boost

Answer 1

jonchambers OP

Dec ’16

> I feel that it would be very uncommon and unsafe to ask the customer for a copy of their push notification certificate to send pushes on their app's behalf (not sure if that would work anyways).

For what it's worth, that would work, and I believe that's actually how a number of large push notification service providers operate. Remember that develoeprs can issue multiple certificates (or signing keys these days) for the same app; a best practice is to issue a certificate/key for exclusive use by a single service provider. That way, the app owner can revoke the certificate/key quickly if something goes wrong without compromising their own ability to send push notifications.

0