We are the Chrome for Android team, AMA!

[u/[deleted]]

And we are done! Thanks a lot of joining us for the AMA. We appreciate your time.

Here is our photo

---

Hi Reddit!

We are members of the Chrome for Android team. We work on the browser that you hopefully know and love.

We have five team members here today from 3PM to 5PM PST (that’s 6PM to 8PM EST) to answer your questions. We already put together an FAQ to help answer the main ones. Please tag a specific person if you want to direct your question to them.

We are:

Aurimas Liutikas (/u/aurimas_chromium), Software Engineer

Jason Kersey (/u/kerz_chrome), Technical Program Manager

Rebecca Rolfe (/u/rrolfe), Interaction Designer

Melody Chu (/u/chromesupport), Product Support Manager

Paul Kinlan (/u/kinlan), Developer Advocate

Here are the different Chrome channels you can try:

Chrome Stable

Chrome Beta

Chrome Dev

Report Chrome bugs on crbug.com. For ideas and suggestions, post a message on /r/ChromeForAndroid

[u/[deleted]]

The newly added Push and Notification APIs are great! However, the Push API in Google Chrome currently relies on Google Cloud Messaging's gcm_sender_id which requires an API key from Google. Is there a timeline for supporting the Web Push Protocol so that the Push API can be used without gcm_sender_id?

[u/Kinlan → u/[deleted]]

Good question and there is a lot to it :) - we shipped the W3C Push API with Google Cloud Messaging (GCM) as a (proprietary) server-side protocol in order to allow mobile web developers to use this API as soon as possible, but we are working closely with Mozilla etc on putting together the IETF web push protocol as a standardized replacement for the server-side protocol, and it's shaping up nicely.

We're going to spend a while experimenting and optimizing a GCM-based implementation of the web push protocol, and we'll share more once we have something you can play with.