How do Chrome notifications work internally?
up vote
0
down vote
favorite
I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.
Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?
I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:
- A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called
Application_Id
- Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.
- The client browser sends back that token to the back-end server which keeps that token along with user details
- Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.
Is that correct?
Question:
- What is the device_id in case of Chrome?
- Is the role of GCM stated above correct?
- Do I need to register web application with GCM as mentioned in step_1 ?
google-chrome web-applications push-notification
add a comment |
up vote
0
down vote
favorite
I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.
Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?
I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:
- A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called
Application_Id
- Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.
- The client browser sends back that token to the back-end server which keeps that token along with user details
- Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.
Is that correct?
Question:
- What is the device_id in case of Chrome?
- Is the role of GCM stated above correct?
- Do I need to register web application with GCM as mentioned in step_1 ?
google-chrome web-applications push-notification
I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.
Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?
I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:
- A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called
Application_Id
- Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.
- The client browser sends back that token to the back-end server which keeps that token along with user details
- Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.
Is that correct?
Question:
- What is the device_id in case of Chrome?
- Is the role of GCM stated above correct?
- Do I need to register web application with GCM as mentioned in step_1 ?
google-chrome web-applications push-notification
I recently learnt how mobile push notifications work but did not get any relevant tutorial how push notifications work on the Chrome browser.
Here is my understanding how Chrome notifications must be working based on mobile notifications. But I'm not sure what the device_id in chrome
/browser notification is? Is it some unique chrome_id or mac_id?
I need to work on Android mobile push notification. I have recently gone through some of the tutorials on Google. I would like to summarize my understandings first:
- A developer registers the web app with Chrome cloud service (is it also called GCM i.e. Google Cloud Messaging service?) and get some unique code called
Application_Id
- Once the end user opens the web application, the client side code asks the user whether he/she would like to register for notifications. If he/she says yes, some unique id may be chrome_id or mac_id is sent to to GCM and GCM generates the unique token and sent back to the Chrome hosting web app.
- The client browser sends back that token to the back-end server which keeps that token along with user details
- Now whenever the back-end needs to send a notification to the user, it will send to GCM along with a token which GCM will forward to Chrome.
Is that correct?
Question:
- What is the device_id in case of Chrome?
- Is the role of GCM stated above correct?
- Do I need to register web application with GCM as mentioned in step_1 ?
google-chrome web-applications push-notification
google-chrome web-applications push-notification
asked Nov 4 at 9:49
user3198603
1,34652250
1,34652250
I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46
add a comment |
I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46
I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46
I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53139520%2fhow-do-chrome-notifications-work-internally%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I think you are using google libraries to manage push, but you can work without libraries and it will be a totally different process
– Felipe Morales
Nov 4 at 19:46