Remote processing of mobile applications
View Patent ↗In an example implementation of the disclosed technology, a method includes accessing, by a management agent associated with a client device, a profile associated with a requested resource, wherein the profile comprises at least one profile criterion. The method also includes evaluating the profile criterion based, at least in part, on status information associated with the client device to determine any processing restrictions associated with the requested resource. The method also includes, responsive to receiving an indication that the resource is subject to a server-device processing restriction, requesting access to the resource from a remote server and receiving an instance of a user interface for interacting with the resource.
1. A method, comprising:
receiving a request from a management agent executed by a client device for access to server-side aspects of a restricted resource, the management agent executed by the client device being configured to generate an aggregate user interface for interacting with one or more of device-side aspects of the restricted resource or the server-side aspects of the restricted resource;
generating an instance of the restricted resource, the instance of the restricted resource being configured to execute the server-side aspects of the restricted resource;
generating an instance of a user interface associated with the restricted resource, the instance of the user interface associated with the restricted resource being configured to provide interaction with the executed server-side aspects of the restricted resource;
determining that the client device is authorized to access the server-side aspects of the restricted resource based at least in part on a profile associated with the restricted resource and information describing the client device, wherein the profile comprises profile criteria related to state details of the client device; and;
providing the management agent executed by the client device with access to data representative of the instance of the user interface associated with the restricted resource.
2. The method of claim 1 , wherein the profile comprises profile criteria related to technological characteristics of the client device.
3. The method of claim 1 , wherein the profile comprises profile criteria related to contextual characteristics of the client device.
4. A system, comprising:
one or more processors; and,
a memory coupled to the one or more processors, the memory storing instructions that, when executed by the one or more processors, cause the system to:
receive a request from a management agent executed by a client device for access to server-side aspects of a restricted resource, the management agent executed by the client device being configured to generate an aggregate user interface for interacting with one or more of device-side aspects of the restricted resource or the server-side aspects of the restricted resource;
generate an instance of the restricted resource, the instance of the restricted resource being configured to execute the server-side aspects of the restricted resource;
generate an instance of a user interface associated with the restricted resource, the instance of the user interface associated with the restricted resource being configured to provide interaction with the executed server-side aspects of the restricted resource;
provide the management agent executed by the client device with access to data representative of the instance of the user interface associated with the restricted resource;
determine that the client device is not authorized to access the server-side aspects of the restricted resource based at least in part on a profile associated with the restricted resource and information describing the client device; and;
cause at least one remedial action to be performed, the remedial action comprising causing the restricted resource to be inaccessible to the client device.
5. The system of claim 4 , wherein the at least one remedial action is specified by the profile associated with the restricted resource.
6. The system of claim 4 , wherein causing the at least one remedial action to be performed further comprises causing at least one function of the client device to be in a locked state.
7. The system of claim 4 , wherein causing the at least one remedial action to be performed further comprises causing data to be erased from client device.
8. The system of claim 4 , wherein causing the at least one remedial action to be performed further comprises causing at least one additional resource to be inaccessible to the client device.
9. A non-transitory computer-readable medium storing executable instructions that, when executed by one or more processors, cause a computing device to:
receive a request from a management agent executed by a client device for access to server-side aspects of a restricted resource, the management agent executed by the client device being configured to generate an aggregate user interface for interacting with one or more of device-side aspects of the restricted resource or the server-side aspects of the restricted resource;
generate an instance of the restricted resource, the instance of the restricted resource being configured to execute the server-side aspects of the restricted resource;
generate an instance of a user interface associated with the restricted resource, the instance of the user interface associated with the restricted resource being configured to provide interaction with the executed server-side aspects of the restricted resource;
determine that the client device is authorized to access the server-side aspects of the restricted resource based at least in part on a profile associated with the restricted resource and information describing the client device, wherein the profile comprises profile criteria related to state details of the client device; and;
provide the management agent executed by the client device with access to data representative of the instance of the user interface associated with the restricted resource.
10. The non-transitory computer-readable medium of claim 9 , wherein the aggregate user interface further comprises at least one indication that a particular portion of the aggregate user interface is for interacting with the device-side aspects of the restricted resource.
11. The non-transitory computer-readable medium of claim 9 , wherein the aggregate user interface further comprises at least one indication that a particular portion of the aggregate user interface is for interacting with the server-side aspects of the restricted resource.
12. The non-transitory computer-readable medium of claim 9 , further storing instructions that, when executed by the one or more processors, further cause the computing device to:
request information describing the client device from the management agent executed by the client device.
13. The non-transitory computer-readable medium of claim 12 , wherein the information describing the client device comprises information related to state details of the client device.
14. The non-transitory computer-readable medium of claim 12 , wherein the information describing the client device comprises information related to technological characteristics of the client device.
15. The non-transitory computer-readable medium of claim 12 , wherein the information describing the client device comprises information related to contextual characteristics of the client device.
16. The method of claim 1 , further comprising:
requesting information describing the client device from the management agent executed by the client device.
17. The system of claim 4 , wherein the system is further configured to:
request information describing the client device from the management agent executed by the client device.
18. The non-transitory computer-readable medium of claim 9 , wherein the state details of the client device comprise an indication of whether an operating system executed by the client device has been modified from a factory state.