Abstract: An embodiment may involve web page metadata that defines a web page, first sub-page metadata that defines a first sub-page, and second sub-page metadata that defines a second sub-page, wherein the web page metadata includes specification of a viewport, and wherein the viewport is associated with an identifier. One or more processors may be configured to: receive a request for the web page; resolve the web page metadata into web content, wherein resolving the web page metadata includes: (i) determining, based on the identifier, a route associated with the viewport, (ii) determining, based on the route, a set of conditions associated with the viewport, (iii) determining that a particular condition is satisfied, wherein the particular condition is associated with the first sub-page and (iv) placing, based on the particular condition being satisfied, the first sub-page metadata in the viewport; and transmit the web content.

Abstract: An embodiment may involve web page metadata that defines a web page, first sub-page metadata that defines a first sub-page, and second sub-page metadata that defines a second sub-page, wherein the web page metadata includes specification of a viewport, and wherein the viewport is associated with an identifier. One or more processors may be configured to: receive a request for the web page; resolve the web page metadata into web content, wherein resolving the web page metadata includes: (i) determining, based on the identifier, a route associated with the viewport, (ii) determining, based on the route, a set of conditions associated with the viewport, (iii) determining that a particular condition is satisfied, wherein the particular condition is associated with the first sub-page and (iv) placing, based on the particular condition being satisfied, the first sub-page metadata in the viewport; and transmit the web content.

Abstract: A server receives a first hypertext transfer protocol (HTTP) from a client device requesting for content associated with a webpage. The server retrieves a plurality of cache keys associated with respective sets of application metadata identified in the first HTTP request from an application metadata database and transmits the cache keys to the client device. The server receives a second HTTP request from the client device identifying one or more cache keys that are not stored in a local HTTP cache of the client device. The server device retrieves the sets of application metadata corresponding to the missing cache keys from the application metadata database and transmits the application metadata to the client device.

Abstract: A system includes an application configured to: receive, from a client device, a query for a first web page of a plurality of web pages; generate a response including a shared content that is common to a plurality of web pages, a first page-specific content that defines the first web page, and a predefined token separating the shared content from the first page-specific content; and transmit, to the client device, the response. Reception of the response is configured to cause the client device to: write, to a cache memory, the shared content, render the first web page based on the response, and in response to reception of a subsequent event that references a second web page, read the shared content from the cache memory and begin rendering the shared content before receiving, from the server application, a second page-specific content that defines the second web page.

Abstract: A system includes an application configured to: receive, from a client device, a query for a first web page of a plurality of web pages; generate a response including a shared content that is common to a plurality of web pages, a first page-specific content that defines the first web page, and a predefined token separating the shared content from the first page-specific content; and transmit, to the client device, the response. Reception of the response is configured to cause the client device to: write, to a cache memory, the shared content, render the first web page based on the response, and in response to reception of a subsequent event that references a second web page, read the shared content from the cache memory and begin rendering the shared content before receiving, from the server application, a second page-specific content that defines the second web page.

Abstract: A server receives a first hypertext transfer protocol (HTTP) from a client device requesting for content associated with a webpage. The server retrieves a plurality of cache keys associated with respective sets of application metadata identified in the first HTTP request from an application metadata database and transmits the cache keys to the client device. The server receives a second HTTP request from the client device identifying one or more cache keys that are not stored in a local HTTP cache of the client device. The server device retrieves the sets of application metadata corresponding to the missing cache keys from the application metadata database and transmits the application metadata to the client device.

Abstract: A server receives a first hypertext transfer protocol (HTTP) from a client device requesting for content associated with a webpage. The server retrieves a plurality of cache keys associated with respective sets of application metadata identified in the first HTTP request from an application metadata database and transmits the cache keys to the client device. The server receives a second HTTP request from the client device identifying one or more cache keys that are not stored in a local HTTP cache of the client device. The server device retrieves the sets of application metadata corresponding to the missing cache keys from the application metadata database and transmits the application metadata to the client device.

Abstract: A system includes an application configured to: receive, from a client device, a query for a first web page of a plurality of web pages; generate a response including a shared content that is common to a plurality of web pages, a first page-specific content that defines the first web page, and a predefined token separating the shared content from the first page-specific content; and transmit, to the client device, the response. Reception of the response is configured to cause the client device to: write, to a cache memory, the shared content, render the first web page based on the response, and in response to reception of a subsequent event that references a second web page, read the shared content from the cache memory and begin rendering the shared content before receiving, from the server application, a second page-specific content that defines the second web page.

Abstract: An embodiment may involve web page metadata that defines a web page, first sub-page metadata that defines a first sub-page, and second sub-page metadata that defines a second sub-page, wherein the web page metadata includes specification of a viewport, and wherein the viewport is associated with an identifier. One or more processors may be configured to: receive a request for the web page; resolve the web page metadata into web content, wherein resolving the web page metadata includes: (i) determining, based on the identifier, a route associated with the viewport, (ii) determining, based on the route, a set of conditions associated with the viewport, (iii) determining that a particular condition is satisfied, wherein the particular condition is associated with the first sub-page and (iv) placing, based on the particular condition being satisfied, the first sub-page metadata in the viewport; and transmit the web content.

Abstract: Persistent storage may contain a plurality of user interface (UI) component definitions. One or more processors may be configured to: receive, by way of a platform UI builder, selection of a UI component definition from the plurality of UI component definitions; bind, by way of input entered into the platform UI builder, data to the UI component definition, wherein the data is from a data source, and wherein the input is a programmatic statement that references the data source or a set of values that references the data source; generate, by way of the platform UI builder, metadata representing the input; create, by a platform runtime, a UI component that incorporates the data into the UI component definition in accordance with the metadata; generate, by the platform runtime, a graphical user interface including the UI component; and provide, for display on a client device, a representation of the graphical user interface.

Abstract: A method for providing user content that may receive, from a user device, a request for content. The method may obtain, in response to the request, a field identifier from a multiple of field identifiers according to a priority for a multiple of fields corresponding to the field identifiers. The field identifier may correspond to a field. The method may obtain application content based on the field identifier. The method may generate declarative content from the application content. The declarative content may express the application content in a declarative programming language. The method may transmit, to the user device, the declarative content.

Abstract: A method for providing application content including obtaining, by a declarative content engine executing on a computer processor, an initial application content from a content repository and expressing the initial application content in a declarative programming language to obtain declarative content and transmitting the declarative content to a user experience player (UXP). The UXP processes the declarative content to obtain the initial application content, binds the initial application content to first platform-specific templates and first platform-specific navigation patterns, and renders the initial application content in a first platform-specific user display format.

Abstract: A method for providing user content that may receive, from a user device, a request for content. The method may obtain, in response to the request, a field identifier from a multiple of field identifiers according to a priority for a multiple of fields corresponding to the field identifiers. The field identifier may correspond to a field. The method may obtain application content based on the field identifier. The method may generate declarative content from the application content. The declarative content may express the application content in a declarative programming language. The method may transmit, to the user device, the declarative content.

Abstract: A method for providing user content that may receive, from a user device, a request for content. The method may obtain, in response to the request, a field identifier from a multiple of field identifiers according to a priority for a multiple of fields corresponding to the field identifiers. The field identifier may correspond to a field. The method may obtain application content based on the field identifier. The method may generate declarative content from the application content. The declarative content may express the application content in a declarative programming language. The method may transmit, to the user device, the declarative content.

Abstract: A method for providing application content including obtaining, by a declarative content engine executing on a computer processor, an initial application content from a content repository and expressing the initial application content in a declarative programming language to obtain declarative content and transmitting the declarative content to a user experience player (UXP). The UXP processes the declarative content to obtain the initial application content, binds the initial application content to first platform-specific templates and first platform-specific navigation patterns, and renders the initial application content in a first platform-specific user display format.

Abstract: A method for providing user content that may receive, from a user device, a request for content. The method may obtain, in response to the request, a field identifier from a multiple of field identifiers according to a priority for a multiple of fields corresponding to the field identifiers. The field identifier may correspond to a field. The method may obtain application content based on the field identifier. The method may generate declarative content from the application content. The declarative content may express the application content in a declarative programming language. The method may transmit, to the user device, the declarative content.

Abstract: A method for providing application content including obtaining, by a declarative content engine executing on a computer processor, an initial application content from a content repository and expressing the initial application content in a declarative programming language to obtain declarative content and transmitting the declarative content to a user experience player (UXP). The UXP processes the declarative content to obtain the initial application content, binds the initial application content to first platform-specific templates and first platform-specific navigation patterns, and renders the initial application content in a first platform-specific user display format.