Google I/O 2015 - Google Cloud Messaging 3.0
Why Stack Overflow recommends it
Stack Overflow users link it when explaining how GCM works, especially on iOS, and when citing official figures such as typical message delivery speed.
Recommended by 1 people across 1 different months, 2015 to 2016.
What it is
A Google I/O 2015 conference talk by Francesco Nerieri, Subir Jhanb and Tingmui Li on Google Cloud Messaging 3.0. It covers a simpler way to handle mobile messaging and notifications across Android, iOS and Chrome.
What people said
Recommends abhimuralidharan · 2016-02 · Stack Overflow · on “GCM (Google Cloud Messaging) for iOS apps”
Its a late answer.But I just started working on GCM on iOS.SO I thought to answer this question as it might help someone. The following flow chart gives a brief idea on GCM. [LINK] GCM can can be used to send updates to a single registrationID,a group to registrationIDs,or we can register a topic in the GCM server and we can send updates to all the devices subscribed to that particular topic. Just follow the steps and you will find GCM integration easy. STEP 1: Do watch this video completely : [this video] This gives the basic idea on how GCM works. STEP 2 Goto this link: [LINK] This shows clearly how you should configure the project.The main and important part is properly configuring the GCM con
Cites voscausa · 2015-06 · Stack Overflow · on “Architecture for cross platform messaging app”
Announced last week: Engage your users across Android, iOS and Chrome via Google Cloud Messaging 3.0: [LINK] [this video]
Cites Devesh Agrawal · 2016-02 · Stack Overflow · on “how to get app name and app version in android using gcm 3.0 API”
I am referring this official video. [this video] Here that talk about we can get app version and app name (package name) using GCM API. I searched on google and found nothing. Did anyone have any idea on what API to use to get APP version and app name?
Cites AL. · 2016-05 · Stack Overflow · on “GCM - How long does it take for push notifications to reach the device?”
GCM was designed to send the notification as soon as the device is available. As stated in the GCM Lifetime of a Message [LINK] docs: In the best-case scenario, if the device is connected to GCM, the screen is on and there are no throttling restrictions, the message will be delivered right away. If you are referring to the average speed, it was mentioned back in Google IO '15 [this video] (01:57): ..50milliseconds on average if the devices are online.. There are also some factors which you can affect the delivery of the notification itself. One example of this is setting the delay_while_idle flag (refer to GCM Lifetime of a Message docs for more info). Hope this gives clarity to what you were ask