Microapp subscription recommendations
Abstract
A system that comprises a microapp server includes a memory and at least one processor coupled to the memory. The microapp server is configured to generate a recommendation to modify a set of one or more subscribed microapps. The microapp server is configured to gather observational data that characterizes interactions of a user with an endpoint. The user is associated with the set of one or more subscribed microapps. The microapp server is further configured to identify, based on the observational data, a modification to the set of one or more subscribed microapps. The microapp server is further configured to send, to an administration console, the recommendation to modify the set of one or more subscribed microapps in accordance with the identified modification.
Claims
exact text as granted — not AI-modifiedWe claim:
1 . A non-transitory computer readable medium storing processor executable instructions to identify an infrequently-used subscribed microapp, the processor executable instructions comprising instructions to:
gather, at a microapp server, observational data that characterizes interactions between a user of an endpoint and a set of one or more subscribed microapps that is associated with the user, wherein the user belongs to a user group, and wherein the user is subject to a requirement to subscribe to microapps included in a list of required microapps; identify, by the microapp server, based on the observational data, an infrequently used microapp that is included in the set of one or more subscribed microapps; make a determination that the infrequently used microapp is not included in the list of required microapps; and send, to an administration console, a recommendation that the infrequently used microapp be removed from the set of one or more subscribed microapps that is associated with the user.
2 . The non-transitory computer readable medium of claim 1 , wherein identifying the infrequently used microapp includes determining that the user interacts with the infrequently used microapp with a frequency that is less than a threshold frequency during a time period.
3 . The non-transitory computer readable medium of claim 1 , wherein:
the observational data characterizes interactions of a plurality of users with a corresponding plurality of endpoints, at least some of the users belonging to the user group; at least some users in the user group have a corresponding set of one or more subscribed microapps; and the recommendation is a recommendation that any users in the user group who have a subscription to the infrequently used microapp have such subscription terminated.
4 . The non-transitory computer readable medium of claim 1 , wherein:
the administration console is hosted at the microapp server; and the administration console is configured to display the recommendation in a user interface before implementing the recommendation.
5 . The non-transitory computer readable medium of claim 1 , the processor executable instructions further comprising instructions to receive, from the administration console, an indication that the set of one or more subscribed microapps has been modified to exclude the infrequently used microapp.
6 . The non-transitory computer readable medium of claim 1 , the processor executable instructions further comprising instructions to update the set of one or more subscribed microapps to exclude the infrequently used microapp.
7 . The non-transitory computer readable medium of claim 1 , wherein the administration console is configured to implement the recommendation in response to determining that an auto-update setting indicates that at least some recommendations generated by the microapp server are to be implemented automatically.
8 . A system that comprises a microapp server that includes a memory and at least one processor coupled to the memory, wherein the microapp server is configured to:
gather, at the microapp server, observational data that characterizes interactions between a user of an endpoint and a set of one or more subscribed microapps that is associated with the user, wherein the user belongs to a user group, and wherein the user is subject to a requirement to subscribe to microapps included in a list of required microapps; identify, by the microapp server, based on the observational data, an infrequently used microapp that is included in the set of one or more subscribed microapps; make a determination that the infrequently used microapp is not included in the list of required microapps; and send, to an administration console, a recommendation that the infrequently used microapp be removed from the set of one or more subscribed microapps that is associated with the user.
9 . The system of claim 8 , wherein identifying the infrequently used microapp includes determining that the user interacts with the infrequently used microapp with a frequency that is less than a threshold frequency during a time period.
10 . The system of claim 8 , wherein:
the observational data characterizes interactions of a plurality of users with a corresponding plurality of endpoints, at least some of the users belonging to the user group; at least some users in the user group have a corresponding set of one or more subscribed microapps; and the recommendation is a recommendation that any users in the user group who have a subscription to the infrequently used microapp have such subscription terminated.
11 . The system of claim 8 , wherein:
the administration console is hosted at the microapp server; and the administration console is configured to display the recommendation in a user interface before implementing the recommendation.
12 . The system of claim 8 , wherein the microapp server is further configured to receive, from the administration console, an indication that the set of one or more subscribed microapps has been modified to exclude the infrequently used microapp.
13 . The system of claim 8 , wherein the microapp server is further configured to update the set of one or more subscribed microapps to exclude the infrequently used microapp.
14 . The system of claim 8 , wherein the administration console is configured to implement the recommendation in response to determining that an auto-update setting indicates that at least some recommendations generated by the microapp server are to be implemented automatically.
15 . A method for identifying an infrequently-used subscribed microapp, the method comprising:
gathering, at a microapp server, observational data that characterizes interactions between a user of an endpoint and a set of one or more subscribed microapps that is associated with the user, wherein the user belongs to a user group, and wherein the user is subject to a requirement to subscribe to microapps included in a list of required microapps; identifying, by the microapp server, based on the observational data, an infrequently used microapp that is included in the set of one or more subscribed microapps; making a determination that the infrequently used microapp is not included in the list of required microapps; and sending, to an administration console, a recommendation that the infrequently used microapp be removed from the set of one or more subscribed microapps that is associated with the user.
16 . The method of claim 15 , wherein identifying the infrequently used microapp includes determining that the user interacts with the infrequently used microapp with a frequency that is less than a threshold frequency during a time period.
17 . The method of claim 15 , wherein:
the administration console is hosted at the microapp server; and the administration console is configured to display the recommendation in a user interface before implementing the recommendation.
18 . The method of claim 15 , further comprising receiving, from the administration console, an indication that the set of one or more subscribed microapps has been modified to exclude the infrequently used microapp.
19 . The method of claim 15 , further comprising updating the set of one or more subscribed microapps to exclude the infrequently used microapp.
20 . The method of claim 15 , wherein the administration console is configured to implement the recommendation in response to determining that an auto-update setting indicates that at least some recommendations generated by the microapp server are to be implemented automatically.Join the waitlist — get patent alerts
Track US2022269742A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.