An embedded experience is a way for applications to embed content into other applications and let users interact dynamically with that content directly in context without having to switch to another application.
Embedded experiences eliminate the hassle of constantly switching windows, opening applications, and authenticating with multiple sites and services. This constant switching causes users to lose focus on their tasks, which decreases their levels of productivity. If users can access, filter, and respond to most of their work processes from a stream of activities in a single interface, they can manage their work more effectively.
The best way to demonstrate embedded experiences is to see them in action in the developer sandbox
on the OpenSocial website. The following image shows an example of an embedded experience in the context of an activity stream, a personal view of relevant updates and events that have been aggregated from multiple sources.
In the image, notice the activity stream on the left. Similar to a news feed on a social networking site but applied to enterprise data and data sources, an activity stream is updated with new content and events as data is retrieved and published to the stream. Data that is published to the activity stream comes from any service, including IBM
® services, enterprise services, and internet services.
In the activity stream, the user can click any of the events to get more information about that event. Here, the owner has clicked a file-posting event. A window displays off to the side of the activity stream that allows the user to perform multiple actions with the file, for example preview the file, share the file, save the file to a folder, and more. This window of information is the embedded experience. Users can easily interact with the file without ever having to leave their activity stream.
™ Object Notation (JSON) format.
Next topic: Tutorial: Creating embedded experiences