Google released its Beta 42 version of Google Chrome, which is compatible with Android, Windows, Mac, Linux and Chrome OS. The new version allows developers to create web applications using advanced scripting languages and includes new features that allow them to create more immersive web applications.
One of the main new developments presented by Google is the new Push API and Notification API that allow developers to incorporate in their sites, Push Notifications to their end users -even after the web-page or tab is closed. Presenting such notifications is subject to obtainingthe explicit permission of the end user.
Google has yet to release formal guidelines concerning the methods of obtaining the end user’s permission for prompting Push Notifications or restrictions concerning the content of such notifications. However, the following guidelines may demonstrate recommended best practices (mainly based on draft guidelines being considered by the Chrome team):

  1. The permission prompt should be put in context and displayed as a clear and conspicuous opt-in call to action.
  2. The permission prompt should be displayed after the user has demonstrated willingness to grant that permission, as well be restricted for a particular purpose
  3. Provide users with in-site management controls which will apply to the notification preferences and frequency.
  4. When permission prompt appears, it is recommended to consider "greying out" the remainder of page with an overlay (to help users notice the permission prompt).
  5. It is recommended to measure the acceptance rates of permission prompts, and the number of users revoking permission with Chrome’s kill switch (Chrome provides users a kill switch that disables all notifications from a specific site).