Abstract: In some examples, dynamic responsive form creation may include obtaining, in a live environment and for a form, an indication of a modification to a field of the form. A modification to a schema may be determined in the live environment and based on the indication of the modification to the field of the form. A transformed schema may be generated based on transformation, in the live environment, of the modification to the schema. The transformed schema may be in a format that is usable to modify the form. An input associated with the field may be obtained in the live environment and based on a modified form generated from the transformed schema. A determination may be made, in the live environment, as to whether the input is valid by analyzing a validation associated with the field.

Abstract: Techniques are described herein that are capable of modeling a lifetime of a hybrid software application using an application manifest. For instance, workflows and input-output information may be received (e.g., from an independent software vendor). The workflows are configured to implement respective heterogeneous software products that are included in a hybrid software application. The input-output information specifies inputs of the heterogeneous software products and a mapping between output(s) of first heterogeneous software product(s) and input(s) of second heterogeneous software product(s). Operations that are to be performed to execute the workflows are determined based at least in part on the inputs and the mapping. A lifetime of the hybrid software application is modeled by generating an application manifest that defines the lifetime based at least in part on the operations.

Abstract: Techniques are described herein that are capable of modeling a lifetime of a hybrid software application using an application manifest. For instance, workflows and input-output information may be received (e.g., from an independent software vendor). The workflows are configured to implement respective heterogeneous software products that are included in a hybrid software application. The input-output information specifies inputs of the heterogeneous software products and a mapping between output(s) of first heterogeneous software product(s) and input(s) of second heterogeneous software product(s). Operations that are to be performed to execute the workflows are determined based at least in part on the inputs and the mapping. A lifetime of the hybrid software application is modeled by generating an application manifest that defines the lifetime based at least in part on the operations.

Abstract: Techniques are described herein that are capable of modeling a lifetime of a hybrid software application using an application manifest. For instance, workflows and input-output information may be received (e.g., from an independent software vendor). The workflows are configured to implement respective heterogeneous software products that are included in a hybrid software application. The input-output information specifies inputs of the heterogeneous software products and a mapping between output(s) of first heterogeneous software product(s) and input(s) of second heterogeneous software product(s). Operations that are to be performed to execute the workflows are determined based at least in part on the inputs and the mapping. A lifetime of the hybrid software application is modeled by generating an application manifest that defines the lifetime based at least in part on the operations.

Abstract: A development environment provides warnings based on one or more application categories set for an application. Each warning has a trigger threshold and a warning action. Different application categories have different warnings. The development environment proactively tests for trigger conditions and provides triggered warnings within a workflow that includes application designing, code editing, building, and running. For instance, a Social Networking application whose start-up time is greater than desired for Social Networking applications will trigger a warning. Password Manager or Finance applications that should use a more secure approach to store user data will trigger a warning not given to applications in other categories. A News application may trigger a warning from the development environment that application content is not easily readable if a user switches to a light color theme on a device. The application category is selected by the developer or set proactively by the development environment.

Abstract: A JIT (Just-In-Time) compiler performs dual-mode code generation by determining whether an application has opted-in to SIMD (Single Instruction Multiple Data) code generation both at JIT-time and at runtime. The application may select the code generation mode by identifying whether it has opted-in to SIMD code generation. As a result, the underlying implementation guarantees application compatibility by allowing the application to select the code generation mode. Additionally, applications have the ability to select into different code generation modes during concurrent execution.

Abstract: A development environment simulates conditions combining device states, events, hardware configurations, and usage scenarios, and applies specific rating criteria to arrive at individual quality parameter ratings. Ratings are provided for quality parameters such as user experience, cost awareness, battery friendliness, responsiveness, global readiness, device independence, application stability. For example, battery friendliness depends on criteria such as battery life in a specified usage scenario, whether unused peripherals are powered, whether application program interfaces designated as power-hungry are avoided, whether darker color themes can be chosen over lighter colors, and whether batching is used for network data communications. Some rating criteria are application-category-specific. For example, security is rated differently for a Finance application than a Music application.

Abstract: A development environment provides warnings based on one or more application categories set for an application. Each warning has a trigger threshold and a warning action. Different application categories have different warnings. The development environment proactively tests for trigger conditions and provides triggered warnings within a workflow that includes application designing, code editing, building, and running. For instance, a Social Networking application whose start-up time is greater than desired for Social Networking applications will trigger a warning. Password Manager or Finance applications that should use a more secure approach to store user data will trigger a warning not given to applications in other categories. A News application may trigger a warning from the development environment that application content is not easily readable if a user switches to a light color theme on a device. The application category is selected by the developer or set proactively by the development environment.

Abstract: A JIT (Just-In-Time) compiler performs dual-mode code generation by determining whether an application has opted-in to SIMD (Single Instruction Multiple Data) code generation both at JIT-time and at runtime. The application may select the code generation mode by identifying whether it has opted-in to SIMD code generation. As a result, the underlying implementation guarantees application compatibility by allowing the application to select the code generation mode. Additionally, applications have the ability to select into different code generation modes during concurrent execution.