Feature usage prediction using shell application feature telemetry

• US 10,346,284 B1
• Filed: 01/11/2018
• Issued: 07/09/2019
• Est. Priority Date: 01/11/2018
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Yang, Chenguang, Kohlmeier, Bernhard S. J., Ma, Lin, Kleiner, Madeline, Qin, Peng
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US15/868,697
• Publication Number:
  US 20190213106A1
• Time in Patent Office: 544 Days
• Field of Search: 717123-129
• CPC Class Codes: G06F 11/3608 using formal methods, e.g. model checking, abstract interpretation theorem proving G06N5/013
• CPC Class Codes: G06F 11/3616 using software metrics
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: G06Q 30/0202 Market predictions or forecasting for commercial activities

Abstract

A shell application feature can include trigger information and logic. During operation, the shell application feature can receive an indicator that a trigger occurred; and, in response to the trigger, initiate its logic. The logic of the shell feature is locally performed to identify whether state, object type, user actions, or a combination thereof, with respect to the application satisfy a success criteria corresponding to behavior that will be a prerequisite for a potential feature that is not yet fully implemented. If the state, object type, user action, or combination thereof satisfies the success criteria, a success notification can be communicated to a feature collection service.

Claims

1. A system comprising:

one or more processors;

a storage system;

an application stored on the storage system;

a shell application feature comprising trigger information to define a trigger and logic of a shell feature stored on the storage system that, when executed by at least one of the one or more processors, directs the at least one of the one or more processors to;

receive an indicator that the trigger occurred;

in response to the trigger, initiate the logic of the shell feature, wherein the shell feature is a potential feature that is not yet fully implemented for the application;

determine, according to the logic of the shell feature, whether one or more of state, object type, and

user actions with respect to the application satisfy a success criteria corresponding to behavior that will be a prerequisite for the potential feature that is not yet fully implemented; and

if the one or more of state, object type, and user action satisfies the success criteria, communicate a success notification to a feature collection service.

2. The system of claim 1, wherein the application comprises a productivity application.

3. The system of claim 1, wherein the application comprises a social media application.

4. The system of claim 1, wherein the application comprises a communication application.

5. The system of claim 1, wherein the application comprises an operating system.

6. The system of claim 1, further comprising a second shell application feature stored on the storage system that, when executed by at least one of the one or more processors, directs the at least one of the one or more processors to:

receive a corresponding indicator that a corresponding trigger occurred;

in response to the corresponding trigger, initiate logic of a second shell feature, wherein the second shell feature is a second potential feature that is not yet fully implemented for the application;

determine, according to the logic of the second shell feature, whether one or more of state, object type, and

user actions with respect to the application satisfy a second success criteria corresponding to behavior that will be a prerequisite for the potential second feature that is not yet fully implemented; and

if the one or more of state, object type, and user action satisfies the second success criteria, communicate a corresponding success notification to the feature collection service.

7. The system of claim 1, the potential feature comprises a service call, wherein in the logic of the shell feature, the service call is not performed.

8. The system of claim 1, wherein the shell application feature further directs the processing system to:

store metadata on the storage system when performing the logic of the shell feature;

perform local metadata processing of the metadata; and

if the one or more of state, object type, and user action satisfies the success criteria, communicate processed metadata to the feature collection service.

9. One or more computer readable storage media having instructions including a shell application feature comprising trigger information to define a trigger and logic of a shell feature stored thereon that when executed by a computing device, direct the computing device to at least:

receive an indicator that the trigger occurred;

in response to the trigger, initiate the logic of the shell feature, wherein the shell feature is a potential feature that is not yet fully implemented for the application;

determine, according to the logic of the shell feature, whether one or more of state, object type, and

user actions with respect to the application satisfy a success criteria corresponding to behavior that will be a prerequisite for the potential feature that is not yet fully implemented; and

if the one or more of state, object type, and user action satisfies the success criteria, communicate a success notification to a feature collection service.

10. The media of claim 9, wherein the instructions that direct the computing device to perform the logic of the shell feature direct the computing device to:

locally store metadata about actions of the user; and

identify from the metadata whether the one or more of state, object type, and user actions satisfy the success criteria.

11. The media of claim 9, the potential feature comprises a service call.

12. The media of claim 11, wherein in the logic of the shell feature, the service call is not performed.

13. A method comprising:

receiving, at a system comprising a shell application feature, an indicator that a trigger occurred, wherein the shell application feature comprises trigger information to define the trigger and logic of a shell feature, wherein the shell feature is a potential feature that is not yet fully implemented for the application;

in response to the trigger, initiating the logic of the shell feature;

determining, according to the logic of the shell feature, whether one or more of state, object type, and

user actions with respect to one or more applications satisfy a success criteria corresponding to behavior that will be a prerequisite for the potential feature that is not yet fully implemented; and

if the one or more of state, object type, and user action satisfies the success criteria, communicating a success notification to a feature collection service.

14. The method of claim 13, further comprising:

receiving an update to at least one of the one or more applications, wherein the update comprises the shell application feature comprising the trigger information to define the trigger and the logic of the shell feature.

15. The method of claim 13, wherein at least one of the one or more applications comprises a productivity application.

16. The method of claim 13, wherein at least one of the one or more applications comprises a social media application.

17. The method of claim 13, wherein at least one of the one or more applications comprises a communication application.

18. The method of claim 13, wherein at least one of the one or more applications comprises an operating system.

19. The method of claim 13, wherein the potential feature comprises a service call.

20. The method of claim 13, further comprising:

locally storing metadata on the storage system when performing the logic of the shell feature;

performing local metadata processing of the metadata; and

if the one or more of state, object type, and user action satisfies the success criteria, communicate processed metadata to the feature collection service.