Google Cloud Messaging (GCM) will be deprecated soon...

It's time to Upgrade from GCM to FCM:
https://developers.googleblog.com/2018/04/time-to-upgrade-from-gcm-to-fcm.html

Step-by-step migration guide: https://developers.google.com/cloud-messaging/android/android-migrate-fcm

#FCM #GCM

End-to-end encryption for push messaging, simplified:

Developers already use HTTPS to communicate with Firebase Cloud Messaging (FCM). The channel between FCM server endpoint and the device is encrypted with SSL over TCP. However, messages are not encrypted end-to-end (E2E) between the developer server and the user device unless developers take special measures. To this end, we advise developers to use keys generated on the user device to encrypt push messages end-to-end. But implementing such E2E encryption has historically required significant technical knowledge and effort. That is why we are excited to announce the Capillary open source library which greatly simplifies the implementation of E2E-encryption for push messages between developer servers and users' Android devices.

https://android-developers.googleblog.com/2018/06/project-capillary-end-to-end-encryption.html?m=1

https://github.com/google/capillary

#Google #FCM

The GCM server and client APIs are deprecated and will be removed as soon as April 11, 2019 (in 1 month !).

Migrate GCM apps to Firebase Cloud Messaging (FCM), which inherits the reliable and scalable GCM infrastructure, plus many new features. See the migration guide to learn more.

https://www.youtube.com/watch?v=IeexEiFprY8

Migrating from GCM to FCM → https://goo.gl/hyt6e7
FCM Guide → https://goo.gl/GQ67DS
GCM Migration FAQ → https://goo.gl/hY48co

#GCM #Firebase #FCM #Google