Staged Release of Updates with Anomaly Monitoring

1. A method of staging installation of a feature, said method comprising: on a first computing device in communication with a plurality of remote computing devices maintaining a feature associated with an application, wherein said features comprises a package of code and an action setting, said action setting comprising an action selected from the group consisting of Disable, Enable, and Pause; monitoring, by said first computing device, an active subset of said plurality of remote computing devices running said application according to a set of metrics associated with said application; activating installation of said feature from said first computing device to a first segment of said active subset by changing said action setting from Disable to Enable and transmitting said package of code; monitoring said installation to detect an anomaly among said set of metrics; and in response to detecting said anomaly, pausing installation of said feature from said first computing device to said first segment by changing said action setting from Enable to Pause and generating a repair ticket.

2. The method of claim 1 , further comprising: activating installation of said feature by changing said action setting from Disable to Enable for a subsequent segment of said active subset of said plurality of remote computing devices, iteratively, unless an anomaly is detected and until said feature is installed on substantially all devices in said active subset.

3. The method of claim 1 , further comprising: in response to detecting an anomaly among said set of metrics associated with said first segment, disabling installation of said feature from said first computing device by changing said action setting from Enable to Disable and generating a repair ticket.

4. The method of claim 1 , further comprising: uploading said feature from said first computing device across a network to an application distribution platform; detecting from said application platform a quantity of installations of said feature; and in response to said detected quantity reaching a threshold limit, executing said step of activating installation of said feature for said first segment of said active subset.

5. The method of claim 1 , wherein said feature comprises a plurality of features, each comprising a rank, said method further comprising: maintaining on said first computing device an ordered list of said plurality of features by rank; and activating installation of said plurality of features, by said rank according to said ordered list, from said first computing device to said first segment of said active subset by changing said action setting from Disable to Enable and transmitting said package of code, wherein said step of pausing installation further comprises activating installation of a subsequent feature, by said rank according to said ordered list.

6. The method of claim 1 , wherein said set of metrics comprises a performance metric comprising: a crash rate associated with said application; an app-open latency associated with an instance of opening said application; and a task latency associated with a duration between starting and completing a selected task by said application, wherein said selected task comprises a capture task and a send task.

7. The method of claim 1 , wherein said set of metrics comprises an engagement metric comprising: a session length associated with said application; and a quantity of user actions performed by said application, wherein said user actions comprise creation actions and send actions.

8. The method of claim 1 , wherein said set of metrics comprises a plurality of metric values, each associated with a stability threshold, and wherein said step of monitoring the installation further comprises: determining for each metric value whether said associated stability threshold is exceeded.

9. A system for monitoring the staged release of a feature, the system comprising: a first computing device in communication with a plurality of remote computing devices, said first computing device comprising a processor, a memory, and programming stored in the memory, wherein execution of said programming by said processor configures said first computing device to perform operations, including operations to: maintain a feature associated with an application, wherein said feature comprises a package of code and an action setting, said action setting comprising an action selected from the group consisting of Disable, Enable, and Pause; monitor an active subset of said plurality of remote computing devices running said application according to a set of metrics associated with said application; activate installation of said feature from said first computing device to a first segment of said active subset by changing said action setting from Disable to Enable and transmitting said package of code; monitor said installation to detect an anomaly among said set of metrics; and in response to detecting said anomaly, pause installation of said feature from said first computing device to said first segment by changing said action setting from Enable to Pause and generating a repair ticket.

10. The system of claim 9 , wherein execution of said programming by said processor further configures said first computing device to perform additional operations, including operations to: activate installation of said feature by changing said action setting from Disable to Enable for a subsequent segment of said active subset of said plurality of remote computing devices, iteratively, unless said anomaly is detected and until said feature is installed on substantially all devices in said active subset.

11. The system of claim 9 , wherein execution of said programming by said processor further configures said first computing device to perform additional operations, including operations to: in response to detecting said anomaly among said set of metrics associated with said first segment, disabling installation of said feature from said first computing device by changing said action setting from Enable to Disable and, generating a repair ticket.

12. The system of claim 9 , wherein execution of said programming by said processor further configures said first computing device to perform additional operations, including operations to: upload said feature from said first computing device across a network to an application distribution platform; detect from said application platform detecting a quantity of installations of said feature; and in response to said detected quantity reaching a threshold limit, executing said step of activating installation of said feature for said first segment of said active subset.

13. The system of claim 9 , wherein said feature comprises a plurality of features, each comprising a rank, and wherein execution of said programming by said processor further configures said first computing device to perform additional operations, including operations to: maintain on said first computing device an ordered list of said plurality of features by rank; and activate installation of said plurality of features, by said rank according to said ordered list, from said first computing device to a first segment of said active subset of said plurality of remote computing devices by changing said action setting from Disable to Enable and transmitting said package of code, wherein said operation of pausing installation further comprises activating installation of a subsequent feature, by said rank according to said ordered list.

14. The system of claim 9 , wherein said set of metrics comprises a performance metric comprising: a crash rate associated with said application; an app-open latency associated with an instance of opening said application; and a task latency associated with a duration between starting and completing a selected task by said application, wherein said selected task comprises a capture task and a send task.

15. The system of claim 9 , wherein said set of metrics comprises an engagement metric comprising: a session length associated with said application; and a quantity of user actions performed by said application, wherein said user actions comprise creation actions and send actions.

16. The system of claim 9 , wherein said set of metrics comprises a plurality of metric values, each associated with a stability threshold, and wherein said operation of monitoring said installation further comprises: determining for each metric value whether said associated stability threshold is exceeded.

17. A non-transitory processor-readable storage medium that stores processor-executable instructions that, when executed by a processor of a machine, cause said machine to perform operations comprising: on a first computing device in communication with a plurality of remote computing devices, maintaining a feature associated with an application, wherein said feature comprises a package of code and an action setting, said action setting comprising an action selected from the group consisting of Disable, Enable, and Pause; monitoring an active subset of said plurality of remote computing devices running said application according to a set of metrics associated with said application; activating installation of said feature from said first computing device to a first segment of said active subset by changing said action setting from Disable to Enable and transmitting said package of code; monitoring said installation to detect an anomaly among said set of metrics; and in response to detecting said anomaly, pausing installation of said feature from said first computing device to said first segment by changing said action setting from Enable to Pause and generating a repair ticket.

18. The non-transitory processor-readable storage medium of claim 17 , wherein execution of said instructions causes said machine to perform further operations, comprising: activating installation of said feature by changing said action setting from Disable to Enable for a subsequent segment of said active subset of said plurality of remote computing devices, iteratively, unless said anomaly is detected and until said feature is installed on substantially all devices in said active subset.