Abstract: A method for determining relevance for activity feeds is disclosed. Activity feeds are received from one or more business entities. Information is received regarding activities being performed by a user. Context information is received regarding the user. A user context is determined from the information the regarding activities being performed by the user and the context information. The user context indicates the current status of the user. A relevance of the activity feeds is determined based on the user context. At least some of the activity feeds are displayed on a computing device. The at least some of the activity feeds are displayed according to a priority determined by the relevance.

Abstract: Semantic zoom based navigation may be used to navigate content, such as content related to spreadsheets. Different gestures (e.g. pinch/stretch, pan, swipe) may be used while navigating the content. For example, while viewing data from a particular sheet in a workbook a pinch gesture may be received that changes the displayed content to a thumbnail view showing thumbnails that each represent a different sheet within the workbook. A gesture may also be received to change a view of an object. For example, a user may perform a stretch gesture near an object (e.g. a chart, graph, . . . ) that changes the current view to a view showing underlying data for the object. A user may also perform a gesture (e.g. a stretch gesture) on a portion of a displayed object that changes the current view to a view showing the underlying data for a specific portion of the object.

Abstract: A tweak and view mode may be used by a user to see an effect of a proposed change to a document before the change is committed to the document. The application may automatically navigate to different portions of the document and/or display different sections of the document. Instead of the user having to search for the portion of the document affected by the change, the changed portions are determined for the user. The portions may be automatically displayed to the user and/or the user may determine when to move to each different portion that changed as a result of the proposed change. The proposed change may be accepted/rejected by the user. For example, a User Interface (UI) element may be selected by the user to either accept the change or reject the change.

Abstract: Different prices may be charged for an In-App Purchase (IAP) for a same item based on a market associated with the user. For example, a user in one market may be charged a different price for an item than what is charged for the item to a user in a different market. A different product identifier is associated with the item for each of the different markets for the item. The item is submitted to the application store as different items that have the different product identifiers for each of the different markets. When an IAP request for an item is received from a user, a market that is associated with the user is determined based on a location associated with the user. After determining the market for the user, the product identifier that identifies the product is used to obtain the item from the application store.

Abstract: A method for determining relevance for activity feeds is disclosed. Activity feeds are received from one or more business entities. Information is received regarding activities being performed by a user. Context information is received regarding the user. A user context is determined from the information the regarding activities being performed by the user and the context information. The user context indicates the current status of the user. A relevance of the activity feeds is determined based on the user context. At least some of the activity feeds are displayed on a computing device. The at least some of the activity feeds are displayed according to a priority determined by the relevance.

Abstract: Disclosed herein are systems, methods, and software for facilitating application licensing. In at least one implementation, license information for an application is identified based at least in part on a developer profile associated with the application and a state of a license for the application identified from at least a portion of the license information. Presentation of the application in accordance with the state of the license for the application can then be initiated.

Abstract: A method for determining relevance for activity feeds is disclosed. Activity feeds are received from one or more business entities. Information is received regarding activities being performed by a user. Context information is received regarding the user. A user context is determined from the information the regarding activities being performed by the user and the context information. The user context indicates the current status of the user. A relevance of the activity feeds is determined based on the user context. At least some of the activity feeds are displayed on a computing device. The at least some of the activity feeds are displayed according to a priority determined by the relevance.

Abstract: Disclosed herein are systems, methods, and software for facilitating application licensing. In at least one implementation, license information for an application is identified based at least in part on a developer profile associated with the application and a state of a license for the application identified from at least a portion of the license information. Presentation of the application in accordance with the state of the license for the application can then be initiated.

Abstract: Disclosed herein are systems, methods, and software for facilitating application licensing. In at least one implementation, license information for an application is identified based at least in part on a developer profile associated with the application and a state of a license for the application identified from at least a portion of the license information. Presentation of the application in accordance with the state of the license for the application can then be initiated.

Abstract: Disclosed herein are systems, methods, and software for facilitating gallery environments and views. In at least one implementation an initial view is presented of tagged items arranged in tag groups. The tag groups correspond to tags and the tagged items are arranged in the tag groups based on with which of the tags each of the tagged items is associated. One of the groups may be identified for enhanced viewing. Accordingly, tagged items associated with the identified group, by way of their association with a tag corresponding to the group, are identified. In some implementations they may be referred to as enhanced tagged items. An enhanced view may then be presented of at least the enhanced tagged items.

Abstract: Users may collaborate on a document and be notified of changes (e.g. comments, changes) made to the document using different notification methods. A comment may be added to the document from within the document and/or externally from the document. A comment may also be added to a comment stream (e.g. a thread of related comments). The different notification mechanisms may include mechanisms such as: Short Message Service (SMS), Multimedia Messaging Service (MMS), electronic mail, phone call, Instant Messaging (IM), social network post/message, toast message, live tile, and the like. A user may configure the desired notification methods. A newsfeed may display a feed of collaboration items that reflect comments/changes to the document. The user may select a displayed collaboration item from the newsfeed to access the document. A user may also respond (e.g. comment) to a notification that may be added as a comment in the document.

Abstract: Semantic zoom based navigation may be used to navigate content, such as content related to spreadsheets. Different gestures (e.g. pinch/stretch, pan, swipe) may be used while navigating the content. For example, while viewing data from a particular sheet in a workbook a pinch gesture may be received that changes the displayed content to a thumbnail view showing thumbnails that each represent a different sheet within the workbook. A gesture may also be received to change a view of an object. For example, a user may perform a stretch gesture near an object (e.g. a chart, graph, . . . ) that changes the current view to a view showing underlying data for the object. A user may also perform a gesture (e.g. a stretch gesture) on a portion of a displayed object that changes the current view to a view showing the underlying data for a specific portion of the object.

Abstract: A tweak and view mode may be used by a user to see an effect of a proposed change to a document before the change is committed to the document. The application may automatically navigate to different portions of the document and/or display different sections of the document. Instead of the user having to search for the portion of the document affected by the change, the changed portions are determined for the user. The portions may be automatically displayed to the user and/or the user may determine when to move to each different portion that changed as a result of the proposed change. The proposed change may be accepted/rejected by the user. For example, a User Interface (UI) element may be selected by the user to either accept the change or reject the change.

Abstract: Different prices may be charged for an In-App Purchase (IAP) for a same item based on a market associated with the user. For example, a user in one market may be charged a different price for an item than what is charged for the item to a user in a different market. A different product identifier is associated with the item for each of the different markets for the item. The item is submitted to the application store as different items that have the different product identifiers for each of the different markets. When an IAP request for an item is received from a user, a market that is associated with the user is determined based on a location associated with the user. After determining the market for the user, the product identifier that identifies the product is used to obtain the item from the application store.

Abstract: Disclosed herein are systems, methods, and software for facilitating gallery environments and views. In at least one implementation an initial view is presented of tagged items arranged in tag groups. The tag groups correspond to tags and the tagged items are arranged in the tag groups based on with which of the tags each of the tagged items is associated. One of the groups may be identified for enhanced viewing. Accordingly, tagged items associated with the identified group, by way of their association with a tag corresponding to the group, are identified. In some implementations they may be referred to as enhanced tagged items. An enhanced view may then be presented of at least the enhanced tagged items.

Abstract: Disclosed herein are systems, methods, and software for facilitating application licensing. In at least one implementation, license information for an application is identified based at least in part on a developer profile associated with the application and a state of a license for the application identified from at least a portion of the license information. Presentation of the application in accordance with the state of the license for the application can then be initiated.

Abstract: A method for determining relevance for activity feeds is disclosed. Activity feeds are received from one or more business entities. Information is received regarding activities being performed by a user. Context information is received regarding the user. A user context is determined from the information the regarding activities being performed by the user and the context information. The user context indicates the current status of the user. A relevance of the activity feeds is determined based on the user context. At least some of the activity feeds are displayed on a computing device. The at least some of the activity feeds are displayed according to a priority determined by the relevance.

Abstract: Independent software integration is described. In an embodiment, source code of independently developed software is received for integration into a developing software build and the source code is maintained as a limited-access resource to protect proprietary information contained within the source code. The source code is tested independent of the developing software build for error-free integration into the developing software build. Binary data is generated from the source code, and the binary data is integrated into the developing software build such that the independently developed software executes as an integrated component when the software build is complete.

Abstract: In the illustrated and described embodiments, scanning solutions are presented which, from a user's standpoint (either a sender or receiver), are simplistic and intuitive to use. In at least some embodiments, scanned documents can be sent to various digital destinations in which the documents can then be consumed by an end user or system in an intuitive and user-friendly manner. In addition, various embodiments provide infrastructure support for imparting, to the scanning functionality, features that greatly enhance the user's ability to consume and use scanned documents. Other features that can be provided include authentication, the use of scan profiles, post-processing of documents upon acquisition, routing of documents post-processing or upon acquisition or combinations thereof, and integration with other features such as printing, copying and/or faxing to support multi-functionality.