Method for data type driven front-end rendering

Abstract

According to various embodiments, a computer-implemented method may include the following steps: receiving input data via a back-end user interface by a processor set, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of a front-end user interface; generating rendering instructions by the processor set based on the at least one prompt type and at least one associated response type; receiving a request to view the front-end user interface from a front-end platform by the processor set; and in response to receiving the request to view the front-end user interface, sending the rendering instructions to the front-end platform, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface.

Description

Background Technology

[0001] Various aspects of the present invention generally relate to systems and methods for rendering user interfaces (UIs) using computer program front-end development frameworks such as Model-View-Controller (MVC).

[0002] MVC can be used as a front-end development framework for creating and rendering UI. The architectural pattern associated with MVC provides low-level widgets that can be accessed by the user to construct the front-end UI and views, but whose code cannot be run by the rendering engine or processing engine. Summary of the Invention

[0003] In one aspect of the invention, there is a computer-implemented method comprising: receiving input data via a backend UI by a set of processors, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of a frontend UI; generating rendering instructions by the set of processors based on the at least one prompt type and at least one associated response type; receiving a request to view the frontend UI from a frontend platform by the set of processors; and in response to receiving the request to view the frontend UI, sending the rendering instructions to the frontend platform by the set of processors, wherein the rendering instructions cause the frontend platform to dynamically render the frontend UI.

[0004] In another aspect of the invention, there is a computer program product comprising one or more computer-readable storage media on which program instructions are commonly stored. The program instructions are executable to: receive input data via a back-end user interface, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of a front-end user interface; generate rendering instructions based on the at least one prompt type and at least one associated response type; receive a request from a front-end platform to view the front-end user interface; and, in response to receiving the request to view the front-end user interface, send the rendering instructions to the front-end platform, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface.

[0005] In another aspect of the invention, there is a system comprising: a processor set, one or more computer-readable storage media, and program instructions commonly stored on the one or more computer-readable storage media. The program instructions are executable to: receive input data via a back-end user interface, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of a front-end user interface; generate rendering instructions based on the at least one prompt type and at least one associated response type; receive a request from a front-end platform to view the front-end user interface; and, in response to receiving the request to view the front-end user interface, send the rendering instructions to the front-end platform, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface. Attached Figure Description

[0006] Preferred embodiments of the invention will now be described by way of example only with reference to the following figures: Figure 1 A computing environment according to an embodiment of the present invention is described.

[0007] Figure 2A A block diagram of an exemplary computing environment according to an embodiment of the present invention is shown.

[0008] Figure 2B A block diagram of an exemplary computing environment according to an embodiment of the present invention is shown.

[0009] Figure 3 A flowchart of a computer-implemented method according to an embodiment of the present invention is shown.

[0010] Figure 4 A flowchart of a computer-implemented method according to an embodiment of the present invention is shown.

[0011] Figure 5 A diagram illustrating a computer-implemented method according to an embodiment of the present invention is shown.

[0012] Figure 6 A diagram illustrating a computer-implemented method according to an embodiment of the present invention is shown.

[0013] Figure 7 A diagram illustrating a computer-implemented method according to an embodiment of the present invention is shown.

[0014] Figure 8 A diagram illustrating a computer-implemented method according to an embodiment of the present invention is shown.

[0015] Figure 9 A diagram illustrating a computer-implemented method according to an embodiment of the present invention is shown.

[0016] Figure 10 A diagram illustrating a computer-implemented method according to an embodiment of the present invention is shown.

[0017] Figure 11 A flowchart of a program executable file according to an embodiment of the present invention is shown. Detailed Implementation

[0018] Embodiments of the present invention generally relate to a method for rendering a front-end UI for mobile or web browser applications, wherein the UI seen by the user is dynamically rendered based on tasks or content and rendering instructions. This system and method enable updates to be performed on all instances of the application without requiring developers to distribute new application files for users to install or update to experience new application features.

[0019] In one embodiment, the system may include front-end UI dynamic rendering code, where web page templates and UI view widgets can be built within a front-end container. The UI presented to the user via a computing device display can be dynamically rendered by at least one processor based on data types and associated rendering instructions from the system. New data types and rendering instructions can be created and transmitted to the system, for example, via a network, without changing the source code or rebuilding the front-end application.

[0020] MVC is a common front-end development framework for creating UIs, but the architectural pattern associated with MVC provides user-accessible low-level widgets for constructing front-end UIs and views. For security reasons, data and code can be strictly separated within MVC. If data contains code, the rendering or processing engine may not run that code.

[0021] Building the front-end UI is a labor-intensive process for developers who need to code for individual pages, such as in use cases like medical questionnaires or tasks. The implementation of the exposed system allows for use cases that extend the application of data collection tasks, such as deploying new healthcare questionnaires, tasks, or tests during clinical research, or presenting new analytics dashboards in financial reporting.

[0022] In embodiments, the disclosed system can be configured to allow pre-identified "super users," such as administrator users or users wishing to build a front-end UI, to increase the flexibility of UI generation and extend the system's useful life by allowing super users to provide code snippets as part of their data content when generating the UI. In this way, the system can include computer product programming to facilitate the generation of front-end UI layout templates and dynamically constructed widgets based on both non-code input and code snippet submissions. In embodiments, the system allows rendering different types of user interaction components to the UI, including input or output components such as radio buttons, text input, and video or audio recordings, not just context, text, or image components.

[0023] In embodiments, a method for dynamically rendering an interface to a front-end user may include receiving task prompts (such as prompt types) and associated input prompts (such as answer types) from a back-end UI (e.g., task visual response options, such as single or multiple choice questions, slider selection, and text, image, audio, or video prompts). The method may include receiving a request to view the interface on a device and dynamically rendering different types of user interaction components.

[0024] In an embodiment, the method for dynamically rendering an interface to a front-end user may include receiving a request to view a task on the interface; displaying a question prompt to the front-end user; receiving an answer to the question prompt; customizing the interface by rendering different types of user interaction components that can be used for input or output (radio buttons, text input, or audio recording) instead of simply delivering context, text, or images based on the task and answer; detecting the super user's credentials on the back-end; detecting whether the front-end user is using a web-based interface that supports JavaScript / CSS, or a mobile interface, wherein if the front-end user is using a web-based interface, the back-end processes the code and modifies the payload to include appropriate JavaScript / CSS sent to the front-end, and if the front-end user is using a mobile platform, using a cross-platform development framework to allow the super user to write their code snippets in JavaScript / CSS; and compiling the code snippets in a format that the front-end rendering platform can correctly process.

[0025] As a non-limiting example, cross-platform development frameworks can include software applications developed using a single codebase that are compatible with multiple different operating systems, such as various mobile device operating systems.

[0026] In this embodiment, the front-end UI elements (such as interactive components) of the software platform visualize an end-to-end data pipeline that moves data through stages, including but not limited to data ingestion, data storage, data analysis, and data access. The software platform can connect to mobile applications, wearable devices, or Internet of Things (IoT) devices, such as via a wireless network, to collect and ingest data into a secure database. The rendering of the front-end UI (such as those displayed on computing devices in mobile applications or web browser applications) can be dynamically performed based on content and rendering instructions provided by the system. This enables updates to instances of the software application (including UI updates) without requiring developers to distribute new application files to users, which would then require consumer users to install or update to experience the new UI features.

[0027] In this embodiment, a backend user (such as a superuser) with little or no development or software coding background can control the content of tasks, surveys, or questionnaires delivered to all users (including those exposed to and interacting with the frontend UI). Backend users can create task visualization elements within the UI by selecting from a list of various task visualization response options, including task prompts and associated input prompts (e.g., question prompts and answer prompts), such as single-choice or multiple-choice questions; slider selection; text, image, audio, or video prompts; or the like.

[0028] In this embodiment, backend users familiar with software coding or development can use code snippets to control the dynamic rendering of frontend UI elements that may not be supported by various task visualization response option lists.

[0029] According to the embodiments, and as follows Figure 3 and Figure 5-9 As shown, dynamic rendering may include converting data from a first format (such as text input) into a structured format that conforms to the JavaScript Object Notation (JSON) standard. The system can receive superuser input that identifies task prompts and input suggestions to be dynamically rendered in the UI display on the user's device.

[0030] According to embodiments, dynamic rendering may include converting input data (e.g., text input) into a JSON-compatible structure that conforms to JSON syntax rules. This process may include steps such as data transformation, serialization, or validation. Dynamic rendering may also include sending JSON-formatted input data (e.g., in the form of rendering instructions) to a front-end platform, which can render predefined widgets on the display in the front-end UI based on task prompts and associated input hints entered by the superuser.

[0031] According to an embodiment, dynamic rendering may include the use of predefined question types in a pre-built widget. The pre-built widget can determine how to display task hints and input suggestions when dynamically rendered on the front-end UI. Superuser input can be converted to the JSON standard and parsed into the pre-built widget through steps such as tokenization, analysis, extraction, error handling, transformation, or validation.

[0032] According to the embodiments, and as follows Figure 4 and Figure 10 As shown, dynamic rendering may include receiving at least one code snippet as input for generating a UI that includes task hints and input suggestions. A cross-platform development framework can be utilized to allow the superuser to write their code snippets in JavaScript, CSS, HTML, or Objective-C. The system can determine whether the code snippet is written in JavaScript, CSS, HTML, or Objective-C; format the code snippet as JSON; and compile the code snippet. For example, the superuser can enter a code snippet related to a specific task hint within the backend UI, which can be sent to a frontend platform that can render the code snippet in a web browser as a user-facing UI displayed on the computing device's screen.

[0033] In this embodiment, the code snippet can be used by a superuser on a web browser-based front-end platform, including encoding the custom widget using JavaScript, CSS, HTML, or Objective-C. The system can process the superuser's code snippet and modify the payload to include the provided code snippet, then send the modified payload to the front-end platform and render the custom widget in the UI based on the code snippet in the web browser.

[0034] In this embodiment, the code snippets can be used by the superuser in a mobile software application platform or mobile interface, including encoding custom widgets using JavaScript, CSS, HTML, or Objective-C. The backend service can receive data from the superuser input, package it together with rendering instructions, compile the information on demand according to the frontend type, and then distribute the packaged render-ready payload to the frontend. The system can perform a backend service check on the code snippet format to determine superuser credentials or verify the code snippet format, and send the code snippet to the frontend platform, where the frontend platform can compile the code snippet and render the custom widget in the mobile frontend platform. The code snippets can be input in JavaScript, CSS, or HTML format, allowing them to be formatted into rendering instructions by the backend service and directly processed by the user-facing web browser to generate a user-facing UI.

[0035] In an embodiment, a computer-implemented method may include: receiving input data, including at least one prompt type and at least one associated response type, via a backend UI by a processor set, wherein the at least one prompt type and at least one associated response type define aspects of the frontend UI; generating rendering instructions by the processor set based on the at least one prompt type and at least one associated response type; receiving a request to view the frontend UI from a frontend platform by the processor set; and, in response to receiving the request to view the frontend UI, sending rendering instructions to the frontend platform, wherein the rendering instructions cause the frontend platform to dynamically render the frontend UI. Embodiments of the present invention improve the process of building a frontend UI by allowing superusers to provide code snippets as part of their data content during UI generation or by dynamically constructing widgets based on both frontend UI layout templates and non-code input, thereby resulting in increased flexibility in UI generation and extended system lifespan.

[0036] In one embodiment, the computer-implemented method may include generating rendering instructions that convert the at least one prompt type and the at least one associated response type into JavaScript Object Notation (JSON) formatted input data. Embodiments of the present invention improve the process of building front-end UIs by systematically formatting prompt types and response types as JSON input data without requiring the user to have coding language knowledge.

[0037] In one embodiment, the computer-implemented method may include generating rendering instructions that parse JSON-formatted input data into at least one pre-built widget. Embodiments of the present invention improve the process of building a front-end UI by systematically creating pre-built widgets based on JSON input data.

[0038] In one embodiment, the computer-implemented method may include sending rendering instructions to send at least one pre-built widget to a front-end platform, wherein the at least one pre-built widget causes the front-end platform to dynamically render a front-end user interface. Embodiments of the present invention improve the process of building a front-end UI by rendering pre-built widgets based on JSON input data.

[0039] In embodiments, the computer-implemented method may include: detecting superuser credentials at the backend user interface; and detecting whether the frontend user is using a web-based interface or a mobile interface that supports at least one language selected from the group consisting of Cascading Style Sheets (CSS), JavaScript, and Hypertext Markup Language (HTML). Embodiments of the present invention improve the process of building the frontend UI by automatically identifying web-based user interfaces in order to correctly render the UI.

[0040] In embodiments, a computer-implemented method may include: in response to detecting that a web-based interface supports at least one language selected from the group consisting of CSS, JavaScript, and HTML; receiving at least one code snippet as user input; parsing the at least one code snippet; modifying the at least one code snippet into JSON format; and wherein sending rendering instructions to a front-end platform includes sending the modified code snippet to the front-end platform, wherein the modified code snippet causes the front-end platform to dynamically render the front-end user interface. Embodiments of the present invention improve the process of building a front-end UI by allowing superusers to provide code snippets as part of their data content when generating the UI or by generating it based on a front-end UI layout template of a web-based interface.

[0041] In an embodiment, a computer-implemented method may include: in response to detecting that a web-based interface supports a mobile interface: performing at least one backend service check on at least one code snippet; wherein sending rendering instructions includes sending the at least one code snippet to a frontend platform; and compiling the at least one code snippet, wherein the at least one code snippet causes the frontend platform to dynamically render the frontend user interface. Embodiments of the present invention improve the process of building a frontend UI by compiling information on demand according to the web-based interface type and distributing code snippets as packaged render-ready payloads to the frontend.

[0042] In embodiments, the computer-implemented method may include receiving at least one code snippet in JavaScript or CSS via a cross-platform development framework. Embodiments of the invention improve the process of building front-end UIs by allowing users to use a single codebase that works compatible with several different operating systems.

[0043] In embodiments, a computer-implemented method may include: rendering instructions causing a front-end platform to dynamically render a front-end user interface by configuring at least one action to be selected from a group of various different types of user interaction components that include receiving at least one input and generating at least one output. Embodiments of the present invention improve the process of generating a UI that includes template and widget generation to receive user input.

[0044] In embodiments, a computer program product may include one or more computer-readable storage media, on which program instructions are collectively stored. The program instructions are executable to: receive input data via a back-end user interface, including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of the front-end user interface; generate rendering instructions based on the at least one prompt type and at least one associated response type; receive a request from a front-end platform to view the front-end user interface; and, in response to receiving the request to view the front-end user interface, send rendering instructions to the front-end platform, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface. Embodiments of the present invention improve the process of building a front-end UI by allowing superusers to provide code snippets as part of their data content during UI generation or by dynamically constructing widgets based on both front-end UI layout templates and non-code input, thereby resulting in increased flexibility in UI generation and extended system lifespan.

[0045] In one embodiment, a computer program product is disclosed, wherein generating rendering instructions includes converting the at least one prompt type and the at least one associated response type into input data formatted in JavaScript Object Notation (JSON). Embodiments of the invention improve the process of building front-end UIs by systematically formatting prompt types and response types as JSON input data without requiring the user to have coding language knowledge.

[0046] In one embodiment, a computer program product is disclosed, wherein generating rendering instructions includes parsing JSON-formatted input data into at least one pre-built widget. Embodiments of the invention improve the process of constructing a front-end UI by systematically creating pre-built widgets based on JSON input data.

[0047] In one embodiment, a computer program product is disclosed, wherein sending rendering instructions includes sending at least one pre-built widget to a front-end platform, wherein the at least one pre-built widget causes the front-end platform to dynamically render a front-end user interface. Embodiments of the present invention improve the process of constructing a front-end UI by rendering pre-built widgets based on JSON input data.

[0048] In embodiments, the computer program product may include detecting superuser credentials at the back-end user interface; and detecting whether the front-end user is using a web-based interface or a mobile interface, the web-based interface supporting at least one language selected from the group including Cascading Style Sheets (CSS), JavaScript, and Hypertext Markup Language (HTML). Embodiments of the present invention improve the process of constructing the front-end UI by automatically identifying web-based user interfaces to correctly render the UI.

[0049] In embodiments, a computer program product may include: in response to detecting that a web-based interface supports at least one language selected from the group including CSS, JavaScript, and HTML, an executable program for receiving at least one code snippet as user input; parsing the at least one code snippet; modifying the at least one code snippet into JSON format; and wherein sending rendering instructions to a front-end platform includes sending the modified code snippet to the front-end platform, wherein the modified code snippet causes the front-end platform to dynamically render the front-end user interface. Embodiments of the invention improve the process of constructing a front-end UI by allowing superusers to provide code snippets as part of their data content when generating the UI, or by generating a front-end UI layout template based on a web-based interface.

[0050] In an embodiment, a computer program product may include: in response to detecting that a web-based interface supports a mobile interface: performing at least one backend service check of at least one code snippet; wherein sending rendering instructions includes sending the at least one code snippet to a frontend platform; and compiling the at least one code snippet, wherein the at least one code snippet causes the frontend platform to dynamically render a frontend user interface. Embodiments of the present invention improve the process of constructing a frontend UI by compiling information on demand according to the type of web-based interface and distributing code snippets as packaged render-ready payloads to the frontend.

[0051] In embodiments, the computer program product may include program instructions executable to receive at least one code snippet in at least one of JavaScript or CSS via a cross-platform development framework. Embodiments of the invention improve the process of constructing front-end UIs by allowing users to use a single codebase that works compatible with a variety of different operating systems.

[0052] In embodiments, a computer program product may include rendering instructions that cause a front-end platform to dynamically render a front-end user interface by causing the front-end platform to dynamically render a front-end user interface by selecting at least one action from a variety of different types of user interaction components, including receiving at least one input and generating at least one output. Embodiments of the present invention improve the process of generating a UI that includes template and widget generation to receive user input.

[0053] In an embodiment, a system may include a processor set, one or more computer-readable storage media, and program instructions co-stored on the one or more computer-readable storage media. The program instructions are executable to: receive input data via a back-end user interface, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of a front-end user interface; generate rendering instructions based on the at least one prompt type and at least one associated response type; receive a request from a front-end platform to view the front-end user interface; and in response to receiving the request to view the front-end user interface, send rendering instructions to the front-end platform, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface. Embodiments of the present invention improve the process of building a front-end UI by allowing superusers to provide code snippets as part of their data content during UI generation or by dynamically constructing widgets based on both front-end UI layout templates and non-code input, thereby resulting in increased flexibility in UI generation and extended system lifespan.

[0054] In one embodiment, the system can generate rendering instructions that include converting at least one prompt type and at least one associated response type into input data formatted in JavaScript Object Notation (JSON). Embodiments of the invention improve the process of building a front-end UI by allowing superusers to provide code snippets as part of their data content during UI generation, or by dynamically constructing widgets based on both front-end UI layout templates and non-code input, thereby resulting in increased flexibility in UI generation and extended system lifespan.

[0055] Various aspects of this disclosure are described through narrative text, flowcharts, block diagrams of computer systems, and / or block diagrams of machine logic included in embodiments of a computer program product (CPP). With respect to any flowchart, depending on the technology involved, operations may be performed in a different order than those shown in a given flowchart. For example, again depending on the technology involved, two operations shown in consecutive flowchart blocks may be performed in reverse order, as a single integrated step, simultaneously, or in a manner that at least partially overlaps in time.

[0056] Computer Program Product Embodiment (“CPP Embodiment” or “CPP”) is a term used in this disclosure to describe any group of one or more storage media (also referred to as “media”) commonly included in a group of one or more storage devices, said group of one or more storage devices commonly including machine-readable code corresponding to instructions and / or data for performing the computer operations specified in a given CPP claim. A “storage device” is any tangible device capable of holding and storing instructions for use by a computer processor. Without limitation, a computer-readable storage medium can be an electronic storage medium, a magnetic storage medium, an optical storage medium, an electromagnetic storage medium, a semiconductor storage medium, a mechanical storage medium, or any suitable combination of the foregoing. Some known types of storage devices that include these media include: magnetic disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), optical disc read-only memory (CD-ROM), digital universal disc (DVD), memory sticks, floppy disks, mechanical encoding devices (such as punched cards or pits / ridges formed on the main surface of the disk), or any suitable combination of the foregoing. As used in this disclosure, computer-readable storage media should not be construed as storing transient signals, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides, optical pulses through fiber optic cables, electrical signals transmitted through wires and / or other transmission media, etc. As those skilled in the art will understand, data typically moves at some occasional points in time during normal operation of the storage device (such as during access, defragmentation, or garbage collection), but this does not make the storage device transient, because the data is not transient when it is stored.

[0057] refer to Figure 1 The computing environment 100 includes examples of environments for executing at least some computer code (such as the dynamic UI rendering code of block 200) related to the execution of the methods of the present invention. In addition to block 200, the computing environment 100 includes, for example, a computer 101, a wide area network (WAN) 102, an end-user device (EUD) 103, a remote server 104, a public cloud 105, and a private cloud 106. In this embodiment, the computer 101 includes a processor set 110 (including processing circuitry 120 and a cache 121), a communication architecture 111, volatile memory 112, persistent storage device 113 (including an operating system 122 and block 200, as identified above), a peripheral device set 114 (including a user interface (UI) device set 123, a storage device 124, and an Internet of Things (IoT) sensor set 125), and a network module 115. The remote server 104 includes a remote database 130. Public cloud 105 includes gateway 140, cloud orchestration module 141, host physical machine set 142, virtual machine set 143, and container set 144.

[0058] Computer 101 can take the form of a desktop computer, laptop computer, tablet computer, smartphone, smartwatch or other wearable computer, mainframe computer, quantum computer, or any other form of computer or mobile device now known or to be developed in the future capable of running programs, accessing networks, or querying databases such as remote database 130. As is well known in the field of computer technology, and depending on the technology, the performance of a computer-implemented method can be distributed across multiple computers and / or multiple locations. On the other hand, in this presentation of computing environment 100, the detailed discussion focuses on a single computer, specifically computer 101, to keep the presentation as simple as possible. Computer 101 can reside in the cloud, even... Figure 1 It is not shown in the cloud. On the other hand, computer 101 does not need to be in the cloud, except to the extent that can be definitively indicated.

[0059] Processor set 110 includes one or more computer processors of any type now known or to be developed in the future. Processing circuitry 120 may be distributed across multiple packages, such as multiple cooperating integrated circuit chips. Processing circuitry 120 may implement multiple processor threads and / or multiple processor cores. Cache 121 is memory located within the processor chip package(s) and is typically used for data or code that should be readily accessible by the threads or cores running on processor set 110. Cache memory is typically organized into multiple levels based on its relative proximity to the processing circuitry. Alternatively, some or all of the cache in the processor set may be located “off-chip.” In some computing environments, processor set 110 may be designed to work with qubits and perform quantum computing.

[0060] Computer-readable program instructions are typically loaded onto computer 101 to cause the processor set 110 of computer 101 to perform a series of operational steps to implement a computer-implemented method, such that the instructions thus executed instantiate the method specified in the flowchart and / or the narrative description of the computer-implemented method included in this document (collectively, the “method of the invention”). These computer-readable program instructions are stored in various types of computer-readable storage media, such as cache 121 and other storage media discussed below. The program instructions and associated data are accessed by processor set 110 to control and direct the execution of the method of the invention. In computing environment 100, at least some of the instructions for performing the method of the invention may be stored in block 200 of persistent storage device 113.

[0061] Communication architecture 111 is a signal transmission path that allows various components of computer 101 to communicate with each other. Typically, this architecture consists of switches and conductive paths, such as switches and conductive paths that form buses, bridges, physical input / output ports, etc. Other types of signal communication paths can be used, such as fiber optic communication paths and / or wireless communication paths.

[0062] Volatile memory 112 is any type of volatile memory now known or to be developed in the future. Examples include dynamic random access memory (RAM) or static RAM. Typically, volatile memory 112 is characterized by random access, but this is not necessary unless explicitly stated otherwise. In computer 101, volatile memory 112 is located in a single package and is internal to computer 101; however, alternatively or additionally, volatile memory may be distributed across multiple packages and / or located externally relative to computer 101.

[0063] The persistent storage device 113 is any form of non-volatile storage device for a computer, now known or to be developed in the future. The non-volatility of this storage device means that the stored data is retained regardless of whether power is supplied to the computer 101 and / or directly to the persistent storage device 113. The persistent storage device 113 may be a read-only memory (ROM), but typically at least a portion of the persistent storage device allows data to be written, deleted, and rewritten. Some common forms of persistent storage devices include hard disks and solid-state storage devices. The operating system 122 may take several forms, such as various known proprietary operating systems employing a kernel or an operating system with an open-source portable operating system interface type. The code included in block 200 generally includes at least some of the computer code involved in performing the methods of the present invention.

[0064] Peripheral device set 114 includes the peripheral device set of computer 101. Data communication connections between peripheral devices and other components of computer 101 can be implemented in various ways, such as Bluetooth connections, near field communication (NFC) connections, connections made by cables (such as Universal Serial Bus (USB) type cables), plug-in connections (e.g., secure digital (SD) cards), connections made through local area communication networks, and even connections made through wide area networks such as the Internet. In various embodiments, UI device set 123 may include components such as displays, speakers, microphones, wearable devices (such as goggles and smartwatches), keyboards, mice, printers, touchpads, game controllers, and haptic devices. Storage device 124 is an external storage device, such as an external hard drive, or a pluggable storage device, such as an SD card. Storage device 124 may be persistent and / or volatile. In some embodiments, storage device 124 may take the form of a quantum computing storage device for storing data in the form of qubits. In embodiments where computer 101 requires substantial storage (e.g., where computer 101 locally stores and manages a large database), this storage can be provided by peripheral storage devices designed to store very large amounts of data, such as a storage area network (SAN) shared by multiple geographically distributed computers. The IoT sensor set 125 consists of sensors that can be used in IoT applications. For example, one sensor could be a thermometer, while another could be a motion detector.

[0065] Network module 115 is a collection of computer software, hardware, and firmware that allows computer 101 to communicate with other computers via WAN 102. Network module 115 may include hardware such as a modem or Wi-Fi transceiver, software for packetizing and / or depacketizing data transmitted over the communication network, and / or web browser software for transmitting data over the Internet. In some embodiments, the network control and network forwarding functions of network module 115 are performed on the same physical hardware device. In other embodiments (e.g., embodiments utilizing software-defined networking (SDN), the control and forwarding functions of network module 115 are performed on physically separate devices, such that the control function manages several different network hardware devices. Computer-readable program instructions for performing the methods of the present invention can typically be downloaded to computer 101 from an external computer or external storage device via a network adapter card or network interface included in network module 115.

[0066] WAN 102 is any wide area network (e.g., the Internet) capable of transmitting computer data over non-local distances using any technology known now or to be developed in the future for transmitting computer data. In some embodiments, WAN 102 may be replaced by and / or supplemented by a local area network (LAN), which is designed to transmit data between devices located in a local area, such as a Wi-Fi network. WAN and / or LAN typically include computer hardware such as copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and edge servers.

[0067] End User Equipment (EUD) 103 is any computer system used and controlled by an end user (e.g., a customer of the enterprise operating computer 101) and can take any of the forms discussed above in conjunction with computer 101. EUD 103 typically receives helpful and useful data from the operation of computer 101. For example, assuming computer 101 is designed to provide recommendations to the end user, these recommendations would typically be transmitted to EUD 103 from network module 115 of computer 101 via WAN 102. In this way, EUD 103 may display or otherwise present the recommendations to the end user. In some embodiments, EUD 103 may be client equipment such as a thin client, heavy client, mainframe, desktop computer, etc.

[0068] Remote server 104 is any computer system that provides at least some data and / or functionality to computer 101. Remote server 104 can be controlled and used by the same entity operating computer 101. Remote server 104 represents a machine (one or more) that collects and stores helpful and useful data for use by other computers such as computer 101. For example, if computer 101 is designed and programmed to provide recommendations based on historical data, that historical data can be provided to computer 101 from a remote database 130 of remote server 104.

[0069] Public cloud 105 is any computer system that can be used by multiple entities, providing on-demand availability of computer system resources and / or other computing capabilities (especially data storage (cloud storage) and computing power) without the need for direct, active management by users. Cloud computing typically leverages resource sharing to achieve scalability consistency and economy. Direct and active management of the computing resources of public cloud 105 is performed by the computer hardware and / or software of cloud orchestration module 141. The computing resources provided by public cloud 105 are typically implemented by virtual computing environments running on various computers constituting host physical machine set 142, which is the entire domain of physical computers in and / or available to the public cloud 105. Virtual computing environments (VCEs) typically take the form of virtual machines from virtual machine set 143 and / or containers from container set 144. It should be understood that these VCEs can be stored as images and can be transferred between various physical machine hosts as images or after the VCEs are instantiated. Cloud orchestration module 141 manages the transfer and storage of images, deploys new instantiations of VCEs, and manages the active instantiation of VCE deployments. Gateway 140 is a collection of computer software, hardware, and firmware that allow public cloud 105 to communicate via WAN 102.

[0070] Now, we will provide some further explanation of Virtualized Computing Environments (VCEs). A VCE can be stored as an "image." New active instances of a VCE can be instantiated from this image. Two common types of VCEs are virtual machines and containers. A container is a VCE that uses operating system-level virtualization. This refers to an operating system feature where the kernel allows multiple isolated user-space instances, called containers, to exist. From the perspective of the programs running within them, these isolated user-space instances typically appear as actual computers. Computer programs running on a regular operating system can utilize all the resources of that computer, such as connected devices, files and folders, network shares, CPU power, and quantifiable hardware capabilities. However, programs running within a container can only use the contents of the container and the devices allocated to the container; this is a characteristic known as containerization.

[0071] Private cloud 106 is similar to public cloud 105, except that computing resources are available only to a single enterprise. While private cloud 106 is depicted as communicating with WAN 102, in other embodiments, private cloud may be completely disconnected from the Internet and accessible only via a local / private network. A hybrid cloud is a combination of multiple clouds of different types (e.g., private, community, or public cloud types) typically implemented by different vendors. Each of the multiple clouds remains a separate and discrete entity, but the larger hybrid cloud architecture is bound together by standardization or proprietary technology that enables orchestration, management, and / or data / application portability across the multiple component clouds. In this embodiment, both public cloud 105 and private cloud 106 are part of a larger hybrid cloud.

[0072] Figure 2A An exemplary environment 205 according to an embodiment of the present invention is depicted. In this embodiment, the environment includes a dynamic rendering server 240, which includes or communicates with a dynamic UI rendering module 201, corresponding to a computer 101 and dynamic UI rendering code 200, such as... Figure 1 As shown in the image. The dynamic rendering server 240 includes a dynamic UI rendering module 201 and a backend service 203 or communicating with it. The backend service 203 is used to render the backend UI and interface to a frontend user device 204 connected to the network 220, which corresponds to... Figure 1 The end-user device 103. The dynamic rendering server 240 can be configured to communicate simultaneously with multiple different user computer devices 204. The environment 205 includes at least one database 230, which is connected via a network 220 (corresponding to...). Figure 1 The WAN 102) communicates operatively with the dynamic rendering server 240. The database 230 (corresponding to...) Figure 1 The remote server 104 or remote database 130 can store predefined widgets corresponding to front-end UI elements (such as interactive components). The exemplary environment 205 may include requests to view the interface on the user device 204; receiving superuser data via the back-end UI 201; and processing the superuser data on the user device 204 (corresponding to...). Figure 1 The interface is dynamically rendered on the end-user device 103.

[0073] In an embodiment, Figure 2A The dynamic rendering server 240 includes a rendering module 201 and a backend service 203, each of which may include Figure 1The code of block 200 is a module. Such a module may include routines, programs, objects, components, logic, data structures, etc., that perform specific tasks or implement code of specific data types used by block 200 to perform functions and / or methods as described in the embodiments of the invention herein. These modules of the code of block 200 may be provided by Figure 1 The processing circuitry 120 executes the method of the invention described herein. The dynamic rendering server 240 may include... Figure 2A The modules shown may have more or fewer modules. In embodiments, individual modules may be integrated into a single module. Alternatively, a single module may be implemented as multiple modules. Furthermore, the number of devices and / or networks in the environment is not limited to... Figure 2A The quantities shown are not included. In reality, the environment may include additional equipment and / or networks; fewer devices and / or networks; different devices and / or networks; or different from those shown. Figure 2A The equipment and / or network arranged as shown.

[0074] Figure 2B An exemplary environment depicting the MVC software architecture pattern is used for... Figure 2A The dynamic rendering server 240 dynamically renders the UI, which includes at least one user device 204. The user device 204 accesses a controller 206 212, which can manipulate a UI model 208 214. The UI model can be dynamically rendered via a rendering module 201 based on user input and manipulation via a backend service 203. The frontend UI 202 can be displayed 210 to at least one user device 204.

[0075] Figure 3 The invention is described in accordance with embodiments thereof and regarding Figure 2A and Figure 2B The exemplary method 300 described herein. It can be implemented... Figure 2A or Figure 2B The steps to execute this method in the environment, and refer to Figure 2A and Figure 2B The components depicted in the diagram are used to describe the steps of the method. At step 302, the system may display a backend UI, which includes a prompt 304, comprising a question prompt and input prompts, such as... Figure 5-10 As shown in 520 and 522 respectively. Input prompts can include simple input prompts 306, such as text input prompts, or complex input prompts 308, such as image data input prompts, video data input prompts, audio data input prompts, etc. At step 310, the system can receive superuser input in the form of a task prompt, which includes a predefined question type widget or user code snippet. If the system receives a code snippet as user input 312, the system can parse the code snippet 400, such as... Figure 4 As shown in the diagram. In this embodiment, the code snippet, optionally in JavaScript or CSS format, can be received via a cross-platform development framework, as previously described. If the system receives superuser input 314 for a task-type widget, the system backend can parse the superuser input data into JSON format 316, which can be sent to the frontend platform 318, which may include the frontend user device 204. The frontend platform 318 can then render a predefined widget as a UI element 320 including the superuser input variables.

[0076] Figure 4 The invention is described in accordance with embodiments thereof and regarding Figure 2A , Figure 2B and Figure 3 The exemplary method 400 is described. (For example...) Figure 3 As shown, at step 312, the system can receive a code snippet as user input, and the system can parse the code snippet to determine whether the UI to be generated will be displayed on a web-based browser or a mobile application on the screen, such as by checking the backend service of the code snippet. If the UI to be generated will be displayed on a web-based browser, the system can receive trusted superuser JavaScript, CSS, or HTML encoding (or other web-based editing language) 402 for a specific custom widget. The system can process the received code snippet 404, for example, parsing the code snippet, which may include parsing the JSON-formatted input data into at least one pre-built widget, modifying the code snippet structure to JSON format 406 (including removing unnecessary elements), for example, converting at least one prompt type and at least one associated response type to JSON-formatted input data, and sending the modified code snippet 408 to the front-end platform 401 (corresponding to Figure 3 The front-end platform 318 in Figure 2, the front-end user device 204 and Figure 1 In the end-user device 103, the front-end platform can render a custom UI widget 410 based on a modified code snippet (such as in the form of a rendering instruction). In one embodiment, sending a modified code snippet 408 to the front-end platform 401 (such as in the form of a rendering instruction) can cause the front-end platform to dynamically render the front-end UI. In another embodiment, sending a custom UI widget 410 (such as a pre-built widget in the form of a rendering instruction) to the front-end platform 401 can cause the front-end platform 401 to dynamically render the front-end UI. In other embodiments, the rendering instruction causes the front-end platform 401 to dynamically render the front-end UI by causing the front-end platform 401 to dynamically render various types of user interaction components (such as interaction components corresponding to the UI widget 410), which are configured to receive at least one input or generate at least one output.

[0077] According to an embodiment, the system can also receive code snippets as user input, and the system can parse the code snippets to determine whether the UI to be generated will be displayed in a mobile application on a device display, such as by checking the backend service of the code snippets. If the UI to be generated will be displayed in a mobile application, the system can receive trusted superuser JavaScript, CSS, or HTML encoding 412 for a specific custom widget in a standardized framework, such as a virtual web browser instance. The system can determine 414 whether the received code snippet is in JavaScript, CSS, HTML, or Objective-C format, modify the code snippet structure to JSON format 416, send the modified code snippet 418 to the front-end platform 401, compile the modified code snippet, and render the custom UI widget 420 in the standardized framework based on the modified code snippet 418. In an embodiment, compiling the modified code snippet 418 causes the front-end platform 401 to dynamically render the front-end UI.

[0078] Figure 5 A method 500 is described, including a backend UI 502, which includes task prompts 504a and 504b for dynamically rendering a frontend UI 510 (corresponding to frontend UI 202 in FIG2). A superuser can provide task prompts 504a and 504b after detecting or receiving the superuser's credentials at the backend UI, such as, for example, via superuser login credentials or as specified by an administrator of a superuser with task prompt input permissions. In embodiments, detecting the superuser's credentials at the backend UI may include detecting whether the frontend user is using a web-based interface or a mobile interface that supports at least one language selected from the group including CSS, JavaScript, and HTML.

[0079] Task prompts 504a and 504b can be singular or plural. Each task prompt 504a and 504b may include input data, such as task input 520, response type 522, prompt type 524, prompt file 526, prompt text 528, and data 530.

[0080] Task input 520 may be an auto-filled text input field that indicates the name or order of the tasks associated with task prompts 504a and 504b. As a non-limiting example, task input 520 may be auto-filled based on input to prompt text 528.

[0081] Prompt type 524 can be a text input field or a dropdown menu, encompassing various prompts or question types to be rendered in the front-end UI. Non-limiting examples include text, audio recordings, video recordings, etc. Prompt type 524 input determines whether a predefined widget is rendered as a question or prompt, and answer type 522 acts as an answer to that question or prompt. The system can include predefined templates for each prompt type 524.

[0082] Response type 522 can be a text input field or a dropdown menu, and includes various response types to be rendered in the front-end UI. Non-limiting examples include text input fields, radio buttons, audio or video recordings, etc. The input for response type 522 determines whether a predefined widget is rendered in response to prompt type 524. The system may include predefined templates for each response type 522.

[0083] Prompt file 526 can be configured to render a predefined widget as part of a response to prompt type 524, such as, but not limited to, allowing front-end users to upload files such as images, audio recordings, video recordings, etc.

[0084] The prompt text 528 can be a text input field configured to receive superuser text input to determine the rendering of tasks 512a and 512b. For example, and as... Figure 5 As shown, a super user can enter "What is your gender?" in the prompt text 528 field, which can be rendered as part or all of a predefined widget as a question or prompt, and answer type 522 is used as an answer to that question or prompt.

[0085] Data 530 may include a text input field containing automatically generated text based on inputs to task input 520, response type 522, prompt type 524, prompt file 526, and prompt text 528. Data 530 may automatically generate JSON-compatible code to be sent as rendering instructions 506, including task-specific rendering instructions 508a and 508b for each task prompt 504a and 504b, and JSON-compatible instructions 513 during the dynamic rendering of UI elements in the front-end UI 510. Data 530 may be editable within its text input field or used as a code snippet for generating unique or customized UI elements.

[0086] and Figure 2AThe front-end platform (including front-end UI 510) corresponding to user device 204 can receive JSON-compatible instructions 513 and render user-facing UI elements 512a and 512b corresponding to rendering instructions 508a and 508b for each task prompt 504a and 504b. User-facing UI elements 512a and 512b may include elements such as, but not limited to, a task title 560 corresponding to task input 520; a task progress 562 corresponding to task input 520; a question / hint 564 corresponding to prompt text 528 and prompt type 524; user input 566 corresponding to answer type 522; or a file prompt 514 corresponding to prompt file 526.

[0087] As a non-limiting example, the method may include the step of receiving at least one prompt type and at least one associated answer type via a backend UI. Prompt type 524 and answer type 522 may be, for example, a question-and-answer set used in a survey. The method may include the step of receiving a request to view, for example, a survey corresponding to at least one prompt type 524 and at least one associated answer type 522 on a frontend UI. The request to view may be initiated via an end-user device requesting to view and access, for example, the aforementioned survey. The method may include the step of dynamically rendering the frontend UI based on at least one prompt type 524 and at least one associated answer type 522 via dynamic UI rendering code of dynamic rendering server 240 or block 200. The method may include the step of instructing end-user device 103 to display the frontend UI via a processor set.

[0088] Figure 6 An exemplary method 600 is depicted for generating a UI that responds to a task or issue requiring video recording or uploading, the UI including a backend UI 602, corresponding to... Figure 3 The backend UI 302 and Figure 5 Error 502 is configured to allow the superuser to create tasks and input or questions and answers. Tasks or questions can be generated on the backend based on rendering instruction 604, corresponding to... Figure 5 Rendering instruction 506, including input such as Figure 5 The description previously mentioned includes task input, response type, prompt type, prompt file, prompt text, and data. The system can, based on rendering instruction 604, render the front-end UI 202 corresponding to Figure 2. Figure 5 The front-end UI of 510 is rendered in 606.

[0089] Figure 7 An exemplary method 700 is depicted for generating a UI that requests audio recording or uploading in response to a task or issue. This UI includes a backend UI 602, corresponding to... Figure 3 The backend UI 302 and Figure 5502 is configured to allow superusers to create tasks or issues. Tasks or issues can be generated based on the backend of rendering instruction 704, which corresponds to... Figure 5 Rendering instruction 506, including input such as Figure 5 The description previously mentioned includes task input, response type, prompt type, prompt file, prompt text, and data. The system can, based on rendering instruction 704, render the front-end UI 202 corresponding to Figure 2. Figure 5 The front-end UI of 510 renders widgets in 706.

[0090] Figure 8 An exemplary method 800 is depicted for generating a front-end UI that requires slider interaction in response to a task or question. This UI includes a back-end UI 802, corresponding to... Figure 3 The backend UI 302 and Figure 5 502 is configured to allow superusers to create tasks or issues. Tasks or issues can be generated based on the backend of rendering instruction 804, which corresponds to... Figure 5 Rendering instruction 506, including input such as Figure 5 The description previously mentioned includes task input, response type, prompt type, prompt file, prompt text, and data. The system can, based on rendering instruction 804, render the front-end UI 202 corresponding to Figure 2. Figure 5 The widget is rendered in the front-end UI of 510 806.

[0091] Figure 9 An exemplary method 900 is depicted for generating a UI that requires user interaction with a toggle button or radio button in response to a task or question. This UI includes a backend UI 902, corresponding to... Figure 3 The backend UI 302 and Figure 5 502 is configured to allow superusers to create tasks or issues. Tasks or issues can be generated based on the backend of rendering instruction 904, which corresponds to... Figure 5 Rendering instruction 506, including input such as Figure 5 The description previously mentioned includes task input, response type, prompt type, prompt file, prompt text, and data. The system can, based on rendering instruction 904, render the front-end UI 202 corresponding to Figure 2 and... Figure 5 The front-end UI of 510 renders widgets in 906.

[0092] Figure 10 An exemplary method 1000 for generating a UI based on code snippet input provided via a backend UI is described. Dynamic rendering may include receiving at least one code snippet 1002, corresponding to Figure 4The code snippet 400 serves as input for generating a UI that includes task hints and input suggestions. The code snippet can be received in JavaScript, CSS, or HTML. The system can determine whether the code snippet is in JavaScript, CSS, HTML, or Objective-C; format the code snippet to a JSON-compatible format; compile the code snippet; and render the code snippet as a UI or UI element 1004, corresponding to the UI element 1004, in a web browser or mobile application displayed on a computing device's screen. Figure 3 UI element 320.

[0093] Figure 11 A flowchart of program instructions 1100, executed by a system comprising a processor set, one or more computer-readable storage media, and program instructions co-stored on the one or more computer-readable storage media, is depicted according to a preferred embodiment. The program instructions are executable to receive, via the processor set and through a back-end UI, 1102, input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of the front-end UI; generate, via the processor set, rendering instructions 1104 based on the at least one prompt type and at least one associated response type; receive, via the processor set and from a front-end platform, 1106, a request to view the front-end UI; and, in response to receiving the request to view the front-end UI, send rendering instructions 1108 via the processor set to the front-end platform, wherein the rendering instructions cause the front-end platform to dynamically render the front-end UI.

[0094] In this embodiment, the service provider may be able to perform the processes described herein. In this case, the service provider may create, maintain, deploy, support, etc., computer infrastructure that performs processing steps for one or more clients according to various aspects of the invention. These clients may be, for example, any business using the technology. In return, the service provider may receive payments from the clients(s) according to subscription and / or fee agreements and / or may receive payments from the sale of advertising content to one or more third parties.

[0095] In other embodiments, the implementation provides a method implemented via a computer over a network. In this case, methods such as... Figure 1 Computer infrastructure such as computer 101, and can acquire (e.g., create, purchase, use, modify, etc.) one or more systems for performing the processes according to various aspects of the present invention and deploy said systems onto the computer infrastructure. In this regard, the deployment of the system may include one or more of the following: (1) in a computer infrastructure such as computer 101, and can acquire (e.g., create, purchase, use, modify, etc.) one or more systems for performing the processes according to various aspects of the present invention and deploy said systems onto the computer infrastructure. Figure 1(1) Install program code from a computer-readable medium on a computing device such as a computer 101; (2) add one or more computing devices to the computer infrastructure; and (3) incorporate and / or modify one or more existing systems of the computer infrastructure to enable the computer infrastructure to perform the processing according to various aspects of the invention.

[0096] The description of various embodiments of the invention is presented for illustrative purposes and is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein has been chosen to best explain the principles of the embodiments, practical application, or technical improvements relative to the technology on the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A computer-implemented method, comprising: The processor set receives input data through a back-end user interface, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of the front-end user interface; The processor set generates rendering instructions based on the at least one prompt type and at least one associated response type; The processor set receives a request from the front-end platform to view the front-end user interface; as well as In response to receiving a request to view the front-end user interface, the processor set sends the rendering instructions to the front-end platform, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface.

2. The computer-implemented method of claim 1, wherein generating the rendering instructions includes converting the at least one prompt type and the at least one associated response type into input data in JavaScript Object Notation (JSON) format.

3. The computer-implemented method of claim 2, wherein generating the rendering instructions includes parsing JSON-formatted input data into at least one pre-built widget.

4. The computer-implemented method of claim 3, wherein sending the rendering instruction includes sending the at least one pre-built widget to the front-end platform, wherein the at least one pre-built widget causes the front-end platform to dynamically render the front-end user interface.

5. The computer-implemented method according to any of the preceding claims further comprises: Detect the superuser's credentials on the backend user interface; as well as The system detects whether the front-end user is using a web-based interface or a mobile interface, wherein the web-based interface supports at least one language selected from the group consisting of Cascading Style Sheets (CSS), JavaScript, and Hypertext Markup Language (HTML).

6. The computer-implemented method of claim 5, further comprising responding to detecting that the web-based interface supports at least one language selected from the group comprising CSS, JavaScript, and HTML: Receive at least one code snippet as user input; Analyze at least one of the code snippets; Modify at least one code snippet to JSON format; and Sending the rendering instructions to the front-end platform includes sending a modified code snippet to the front-end platform, wherein the modified code snippet causes the front-end platform to dynamically render the front-end user interface.

7. The computer-implemented method of claim 5, further comprising responding to detecting that the web-based interface supports a mobile interface: Perform checks on at least one backend service for at least one code snippet; Sending the rendering instructions includes sending the at least one code snippet to the front-end platform; and Compile the at least one code snippet, wherein the at least one code snippet causes the front-end platform to dynamically render the front-end user interface.

8. The computer-implemented method of claim 5 further includes receiving at least one code snippet in at least one of JavaScript or CSS via a cross-platform development framework.

9. A computer-implemented method according to any of the preceding claims, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface by causing the front-end platform to dynamically render multiple different types of user interaction components, the user interaction components being configured to cause at least one action to be selected from a group including receiving at least one input and generating at least one output.

10. A computer program product comprising one or more computer-readable storage media, wherein program instructions are commonly stored on the one or more computer-readable storage media, the program instructions being executable to: Input data is received through a back-end user interface, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of the front-end user interface; Rendering instructions are generated based on the at least one prompt type and the at least one associated response type; Receive a request from the front-end platform to view the front-end user interface; as well as In response to receiving a request to view the front-end user interface, the rendering instruction is sent to the front-end platform, wherein the rendering instruction causes the front-end platform to dynamically render the front-end user interface.

11. The computer program product of claim 10, wherein generating the rendering instructions includes converting the at least one prompt type and the at least one associated response type into input data in JavaScript Object Notation (JSON) format.

12. The computer program product of claim 11, wherein generating the rendering instructions includes parsing JSON-formatted input data into at least one pre-built widget.

13. The computer program product of claim 12, wherein sending the rendering instruction includes sending the at least one pre-built widget to the front-end platform, wherein the at least one pre-built widget causes the front-end platform to dynamically render the front-end user interface.

14. The computer program product of claim 13, wherein the program instructions are executable to: Detecting the superuser's credentials on the backend user interface; and The system detects whether the front-end user is using a web-based interface or a mobile interface, wherein the web-based interface supports at least one language selected from the group consisting of Cascading Style Sheets (CSS), JavaScript, and Hypertext Markup Language (HTML).

15. The computer program product of claim 14, wherein the program instructions are executable in response to detecting that the web-based interface supports at least one language selected from the group comprising CSS, JavaScript, and HTML: Receive at least one code snippet as user input; Analyze at least one of the code snippets; Modify at least one code snippet to JSON format; and Sending the rendering instructions to the front-end platform includes sending a modified code snippet to the front-end platform, wherein the modified code snippet causes the front-end platform to dynamically render the front-end user interface.

16. The computer program product of claim 14, wherein the program instructions are executable in response to detecting that the web-based interface supports a mobile interface: Perform checks on at least one backend service for at least one code snippet; Sending the rendering instructions includes sending the at least one code snippet to the front-end platform; and Compile the at least one code snippet, wherein the at least one code snippet causes the front-end platform to dynamically render the front-end user interface.

17. The computer program product of claim 14, wherein the program instructions are executable to receive at least one code snippet in at least one of JavaScript or CSS via a cross-platform development framework.

18. The computer program product according to any one of claims 10 to 17, wherein the rendering instructions cause the front-end platform to dynamically render the front-end user interface by causing the front-end platform to dynamically render multiple different types of user interaction components, the user interaction components being configured to cause at least one action to be selected from the group including receiving at least one input and generating at least one output.

19. A system comprising: A processor set, one or more computer-readable storage media, and program instructions stored together on the one or more computer-readable storage media, the program instructions being executable to: Input data is received through a back-end user interface, the input data including at least one prompt type and at least one associated response type, wherein the at least one prompt type and at least one associated response type define aspects of the front-end user interface; Rendering instructions are generated based on the at least one prompt type and the at least one associated response type; Receive a request from the front-end platform to view the front-end user interface; as well as In response to receiving a request to view the front-end user interface, the rendering instruction is sent to the front-end platform, wherein the rendering instruction causes the front-end platform to dynamically render the front-end user interface.

20. The system of claim 19, wherein generating the rendering instructions includes converting the at least one prompt type and the at least one associated response type into input data in JavaScript Object Notation (JSON) format.

21. A computer program comprising program code means adapted to perform the method according to any one of claims 1 to 9 when the program is run on a computer.

Images