One of the most interesting and valuable developments in enterprise social software (ESS) over the last few years has been the introduction of embedded experiences. Simply put, these are event-driven notifications, usually from other enterprise applications and systems, that surface within the activity stream of an ESS application. Embedded experiences go beyond merely notifying of something important; they also allow one or more actions to be taken to move a business process to the next step.
Embedded experiences are great, but they have been written in proprietary code tied to a specific ESS vendor’s offering. It has not been possible to reuse actionable notifications across vendors’ solutions.
Google has announced a new feature in the latest beta version of its Chrome browser that will provide an open standard alternative for the delivery of extended experiences. Chrome 48 Beta enables developers to quickly create notifications with buttons that let users complete tasks. Those notification can be pushed from browser-based applications and webpages, as well as from Chrome OS applications and extensions to the Chrome browser.
Google and Mozilla employees have contributed to the development of the fledgling Notifications API standard under the auspices of the Web Hypertext Application Technology Working Group (WHATWG) community. This specification is what has been implemented in Google’s Chrome 48 Beta.
A Notification Generator built to define HTML-based embedded experiences has been created by Peter Beverloo. The generator shows how easy it is to define an embedded experience that can appear in any HTML5-compliant web browser.
As previously noted, embedded experiences have been proprietary to individual vendor’s applications and platforms. Google’s beta implementation of the WHATWG’s Notifications API specification is a first important step toward embedded experiences that will work across operating systems and applications. When the feature is properly vetted and becomes part of the stable release of Chrome (and, we assume, Mozilla’s Firefox browser), open, actionable notifications will be reality.
This is important because it will make the development and use of embedded experiences far more practical and widespread. Enterprise software vendors who choose to implement the WHATWG’s Notifications API specification will empower their customers to more easily create interoperability with other vendors’ browser-based tools. Actionable data embedded in notifications will be able to be passed between systems, business process execution will be accelerated, and personal productivity will be increased.
This news further intensifies the browser-based versus operating system-dependent application debate, especially with regards to mobile computing. The current preference for native applications on mobile devices will be challenge to the uptake of the Notifications API specification, given its dependence on the Web browser. Development of more of these types of Web standards is precisely what is needed to swing the pendulum back toward browser-based applications.