The iOS app registers with the Apple Push Notification service (APN) and if successful, is passed a device token encoded in binary format. This token is then passed to the proxibase service and stored as part of the install document for the device/app combo.
We currently have registrationId string property and I'm hoping we can use the same property for both android and iOS and store the device token using base64 string. I think we should add add a property to identify the platform for the install. Something like devicePlatform, required, values [android, ios]. We may also need to start storing the platform api version so if needed, we can adjust the processing logic. This should be easy to capture. Something like deviceApi or deviceVersion.
There are a couple of node modules that simplify interactions with APNs.
The iOS app registers with the Apple Push Notification service (APN) and if successful, is passed a device token encoded in binary format. This token is then passed to the proxibase service and stored as part of the install document for the device/app combo.
We currently have registrationId string property and I'm hoping we can use the same property for both android and iOS and store the device token using base64 string. I think we should add add a property to identify the platform for the install. Something like devicePlatform, required, values [android, ios]. We may also need to start storing the platform api version so if needed, we can adjust the processing logic. This should be easy to capture. Something like deviceApi or deviceVersion.
There are a couple of node modules that simplify interactions with APNs.
https://github.com/argon/node-apn https://www.npmjs.com/package/apns (claims to fork node-apn for more stability with large volumes) https://github.com/neoziro/push-notify (single module with support for apn, gcm, wns)