# US 2021/0176338 A1 · Dynamic user interface delivery system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0176338 A1
- Document ID: US20210176338A1
- Status: Published application
- Kind: A1
- Application number: 17/181,495
- Filed: 2021-02-22
- Published: 2021-06-10
- Earliest claimed: 2013-03-15
- Assignees: Gadget Software, Inc.
- Applicants: Gadget Software, Inc.
- Inventors: Fabio M. CHIUSSI; Parameshwar HEGDE
- Web page: https://patentgrep.com/patent/US20210176338A1

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04W 4/50: Service provisioning or reconfiguring
- H04W 4/60: Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A System Solution offers a Business Entity a way to update a Native Application Client by directly downloading a new version of the Application Client from an Application Server bypassing the Application Store. A Native Application Client is updated while the current Native Application Client is running on the Client Device. A Native Application Client is divided into a Native Layer which runs directly on the Operating System of the Client Device and a Dynamic Layer that runs on the Native Layer. The System Solution automatically generates Application Clients, Application Servers, and Dashboards. The Business Entity uses the generated Dashboards to modify the Dynamic Layer by generating a new Dynamic Layer and making it available for download to the Client Device. The Navigation Parameters can be set in the Dynamic Layer allowing the Business Entity to change the application flow of the Native Application Client.

## Claims

### Claim 1

A system comprising:
an application generator configured to be connected to a network and to automatically generate a two-layer native application client of which at least a portion of the two-layer application client is configured to run on a client device, an application server software and a dashboard generator configured to generate a dashboard using an input from the application generator;
an application server configured to be connected to the network;
the application generator configured to be coupled, via the network, to the application server to automatically deploy the application server software to the application server;
the two-layer native application client includes a native layer and a dynamic layer;
the native layer configured to interact directly with system libraries of an operating system of the client device;
the dynamic layer configured to interact indirectly with system libraries of the operating system of the client device via the native layer; and
the application server configured to be dynamically adapted by execution of the application server software to receive a user input via the dashboard and to deploy an updated dynamic layer to the client device to update the two-layer native application client, the updated dynamic layer being automatically generated based on the received user input,
the application server software being configured to simultaneously directly update the dynamic layer of the two-layer native application client and execute the native layer of the two-layer native application client.

### Claim 2 (depends on 1)

The system of claim 1,
wherein the native layer comprises an update manager to download the updated dynamic layer to the client device from the application server.

### Claim 3 (depends on 1)

The system of claim 1, wherein the two-layer native application client is configured to be updated with the updated dynamic layer while the two-layer native application client is running on the client device.

### Claim 4 (depends on 1)

The system of claim 1, wherein the two-layer native application client comprises a plurality of pages each with at least one button where said buttons are navigation elements.

### Claim 5 (depends on 4)

The system of claim 4,
wherein each of the plurality of pages comprises a plurality of elements each with a plurality of sub-elements, a navigation element, an actionable element, a navigation rule, a Tillable element, and a native logic with an orchestration, an update manager and native client functional blocks.

### Claim 6 (depends on 5)

The system of claim 5, wherein each page of the plurality of pages has a page state of “in use” or “standby”.

### Claim 7 (depends on 5)

The system of claim 5, wherein a conditional navigation determines when a navigation element is displayed in a first page and one or more pages of a second plurality of pages that are linked to the first page.

### Claim 8 (depends on 1)

The system of claim 1, wherein the application generator is configured to generate the input to the dashboard generator.

### Claim 9

A system comprising:
a processor;
a memory coupled to the processor, the memory having stored therein software instructions that, when executed by the processor, cause the processor to perform operations including:
automatically generating, by an application generator, a set of application components, the set of application components comprising a two-layer application client, an application server software based on entity-specific data, and a dashboard generator configured to generate a dashboard using an input from the application generator, wherein the two-layer application client is configured to be runnable on a client device and includes a dynamic layer and a native layer, the dynamic and native layers being configured to be separately updateable; and
automatically deploying the application server software to a server, the server being adapted by the deployed application server software to make the dashboard available to receive user input,
wherein, when a user input is received via the dashboard, a dynamically updated data model is automatically generated based on the received user input and the entity-specific data, and
an updated dynamic layer of the two-layer application client is automatically generated based on the dynamically updated data model, the updated dynamic layer being configured to be transferred directly to the client device to update the dynamic layer of the two-layer application client,
wherein the application server software is configured to directly update the dynamic layer of the two-layer application client while executing the native layer of the two-layer application client.

### Claim 10 (depends on 9)

The system of claim 9,
wherein the two-layer application client is a desktop application client or a cloud application client.

### Claim 11 (depends on 9)

The system of claim 9,
wherein the two-layer application client comprises a plurality of pages and each page comprises a page surface and a page foundation, the page surface being dynamically updateable via the dashboard.

### Claim 12 (depends on 11)

The system of claim 11,
wherein each page surface comprises components including a least one dynamic element, at least one dynamic sub-element, and one or more navigation parameters; and
wherein the operations further include automatically generating dashboards, dashboard validation rules, and dashboards consistency rules based on each page surface.

### Claim 13 (depends on 12)

The system of claim 12, the operations further comprising:
generating, based on the dashboard validation rules and the dashboards consistency rules, a plurality of validation controllers to show a validity and a consistency of the dynamically updated data model; and
determining, using the plurality of validation controllers, the validity and consistency of the updated dynamic layer of the two-layer application client.

### Claim 14 (depends on 9)

The system of claim 9, wherein the application generator is configured to generate the input to the dashboard.

### Claim 15

A method of checking for updates on an application server, the method comprising:
automatically generating, by an application generator, a set of application components, the set of application components comprising a two-layer application client of which at least a portion of the two-layer application client is configured to run on a client device, an application server software based on entity-specific data, and a dashboard that is configured to be generated by a dashboard generator using an input from the application generator, wherein the two-layer application client comprises a dynamic layer and a native layer, the dynamic layer including a plurality of page surfaces and the native layer including an update manager, wherein the application server software is configured to be automatically deployed to the application server, and wherein the application server is configured to communicate with the update manager of the two-layer application client according to a dynamic update protocol;
checking, according to the dynamic update protocol, the application server for an updated page surface and/or a new page surface; and
downloading only the updated page surface and/or the new page surface automatically to update the dynamic layer of the two-layer application client,
the application server being configured by the automatically deployed application server software to receive user input via the dashboard and to deploy the updated page surface and/or the new page surface to the client device to update the two-layer application client according to the dynamic update protocol, the application generator configured to automatically generate the updated page surface and/or the new page surface based on the received user input,
wherein the application server software is configured to directly update the dynamic layer of the two-layer application client while executing the native layer of the two-layer application client.

### Claim 16 (depends on 15)

The method of claim 15, wherein the two-layer application client is a desktop application client.

### Claim 17 (depends on 15)

The method of claim 15, further comprising:
providing a plurality of elements with an element dynamic property in a page surface of the plurality of page surfaces;
providing a plurality of sub-elements with a sub-element dynamic property in the page surface; and
when only a subset of the elements in the page surface have been updated, the downloading comprising minimizing bandwidth usage of a network by downloading less than all of the elements of the page surface from the application server.

### Claim 18 (depends on 15)

The method of claim 15,
wherein the client device is configured to accept applications from one or more application distribution platforms, the two-layer application client being downloaded from one of the one or more application distribution platforms associated with the client device, and
wherein the application server is configured to transfer the updated page surface and/or the new page surface to the client device and directly update the two-layer application client.

### Claim 19 (depends on 15)

The method of claim 15, further comprising:
applying the updated page surface and/or the new page surface without stopping, deleting, and re-installing the two-layer application client; and
the applying being performed while the two-layer application client is running.

### Claim 20 (depends on 15)

The method of claim 15, wherein the application generator is configured to generate the input to the dashboard generator.
