Abstract: Extension activation may be provided. Upon receiving a new document associated with a plurality of related documents, extension trigger conditions may be evaluated. In response to determining that an extension trigger is satisfied, a user interface element associated with the extension trigger may be displayed.

Abstract: Extension activation may be provided. Upon receiving a new document associated with a plurality of related documents, extension trigger conditions may be evaluated. In response to determining that an extension trigger is satisfied, a user interface element associated with the extension trigger may be displayed.

Abstract: Application extension management may be provided. A plurality of related documents may be scanned to determine whether an activation trigger associated with an application extension has been triggered. In response to determining that the activation trigger associated with the application extension has been triggered, the application extension may be triggered and a user interface element associated with the application extension may be displayed according to a display rule.

Abstract: Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions.

Abstract: Application extension management may be provided. A plurality of related documents may be scanned to determine whether an activation trigger associated with an application extension has been triggered. In response to determining that the activation trigger associated with the application extension has been triggered, the application extension may be triggered and a user interface element associated with the application extension may be displayed according to a display rule.

Abstract: A compose form for drafting a message is presented inline within a window along with a message list. For example, instead of overlaying the message application's user interface (UI) with a new window for composing a message, the compose form is displayed within a portion of the window reserved for viewing content of messages. While composing the message using the compose form, the rest of the message application's UI remains visible and accessible to the user. For example, the user may navigate to another folder and/or move to another message/conversation by interacting with the tree view/message list view. A draft of the message being composed may be automatically saved when the user navigates away from the compose form (e.g. by selecting another conversation in the list view).

Abstract: A compose form for drafting a message is presented inline within a window along with a message list. For example, instead of overlaying the message application's user interface (UI) with a new window for composing a message, the compose form is displayed within a portion of the window reserved for viewing content of messages. While composing the message using the compose form, the rest of the message application's UI remains visible and accessible to the user. For example, the user may navigate to another folder and/or move to another message/conversation by interacting with the tree view/message list view. A draft of the message being composed may be automatically saved when the user navigates away from the compose form (e.g. by selecting another conversation in the list view).

Abstract: Extension activation may be provided. A document may be opened within a software application associated with an extension. Upon determining that a data element associated with the document is associated with an activation condition of the extension, the extension may be activated.

Abstract: Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions.

Abstract: Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions.

Abstract: Extension prioritization may be provided. Upon opening a document in a software application, a determination may be made whether the document satisfies a respective activation rule for each of a plurality of application extensions associated with the software application. In response to determining that the document satisfies a respective activation rule for each of a plurality of application extensions associated with the software application a priority may be identified for each of the plurality of application extensions and a user interface element associated with at least one of the plurality of application extensions may be displayed.

Abstract: Systems, methods, and software disclosed herein facilitate draft reminders. In at least one implementation, a primary view of an information management application is rendered. In various scenarios the primary view may include primary items, such as emails, events, tasks, or other types of items. When a reminder view is invoked, draft items are identified to include in the reminder view. The reminder view is then rendered in an overlaid manner with respect to the primary view and includes the draft items.

Abstract: Draft management for new electronic communication messages in a mailbox folder is provided. When a user selects to create a new email message, a draft of the new message may appear in a list view of one or more of the user's mailbox folders. The list view may display aggregated contents from both a mailbox folder and the drafts folder. Drafts may be identified as draft messages so that it may be easy for the user to distinguish between draft messages and other email messages. When a draft is deleted or when a draft is sent, it may be removed from the list view. Additionally, selection controls may be provided in the user interface to sort email items by groupings. Selection of a drafts selection control may cause a display of the draft items in the user's email account.

Abstract: Extension activation may be provided. Upon receiving a new document associated with a plurality of related documents, extension trigger conditions may be evaluated. In response to determining that an extension trigger is satisfied, a user interface element associated with the extension trigger may be displayed.

Abstract: Extension prioritization may be provided. Upon opening a document in a software application, a determination may be made whether the document satisfies a respective activation rule for each of a plurality of application extensions associated with the software application. In response to determining that the document satisfies a respective activation rule for each of a plurality of application extensions associated with the software application a priority may be identified for each of the plurality of application extensions and a user interface element associated with at least one of the plurality of application extensions may be displayed.

Abstract: Application extension management may be provided. A plurality of related documents may be scanned to determine whether an activation trigger associated with an application extension has been triggered. In response to determining that the activation trigger associated with the application extension has been triggered, the application extension may be triggered and a user interface element associated with the application extension may be displayed according to a display rule.

Abstract: Application extension management may be provided. Upon logging into a user device by a user, a list of a plurality of extensions associated with the user may be retrieved from a central repository. Access to each of the plurality of extensions associated with the user on the user device may then be provided to the user device.

Abstract: Extension activation may be provided. A document may be opened within a software application associated with an extension. Upon determining that a data element associated with the document is associated with an activation condition of the extension, the extension may be activated.

Abstract: Concepts and technologies are described herein for cross-platform application programming interfaces for applications. In accordance with the concepts and technologies disclosed herein, the cross-platform APIs support interoperability and extensibility with various application programs using a single language and/or set of APIs. Extensions authored for a particular application program may be used with other application programs that expose the same or a similar set of APIs, even if other object models or APIs associated with the application programs differ from one another. Thus, the APIs support cross-platform, cross-device, and cross-version compatibility of extensions.

Abstract: A compose form for drafting a message is presented inline within a window along with a message list. For example, instead of overlaying the message application's user interface (UI) with a new window for composing a message, the compose form is displayed within a portion of the window reserved for viewing content of messages. While composing the message using the compose form, the rest of the message application's UI remains visible and accessible to the user. For example, the user may navigate to another folder and/or move to another message/conversation by interacting with the tree view/message list view. A draft of the message being composed may be automatically saved when the user navigates away from the compose form (e.g. by selecting another conversation in the list view).