Customized ready-to-go componentized application definitions

1. A system, comprising:

a memory; and

a processor programmed to:

receive a request to invoke a text-list definition of a componentized application stored within the memory, where the text-list definition of the componentized application identifies a collection of different listed independent application sub-components specified by a user to be executed as a set;

create a componentized user interface with a different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application; and

independently access the different listed independent application sub-components based upon user inputs received in association with the respective different user interface component associated with each of the different listed independent application components within the text-list definition of the componentized application.

2. The system of claim 1 , further comprising a display device, and where, in being programmed to create the componentized user interface with the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application, the processor is programmed to:

determine available sub-component interface features of each of the different listed independent application sub-components;

create a set of user interface components that each provides an interface to the determined available sub-component interface features of one of the different listed independent application sub-components;

organize the created set of user interface components within a componentized graphical interface display component; and

display, on the display device, the componentized graphical interface display component comprising the organized created set of user interface components.

3. The system of claim 1 , where, in being programmed to create the componentized user interface with the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application, the processor is programmed to:

prioritize a graphical user interface layout location of the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application based upon a position of an identifier of each of the different listed independent application sub-components within the text-list definition of the componentized application.

4. The system of claim 1 , where the text-list definition of the componentized application comprises an indication of a sequence of invocation of at least two of the different listed independent application sub-components, where a first independent application sub-component is specified to invoke a second independent application sub-component, and where:

in being programmed to create the componentized user interface with the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application, the processor is programmed to:

create a first componentized user interface comprising a first user interface component associated with the first independent application sub-component indicated in the sequence of invocation specified to invoke the second independent application sub-component; and

create, in response to detecting completion of a user interaction with the first user interface component, a second componentized user interface comprising a second user interface component associated with the second independent application sub-component identified in the sequence of invocation.

5. The system of claim 1 , where the processor is further programmed to define the text-list definition of the componentized application, comprising being programmed to:

provide a listing of available independent application sub-components to the user, where the available independent application sub-components are independently executable and provide distinct application features;

receive a user selection of a sub-set of the listed available independent application sub-components;

create the text-list definition of the componentized application comprising text identifiers of the selected sub-set of the listed available independent application sub-components; and

store the created text-list definition of the componentized application within the memory.

6. The system of claim 1 , where the processor is further programmed to determine between downloading the different listed independent application sub-components for local execution and executing remote versions of the different listed independent application sub-components; and where:

in response to determining to download the listed different independent application sub-components for local execution, the processor is programmed to:

download a device-specific implementation of each of the different listed independent application sub-components specified by the user within the text-list definition of the componentized application;

store the downloaded device-specific implementation of each of the different listed independent application sub-components within the memory; and

where, in being programmed to independently access the different listed independent application sub-components based upon the user inputs received in association with the respective different user interface component associated with each of the different listed independent application components within the text-list definition of the componentized application, the processor is programmed to:

independently access the downloaded device-specific implementation of each of the different listed independent application sub-components within the memory; and

in response to determining to not download the different listed independent application sub-components for local execution, the processor is programmed to:

identify within at least one remote storage location within a distributed network each of the different listed independent application sub-components specified by the user within the text-list definition of the componentized application; and

where, in being programmed to independently access the different listed independent application sub-components based upon the user inputs received in association with the respective different user interface component associated with each of the different listed independent application components within the text-list definition of the componentized application, the processor is programmed to:

independently access the different listed independent application sub-components within the at least one remote storage location within the distributed network.

7. A computer program product, comprising:

a non-transitory computer readable storage medium having computer readable program code embodied therewith, where the computer readable program code when executed on a computer causes the computer to:

receive a request to invoke a text-list definition of a componentized application, where the text-list definition of the componentized application identifies a collection of different listed independent application sub-components specified by a user to be executed as a set;

create a componentized user interface with a different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application; and

independently access the different listed independent application sub-components based upon user inputs received in association with the respective different user interface component associated with each of the different listed independent application components within the text-list definition of the componentized application.

8. The computer program product of claim 7 , where, in causing the computer to create the componentized user interface with the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application, the computer readable program code when executed on the computer causes the computer to:

determine available sub-component interface features of each of the different listed independent application sub-components;

create a set of user interface components that each provides an interface to the determined available sub-component interface features of one of the different listed independent application sub-components;

organize the created set of user interface components within a componentized graphical interface display component; and

display the componentized graphical interface display component comprising the organized created set of user interface components.

9. The computer program product of claim 7 , where, in causing the computer to create the componentized user interface with the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application, the computer readable program code when executed on the computer causes the computer to:

prioritize a graphical user interface layout location of the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application based upon a position of an identifier of each of the different listed independent application sub-components within the text-list definition of the componentized application.

10. The computer program product of claim 7 , where the text-list definition of the componentized application comprises an indication of a sequence of invocation of at least two of the different listed independent application sub-components, where a first independent application sub-component is specified to invoke a second independent application sub-component, and where:

in causing the computer to create the componentized user interface with the different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application, the computer readable program code when executed on the computer causes the computer to:

create a first componentized user interface comprising a first user interface component associated with the first independent application sub-component indicated in the sequence of invocation specified to invoke the second independent application sub-component; and

create, in response to detecting completion of a user interaction with the first user interface component, a second componentized user interface comprising a second user interface component associated with the second independent application sub-component identified in the sequence of invocation.

11. The computer program product of claim 7 , where the computer readable program code when executed on the computer further causes the computer to define the text-list definition of the componentized application, comprising causing the computer to:

provide a listing of available independent application sub-components to the user, where the available independent application sub-components are independently executable and provide distinct application features;

receive a user selection of a sub-set of the listed available independent application sub-components;

create the text-list definition of the componentized application comprising text identifiers of the selected sub-set of the listed available independent application sub-components; and

store the created text-list definition of the componentized application.

12. The computer program product of claim 7 , where the computer readable program code when executed on the computer further causes the computer to:

download a device-specific implementation of each of the different listed independent application sub-components specified by the user within the text-list definition of the componentized application; and

store the downloaded device-specific implementation of each of the different listed independent application sub-components within a local storage; and

where, in causing the computer to independently access the different listed independent application sub-components based upon the user inputs received in association with the respective different user interface component associated with each of the different listed independent application components within the text-list definition of the componentized application, the computer readable program code when executed on the computer causes the computer to:

independently access the downloaded device-specific implementation of each of the different listed independent application sub-components within the local storage.

13. The computer program product of claim 7 , where the computer readable program code when executed on the computer further causes the computer to:

identify within at least one remote storage location within a distributed network each of the different listed independent application sub-components specified by the user within the text-list definition of the componentized application; and

where, in causing the computer to independently access the different listed independent application sub-components based upon the user inputs received in association with the respective different user interface component associated with each of the different listed independent application components within the text-list definition of the componentized application, the computer readable program code when executed on the computer causes the computer to:

independently access the different listed independent application sub-components within the at least one remote storage location within the distributed network.