Adaptive deployment of applications for mobile devices
View Patent ↗A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.
1. A method comprising:
receiving, by a processor, a request for installing a version of an application for a user of a particular mobile user device;
receiving, by the processor, device configuration information that includes one or more features of the particular mobile user device from a device database, specifications from the device database mapping to one or more components in an application component data store;
parsing, by the processor, the device configuration information according to the one or more features of the particular mobile user device;
creating, by the processor, a meta-data signature from a subset of the parsed device configuration information;
retrieving in response to the request, by the processor, a configuration of software components from the application component data store, the configuration of software components is selected from multiple software components that can be assembled into variations of the application, the selection based at least in part on mapping the meta-data signature created from the subset of the parsed device configuration information to the configuration of software components;
compiling, by the processor, the configuration of software components into the version of the application based on the meta-data signature mapped to the configuration of software components, the version being customized to the particular mobile device; and
communicating, by the processor, the version of the application to the particular mobile user device.
2. A method as recited in claim 1 , wherein the device configuration information comprises carrier information for the particular mobile user device.
3. A method as recited in claim 1 , wherein the device configuration information comprises a feature of the particular mobile user device.
4. A method as recited in claim 1 , wherein the device configuration information comprises a specification of a resource available on the particular mobile user device.
5. A method as recited in claim 1 , wherein the version of the application comprises a customized compiled executable file customized for execution on the particular mobile device based on the device configuration information.
6. A method as recited in claim 1 , wherein the device configuration information comprises an error message relating to a failed prior deployment of the application.
7. A method as recited in claim 1 , wherein the device configuration information comprises application state information from a prior version of the application.
8. A method as recited in claim 1 , further comprising:
determining, by the processor in response to receiving the request, if the mobile user device is known or unknown based on existence of an entry for a meta-data signature of the mobile user device in a device database;
loading, by the processor, a corresponding device template that comprises the configuration of software components predetermined as currently optimal for the mobile user device if it is determined that the mobile user device is known; and
adding, by the processor, the configuration of software components based on the device configuration if it is determined that the mobile user device is unknown.
9. The method of claim 1 , wherein receiving the device configuration information further comprises:
assigning, by the processor, a user identifier for the user of the mobile device;
transmitting, by the processor, a customized pointer for the application to be installed on the mobile user device, the customized pointer comprising the user identifier.
10. A system comprising:
a processor; and
a memory coupled with the processor, wherein the memory comprising instructions for:
receiving a request for installing a version of an application for a user of a particular mobile user device;
receiving device configuration information that includes one or more features of the particular mobile user device from a device database, specifications from the device database mapping to one or more components in an application component data store;
parsing the device configuration information according to the one or more features of the particular mobile user device;
creating a meta-data signature from a subset of the parsed device configuration information;
retrieving in response to the request, a configuration of software components from the application component data store, the configuration of software components is selected from multiple software components that can be assembled into variations of the application, the selection based at least in part on mapping the meta-data signature created from the subset of the parsed device configuration information to the configuration of software components;
compiling the configuration of software components into the version of the application based on the meta-data signature mapped to the configuration of software components, the current application version being customized to the particular mobile device; and
communicating the version of the application to the mobile user device.
11. A system as recited in claim 10 , wherein the device configuration information comprises carrier information for the particular mobile user device.
12. A system as recited in claim 10 , wherein the device configuration information comprises a model name for the particular mobile user device.
13. A system as recited in claim 10 , wherein the device configuration information comprises a user identifier for the particular mobile user device.
14. A system as recited in claim 10 , wherein the device configuration information comprises user credentials of a user with access to the particular mobile user device.
15. A system as recited in claim 10 , wherein the device configuration information comprises a feature of the particular mobile user device.
16. A system as recited in claim 10 , wherein the device configuration information comprises a specification of a resource available on the particular mobile user device.
17. A system as recited in claim 10 , wherein the version of the application comprises a customized compiled executable file customized for execution on the particular mobile device based on the device configuration information.
18. A system as recited in claim 10 , wherein the device configuration information comprises an error message relating to a failed prior deployment of the application.
19. A system as recited in claim 10 , wherein the device configuration information comprises application state information from a prior version of the application.
20. A system as recited in claim 10 , wherein the device configuration information comprises a meta-data signature of the particular mobile user device.
21. A non-transitory computer readable-medium comprising processor-executable instructions for:
receiving a request for installing a version of an application for a user of a particular mobile user device;
receiving device configuration information that includes one or more features of the particular mobile user device from a device database, specifications from the device database mapping to one or more components in an application component data store;
parsing the device configuration information according to the one or more features of the particular mobile user device;
creating a meta-data signature from a subset of the parsed device configuration information;
retrieving in response to the request, a configuration of software components from the application component data store, the configuration of software components is selected from multiple software components that can be assembled into variations of the application, the selection based at least in part on mapping the meta-data signature created from the subset of the parsed device configuration information to the configuration of software components;
compiling the configuration of software components into the version of the application based on the meta-data signature mapped to the configuration of software components, the version being customized to the particular mobile device; and
communicating the version of the application to the particular mobile user device.