Improving the UX has always been on the radar when Chrome brings out an update. In this recent update, they worked on the need to provide users with a seamless experience on Chrome for Android. With Chrome 63, users won’t be annoyed with notification prompts they don't want to see and marketers can know if the user is interested or not right away without pulling their hair out.
One fine day the people of the world wondered how the Google Chrome desktop push notification ‘bell’ landed on their menu bar. They didn't remember adding it there nor giving permission to make any changes. Yet, there it was embedded in the menu bar, refusing to budge. They did not enable chrome push notification, but it suddenly had taken over their desktop. Some of the comments in the product forums deserve a read. With so many annoyed users complaining about the design, the way chrome push notifications had hijacked the notification menu, the absence of a disable feature, it was about time that chrome got native web push notification on Mac. Google chrome tried to implement its own in-house chrome desktop notifications system instead of OS X Notification Center and we all know how that went.
Mobile and Web both have evolved rather drastically over the last 18 months. Mobile continues to be the preferred choice of medium for, well practically everything. Content, gaming, messaging - mobile has taken everyone by storm. Browsers at the same time have been able to catch up ( almost ) with their native counterparts, allowing developers to do more. In 2016, Chrome on Mobile surpassed the count of billion active users. The recent developments on Chrome and product road map show an uncanny resemblance to that of an operating system. Rather than just another browser. Chrome 59 unpacks capabilities that will help developers up the ante on user engagement. One of it being integrating with OS. Here are the key highlights:
Introducing Chrome Rich Push Notifications Everyone likes makeovers. Alright. Not everyone. But every once in awhile, it is good to go for a makeover and come back refreshed. This is exactly what Chrome has done with web push notifications. And yes, we are super excited about it.
Battery life is one aspect we constantly keep in mind especially when one is on the go. You have loads of work to do, but you can foresee the battery betraying you big time. So using a power efficient browser plays a vital role in minimizing the battery usage. Google Chrome has been used widely for its double digit speed and sleek interference. Chrome was the one that started off with push notifications from v42 and it has been one of the revolutionary innovations, with 350 million push notifications sent to users everyday. But one thing for which it has always been pointed fingers at, was for hogging battery.
Before we talk how to generate your GCM Sender ID and GCM Server Key, let us take a quick shot at answering these questions. What Is GCM Service? Google Cloud Messaging is a free service that enables developers to send messages between GCM servers and client apps. This includes downstream messages from GCM servers to client's app, and upstream messages from client apps to GCM servers. Starting May, Google Cloud Messaging Platform is being replaced by Firebase Cloud Messaging.
Google Chrome is widely used across the globe on both mobile and desktop. Chrome has always tried to bring out the best in them and strive to bring innovative change in every new update that they bring. So there were no surprises when it became the first browser to support web push notifications in Chrome 42.