Abstract: This disclosure relates to widget integration. Embodiments include receiving a workflow definition specifying one or more widgets to be loaded into a shell executing within a given application, the shell comprising a runtime environment, the one or more widgets comprising at least a first cross-platform widget. Embodiments include instantiating the runtime environment for the first cross-platform widget, the runtime environment including a bridge interface for facilitating communications between each widget in the one or more widgets and the given application. Embodiments include loading the first cross-platform widget into the runtime environment. Embodiments include processing, through the bridge interface, a communication from the first cross-platform widget running within the shell, wherein the communication comprises a result of executing a function.

Abstract: This disclosure relates to facilitating communication between widgets of cross-platform applications. An exemplary system includes computing components configured to execute an application shell. The system is configured to cause the application shell to do the following. The application shell instantiates a cross-platform application comprising a plurality of application widgets. The application shell then determines that a first application widget of the plurality of application widgets executes instructions through an execution container of the cross-platform application. The application shell then receives a request comprising criteria from the first application widget, wherein the criteria specify an application widget to listen for communications from. The application shell then receives a communication from the second application widget and determines that the communication matches the criteria of the request by the first application widget.

Abstract: This disclosure relates to facilitating communication between widgets of cross-platform applications. An exemplary system includes computing components configured to execute an application shell. The system is configured to cause the application shell to do the following. The application shell instantiates a cross-platform application comprising a plurality of application widgets. The application shell then determines that a first application widget of the plurality of application widgets executes instructions through an execution container of the cross-platform application. The application shell then receives a request comprising criteria from the first application widget, wherein the criteria specify an application widget to listen for communications from. The application shell then receives a communication from the second application widget and determines that the communication matches the criteria of the request by the first application widget.

Abstract: Certain aspects of the present disclosure provide techniques for facilitating communication between widgets of cross-platform applications. An exemplary system is configured to instantiate a cross-platform application comprising a plurality of application widgets. The system is further configured to determine that a first application widget of the plurality of application widgets executes instructions through an execution container of the cross-platform application. The system is further configured to receive a request comprising criteria from the first application widget, wherein the criteria specify an application widget to listen for communications from. The system is further configured to receive a communication from the second application widget and determines that the communication matches the criteria of the request by the first application widget. The system is further configured to transmit to the first application widget an update containing data from the communication.

Abstract: This disclosure relates to widget integration. Embodiments include receiving a workflow definition specifying one or more widgets to be loaded into a shell executing within a given application, the shell comprising a runtime environment, the one or more widgets comprising at least a first cross-platform widget. Embodiments include instantiating the runtime environment for the first cross-platform widget, the runtime environment including a bridge interface for facilitating communications between each widget in the one or more widgets and the given application. Embodiments include loading the first cross-platform widget into the runtime environment. Embodiments include processing, through the bridge interface, a communication from the first cross-platform widget running within the shell, wherein the communication comprises a result of executing a function.

Abstract: This disclosure relates to third-party integration of native and platform-agnostic based software components into a third-party application. An exemplary method generally includes receiving, a workflow definition specifying one or more widgets to be loaded into a runtime environment, the one or more widgets comprising at least the first cross-platform widget. A runtime environment is instantiated for the first cross-platform widget. The runtime environment includes a bridge interface for facilitating communications between each widget in the one or more widgets and a second application. The first cross-platform widget is loaded into the runtime environment. When a communication between the first cross-platform widget and the second application is received, the communication is processed through the bridge interface. The bridge interface invokes an event at one or more of the first cross-platform widget or the second application based on the communication.

Abstract: A computer-implemented method for facilitating an auto login from a browser to a website is provided. The browser sends a first request on behalf of a user for a secure page to the server for the website. The server then returns a response to the first request which includes HTML and one or more meta tags comprising a URL for a login page. Additionally, the meta tags specify the parameters the login page requires. After confirming that a credential for the user is stored in the browser, the browser issues a second request to the server with the credential and the URL for the login page from the meta tag. Next, the server returns a response to the second request which includes a cookie. After receiving the cookie, the browser saves the cookie and then reloads the secure page using the saved cookie without requiring a manual login operation.

Abstract: This disclosure generally relates to executing dynamically generated applications in a web browser-based shell. An exemplary method generally includes instantiating shared components in the browser-based shell, the shared components exposing a common runtime environment to widgets loaded into the browser-based shell. A first workflow definition representing a first step of a workflow is received. The first workflow definition specifies first widgets, comprising modular components that perform functions represented by the first step of the workflow and comprising a user interface definition, to be loaded into the browser-based shell. The first widgets are obtained from one or more of a remote source, a local cache, or a temporary memory and loaded into the browser-based shell. A user interface is generated according to the first workflow definition to exposes the function to a user which, when invoked, initiates a transition to a second step of the workflow.

Abstract: A computer-implemented method for facilitating an auto login from a browser to a website is provided. During operation, the browser sends a first request on behalf of a user for a secure page to the server for the website. The server then returns a response to the first request which includes HTML and one or more meta tags comprising a URL for a login page. Additionally, the meta tags specify the parameters the login page requires and the type of HTTP method it requires. After confirming that a credential for the user is stored in the browser, the browser issues a second request to the server with the credential (e.g., username and password) and the URL for the login page from the meta tag. Next, the server returns a response to the second request which includes a cookie. After receiving the cookie, the browser saves the cookie and then reloads the secure page using the saved cookie without requiring a manual login operation.

Abstract: A method for processing a service request, including receiving, from a client application, the service request which includes a header which includes transmission metadata and a client trace ID. An internal trace ID is appended to the service request and a request trace log including the client trace ID, the internal trace ID, and a time stamp corresponding to receiving the service request is generated. The method further includes selecting a cloud server including functionality to process the service request. The cloud server determines a dedicated computing cluster of a plurality of distributed cloud computing clusters to handle the service request and sends the service request to the dedicated computing cluster. Finally, the method includes recording, in the request trace log, an interaction of the dedicated computing cluster with the service request.

Abstract: A method for managing a pre-existing website of a business includes receiving, from the business, business information comprising a business name, a location, an industry, an address, a phone number, and a business description, generating a business profile comprising the business information, obtaining, from a keyword provider, a plurality of keywords relating to the business, generating a title comprising the business name, the location, and the plurality of keywords, generating a footer comprising the industry, the address, the phone number, and the plurality of keywords, generating a website content item comprising the business description and the plurality of keywords, generating a first modified website based on the pre-existing website of the business, publishing the first modified website to a network, and inserting, into the business profile, a first hyperlink comprising a first uniform resource locator (URL) pointing to a first network location of the first modified website.