I would suggest that if you have data that needs to be encrypted, your push message should be used to signal your application to download the data securely from your services and not be delivered over push networks.
So let's say you are a doctor and you want to send a patient a reminder for their upcoming appointment. Instead of encrypting the appointment object, sending it through push networks, and decryption being performed on the client, the push messages should be a "appointment reminder" event to the user. The notification handler on the client device would receive this message and enqueue a job on the device to download the appointment information from the doctor's servers.
The reason you want to schedule a job instead of performing the download is that push notifications should be handled very quickly and any follow up work should be scheduled by your operating system. Android is a little more generous about this than iOS, but both will aggressively kill apps that take too long to process a push message.
--
You received this message because you are subscribed to the Google Groups "Aerogear" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aerogear+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aerogear/78787bf7-63b7-4bab-ae03-7c5c30d6edee%40googlegroups.com.