Like its desktop counterpart, Chrome for Android now supports native push notifications. Developers can use the new Push API and Notifications API to have their sites send notifications to their users even after the given page is closed. Google promises users have to first grant explicit permission before they receive such a message, and for now at least, the notifications includes a “Site Settings” button where users can easily disable them.
Next up, Google has tweaked how home screen promotion works. While Chrome 32 introduced the ability for Android users to add home screen shortcuts to their favorite websites via a menu item, Chrome 42 takes the functionality a step further by showing a banner. Users who frequently visit a high-quality web app will be asked if they want to add the site to their home screen with one tap:
If you’re a developer who wants to take advantage of this new feature, you have to meet the eligibility criteria (provide a Web App Manifest, serve all content using HTTPS, and at least partially work offline using a service worker), which will evolve over time based on feedback from users and developers. Google wants to ensure users have a good experience when launching sites from the Android home screen, including when they’re offline. More information about these “app install banners” is available here.
Last but not least, Chrome 42 is the last version to support Android 4.0 Ice Cream Sandwich. Chrome 43, which should be out in the next six weeks or so, will require Android 4.1 or higher.