Abstract: The number, popularity, sophistication, etc. of mobile applications have grown dramatically with the rise of smartphones, tablets, and other such devices. Alternatives to native application development, including approaches such as hybrid application development which may employ among other things a container paradigm, inter alia address various of the drawbacks associated with native application development. A flexible, extensible, and dynamically configurable Feature Vector (FV) facility addresses one challenge with approaches such as hybrid application development—controlling an application's access to features (e.g., functions, methods, resources, etc.) and the efficient administration, management, etc. same.

Abstract: A method and system displaying a plurality of visualizations at a portable electronic device is described. Initially a data presentation application executing at the portable electronic device renders a plurality of visualizations based on a user interface (UI) visualization file. A plurality of screenshots are captured corresponding to the rendered plurality of visualizations. Next a plurality of visualization images are generated by rendering the visualization screenshots at one surface of the plurality of visualizations and metadata related to the data on another surface of the plurality of visualization images. Finally, the generated plurality of visualization images are displayed at a user interface of the portable electronic device.

Abstract: A server system may include a request handler and a storage. The request handler may receive at least one request from a program on a user side. The storage may include a first cache and a second cache, storing data in format directly compatible to the program. The first cache stores only data matching to a server. If the at least one request corresponds to a change to the data from the program, then the second cache stores the at least one request and the request handler sends the at least one request to the server for updating the change.

Abstract: The number, popularity, sophistication, etc. of mobile applications have grown dramatically with the rise of smartphones, tablets, and other such devices. Alternatives to native application development, including approaches such as hybrid application development which may employ among other things a container paradigm, inter alia address various of the drawbacks associated with native application development. A flexible, extensible, and dynamically configurable Feature Vector (FV) facility addresses one challenge with approaches such as hybrid application development—controlling an application's access to features (e.g., functions, methods, resources, etc.) and the efficient administration, management, etc. same.

Abstract: In an example embodiment, extending an application distributed to a plurality of devices may be accomplied by receiving one or more configuration files. Then the configuration files on a platform server. Then the application may be distributed to the plurality of devices, the application containing code performing one or more calls to the one or more configuration files. Then an update to the one or more configuration files may be received. Then the update to the one or more configuration files may be stored on the platform, thereby altering the application distributed to the plurality of devices without recompiling the application.

Abstract: A server system may include a request handler and a storage. The request handler may receive at least one request from a program on a user side. The storage may include a first cache and a second cache, storing data in format directly compatible to the program. The first cache stores only data matching to a server. If the at least one request corresponds to a change to the data from the program, then the second cache stores the at least one request and the request handler sends the at least one request to the server for updating the change.

Abstract: In an example embodiment, a container is downloaded, the container being an application natively executable by a first operating system of the user device, the container including: a container service including one or more libraries of functions designed by a container designer to natively operate on the first operating system; a browser; container metadata defining functions of the application, the functions compatible with the container service for the first operating system and also compatible with a container service for a second operating system; and a plug-in including one or more additional libraries of functions designed by an entity other than the container designer to perform additional native operations on the first operating system. Then, the container metadata can be executed using the browser, causing function calls to the container service and plug-in and thus controlling native functions of the user device.

Abstract: In an example embodiment, a mobile application framework is added to a metadata-driven application. The mobile application framework includes generic libraries having one or more references to one or more configuration files stored on a platform server. Then the one or more configuration files can be updated to include one or more tiles, each tile comprising a user interface element or screen view, each tile being either a primitive tile or a tile embedding other nested tiles within it, thereby updating the metadata-driven mobile application without recompiling it.

Abstract: In an example embodiment, a mobile application framework is provided. This includes a core component configured to expose one or more application program interfaces (APIs) that initialize the mobile application framework when executed. This also includes a user interface component configured to encapsulate a metadata-driven view for the mobile application. This also includes a data component configured to provide bindings to one or more business objects defining data for the mobile application. This also includes a configuration component configured to read and parse metadata in the one or more configuration files and transform the metadata to constructs native to the mobile application.

Abstract: In an example embodiment, a container is downloaded, the container being an application natively executable by a first operating system of the user device, the container including: a container service including one or more libraries of functions designed by a container designer to natively operate on the first operating system; a browser; container metadata defining functions of the application, the functions compatible with the container service for the first operating system and also compatible with a container service for a second operating system; and a plug-in including one or more additional libraries of functions designed by an entity other than the container designer to perform additional native operations on the first operating system. Then, the container metadata can be executed using the browser, causing function calls to the container service and plug-in and thus controlling native functions of the user device.

Abstract: In an example embodiment, a mobile application framework is added to a metadata-driven application. The mobile application framework includes generic libraries having one or more references to one or more configuration files stored on a platform server. Then the one or more configuration files can be updated to include one or more tiles, each tile comprising a user interface element or screen view, each tile being either a primitive tile or a tile embedding other nested tiles within it, thereby updating the metadata-driven mobile application without recompiling it.

Abstract: In an example embodiment, a mobile application framework is provided. This includes a core component configured to expose one or more application program interfaces (APIs) that initialize the mobile application framework when executed. This also includes a user interface component configured to encapsulate a metadata-driven view for the mobile application. This also includes a data component configured to provide bindings to one or more business objects defining data for the mobile application. This also includes a configuration component configured to read and parse metadata in the one or more configuration files and transform the metadata to constructs native to the mobile application.

Abstract: In an example embodiment, extending an application distributed to a plurality of devices may be accomplied by receiving one or more configuration files. Then the configuration files on a platform server. Then the application may be distributed to the plurality of devices, the application containing code performing one or more calls to the one or more configuration files. Then an update to the one or more configuration files may be received. Then the update to the one or more configuration files may be stored on the platform, thereby altering the application distributed to the plurality of devices without recompiling the application.

Abstract: A method includes determining an initial experience-level of a user based on an initial usage of an application by the user, where the application includes a plurality of selectable features, selecting one or more first features from the selectable features to provide to the user, where the selected first features are based on the initial experience-level of the user, and providing a first user interface to the application to enable the user to utilize the first features. A subsequent experience-level of the user is determined based on the user's interactions with the one or more first features, one or more second features are selected from the selectable features to provide to the user, where the selected second features are based on the subsequent experience-level of the user, and a second user interface to the application is provided to enable the user to utilize the second features.

Abstract: A computer-implemented method includes providing one or more initial questions, including a first question, selected from a database of possible questions, where the one or more provided questions are selected based on a sales phase of a sales opportunity. A first response to the first question is received, and one or more additional questions are provided, where each additional question is based at least in part on the first response to the first question. Additional responses to the additional questions are received, and a sales strategy associated with the sales phase of the sales opportunity is provided, where the sales strategy is based at least in part on the first response and the one or more additional responses and the sales strategy includes one or more actions to perform. The one or more included actions are selected from a database of possible actions based on their anticipated ability to increase a likelihood of success of the sales opportunity.

Abstract: A method includes maintaining a database that includes a physical schema that includes a plurality of tables. The tables include table definitions and are populated with data that is modifiable independent of the table definitions. A table of the database that includes non-transactional data is identified, and a storage view of at least a subset of non-transactional data of the identified table is defined, where the storage view includes a storage view definition that includes the non-transactional data and where a modification of the non-transactional data that populates the storage view depends on modifying the storage view definition. Finally, the table in the physical schema is replaced with the storage view.

Abstract: A method includes determining an initial experience-level of a user based on an initial usage of an application by the user, where the application includes a plurality of selectable features, selecting one or more first features from the selectable features to provide to the user, where the selected first features are based on the initial experience-level of the user, and providing a first user interface to the application to enable the user to utilize the first features. A subsequent experience-level of the user is determined based on the user's interactions with the one or more first features, one or more second features are selected from the selectable features to provide to the user, where the selected second features are based on the subsequent experience-level of the user, and a second user interface to the application is provided to enable the user to utilize the second features.

Abstract: A computer-implemented method includes providing one or more initial questions, including a first question, selected from a database of possible questions, where the one or more provided questions are selected based on a sales phase of a sales opportunity. A first response to the first question is received, and one or more additional questions are provided, where each additional question is based at least in part on the first response to the first question. Additional responses to the additional questions are received, and a sales strategy associated with the sales phase of the sales opportunity is provided, where the sales strategy is based at least in part on the first response and the one or more additional responses and the sales strategy includes one or more actions to perform. The one or more included actions are selected from a database of possible actions based on their anticipated ability to increase a likelihood of success of the sales opportunity.