Abstract: Methods and systems for controlling window arrangements for tabbed user interface elements. An example method includes displaying a plurality of application windows including at least one application window for a web browser application having multiple open tabs, the multiple open tabs including at least one active tab and multiple inactive tabs, receiving an input to invoke a snap assist mode; in response to the input, display a snap assist user interface to reconfigure the display of one or more the plurality of the application windows, the snap assist user interface including tab representations and an application-window representation. In response to receiving a selection of a tab representation, a web browser application window is displayed with the corresponding tab as the active tab.

Abstract: Embodiments described herein are directed to simultaneously displaying proxy windows for application windows and/or tabs included in such application windows via a graphical user interface of an operating system. For instance, an application programming interface (API) associated with an application that supports a tabbed document interface (TDI) provides information associated with each tab opened within an application window associated with the application. An API of the operating system receives and utilizes such information to generate and display a proxy window for each tab. The proxy windows for the tabs may be displayed alongside proxy windows of application windows for other applications. The proxy windows may be generated and displayed in response to user invocation of various features of the operating system graphical user interface, including, but not limited to, a task switcher feature, a taskbar feature, or a window snap feature.

Abstract: Embodiments described herein are directed to simultaneously displaying proxy windows for application windows and/or tabs included in such application windows via a graphical user interface of an operating system. For instance, an application programming interface (API) associated with an application that supports a tabbed document interface (TDI) provides information associated with each tab opened within an application window associated with the application. An API of the operating system receives and utilizes such information to generate and display a proxy window for each tab. The proxy windows for the tabs may be displayed alongside proxy windows of application windows for other applications. The proxy windows may be generated and displayed in response to user invocation of various features of the operating system graphical user interface, including, but not limited to, a task switcher feature, a taskbar feature, or a window snap feature.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for integrating web services in shell constructs are provided. Web browsing data, application activity data, and/or device data for a user may be received. A machine learning model may be applied to the data. One or more recommendations may be surfaced based on application of the machine learning model to the data. The recommendations may comprise one or more of: recommendations to install applications; recommendations to add service extensions; recommendations to pin and/or add a shortcut to a website; and/or recommendations to add platform integration services amongst multiple devices.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for integrating web services in shell constructs are provided. Web browsing data, application activity data, and/or device data for a user may be received. A machine learning model may be applied to the data. One or more recommendations may be surfaced based on application of the machine learning model to the data. The recommendations may comprise one or more of: recommendations to install applications; recommendations to add service extensions; recommendations to pin and/or add a shortcut to a website; and/or recommendations to add platform integration services amongst multiple devices.

Abstract: Implementing people as operating system level objects. A method includes, for a user logged in to an operating system, identifying a person with a relationship to the user. For the person, the method further includes identifying information, including information that can be used to communication with the person. The method further includes storing the information related to the person in a data store that is a global data store with respect to the operating system such that the information related to the person can be accessed at the operating system level. The method further includes using the information related to the person stored in the data store to identify applications or services that can be used to communicate with the person. The method further includes displaying in a user interface for the person an enumeration of applications or services that can be used to communicate with the person.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for surfacing collaborative recommendations in relation to topically classified resources are presented. Resources may be topically classified based on application of natural language processing and machine learning models. Relationships amongst users that own, authored and/or edited the resources may be identified. Recommendations may be surfaced based on topical and/or user characteristic overlap associated with the resources. The recommendations may relate to group collaboration on resource creation, sharing of related resources, incorporating related resources in existing resources, and/or recommending group creation and/or collaboration associated with resource topics.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for assisting with event execution are provided. Data from a productivity application associated with a user may be analyzed. A significant life event associated with the user may be identified based on the analysis. A plurality of sources that each have at least one recommendation for executing a type of event corresponding to the significant event may be identified. An itinerary template for the significant life event may be generated from a plurality of the recommendations. The itinerary template may be surfaced. Additional examples of the present disclosure relate to identifying relevant applications for download to a user's device managed by an administrator device.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for assisting with event execution are provided. Data from a productivity application associated with a user may be analyzed. A significant life event associated with the user may be identified based on the analysis. A plurality of sources that each have at least one recommendation for executing a type of event corresponding to the significant event may be identified. An itinerary template for the significant life event may be generated from a plurality of the recommendations. The itinerary template may be surfaced. Additional examples of the present disclosure relate to identifying relevant applications for download to a user's device managed by an administrator device.

Abstract: A computer-implemented technique is described herein for presenting notifications on a user interface presentation of a recipient computing device. The technique is considered tiered because it distinguishes between first-type (people-centric) notifications and second-type notifications, and because it processes and presents first-type notifications in a privileged manner compared to the second-type notifications. For instance, the technique presents content associated with each first-type notification in an allocated window that appears in positional association with a person indicator, where that person indicator identifies the person who sent the first-type notification; the technique presents each second-type notification in a different manner. In some implementations, an application developer who designs a custom first-type notification is given authority to draw within the allocated window that is used to present the custom first-type notification in a manner specified by the application developer.

Abstract: A computer-implemented technique is described herein for presenting notifications on a user interface presentation of a recipient computing device. The technique is considered tiered because it distinguishes between first-type (people-centric) notifications and second-type notifications, and because it processes and presents first-type notifications in a privileged manner compared to the second-type notifications. For instance, the technique presents content associated with each first-type notification in an allocated window that appears in positional association with a person indicator, where that person indicator identifies the person who sent the first-type notification; the technique presents each second-type notification in a different manner. In some implementations, an application developer who designs a custom first-type notification is given authority to draw within the allocated window that is used to present the custom first-type notification in a manner specified by the application developer.

Abstract: A computer-implemented technique is described herein for presenting notifications on a user interface presentation of a recipient computing device. The technique is considered tiered because it distinguishes between first-type (people-centric) notifications and second-type notifications, and because it processes and presents first-type notifications in a privileged manner compared to the second-type notifications. For instance, the technique presents content associated with each first-type notification in an allocated window that appears in positional association with a person indicator, where that person indicator identifies the person who sent the first-type notification; the technique presents each second-type notification in a different manner. In some implementations, an application developer who designs a custom first-type notification is given authority to draw within the allocated window that is used to present the custom first-type notification in a manner specified by the application developer.

Abstract: A computer-implemented technique is described herein for presenting notifications on a user interface presentation of a recipient computing device. The technique is considered tiered because it distinguishes between first-type (people-centric) notifications and second-type notifications, and because it processes and presents first-type notifications in a privileged manner compared to the second-type notifications. For instance, the technique presents content associated with each first-type notification in an allocated window that appears in positional association with a person indicator, where that person indicator identifies the person who sent the first-type notification; the technique presents each second-type notification in a different manner. In some implementations, an application developer who designs a custom first-type notification is given authority to draw within the allocated window that is used to present the custom first-type notification in a manner specified by the application developer.

Abstract: Implementing people as operating system level objects. A method includes, for a user logged in to an operating system, identifying a person with a relationship to the user. For the person, the method further includes identifying information, including information that can be used to communication with the person. The method further includes storing the information related to the person in a data store that is a global data store with respect to the operating system such that the information related to the person can be accessed at the operating system level. The method further includes using the information related to the person stored in the data store to identify applications or services that can be used to communicate with the person. The method further includes displaying in a user interface for the person an enumeration of applications or services that can be used to communicate with the person.

Abstract: Techniques and apparatuses for recipient-based content sharing are described herein. In one or more implementations, input to share content with a recipient is detected. In response to detection of the input, a communication transport for sharing the content with the recipient is determined based at least in part on history of sharing the content with the recipient or a type of the content. The communication transport may be automatically selected from a plurality of communication transports based on the sharing history. For example, the communication transport may be selected based on being the “last used” or “most frequently used” communication transport utilized to share content with the particular recipient. Alternately, a list of suggested communication transports may be presented to the user to enable selection of the communication transport from the list. The content is then shared with the recipient using the determined communication transport.

Abstract: A request, from a requester, is received to view user information on a user's personal site associated with a user. A relationship is determined between the requester and the user. User information is provided to the requester based on the requester's relationship to the user.

Abstract: A request, from a requester, is received to view user information on a user's personal site associated with a user. A relationship is determined between the requester and the user. User information is provided to the requester based on the requester's relationship to the user.

Abstract: A request, from a requester, is received to view user information on a user's personal site associated with a user. A relationship is determined between the requester and the user. User information is provided to the requester based on the requester's relationship to the user.

Abstract: Search results are displayed according to relevance and grouped by the social distance between the person associated with the profile and the user performing the search. Metadata is defined of each of the profiles indicating groups affiliated the profile and a relevance value is determined as a function of the metadata for each of the profiles in the result set. The social distance is determined as a function of a colleague designation associated with the profile.

Abstract: Providing enterprise and targeted content to a personalized portal at a client device in a distributed environment. An administrator managing the distributed environment defines a plurality of workspace pages to be displayed to a user via the portal. The portal also includes a personalized page. The administrator determines workspace content to be provided to the user on the workspace pages via the portal, and the workspace content includes a set of predetermined content parameters. Targeted content is selected from the workspace content as a function of user profile data and the set of predetermined content parameters. The arranged targeted content and personalized content are rendered on the pages via the portal.