# US 2021/0165668 A1 · Third party integration of plugins and widgets

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

- Number: US 2021/0165668 A1
- Document ID: US20210165668A1
- Status: Published application
- Kind: A1
- Application number: 17/177,849
- Filed: 2021-02-17
- Published: 2021-06-03
- Earliest claimed: 2017-12-22
- Assignees: Intuit Inc.
- Applicants: Intuit Inc.
- Inventors: Anshu VERMA; Carlos AMBROZAK; Tapasvi MOTURU; Muzaffar H. MALIK; Jessica Yen Yen SPERLING
- Web page: https://patentgrep.com/patent/US20210165668A1

## CPC

- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 3/04817: using icons (graphical or visual programming using iconic symbols G06F8/34)
- G06F 8/20: Software design
- G06F 9/54: Interprogram communication
- G06F 2209/461: Bridge
- G06F 2209/482: Application
- G06F 2209/545: Gui
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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. Embodiments include determining, by the bridge interface, that a condition has been satisfied based on the communication and transmitting a message to the given application based on the condition being satisfied.

## Claims

### Claim 1

A system comprising:
one or more processors; and
a memory comprising executable instructions that, when executed by the one or more processors, cause the system to:
receive, from an application server, 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 cross-platform widget;
obtain, from the application server, the cross-platform widget;
instantiate the runtime environment for the 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, wherein the given application runs outside of the shell;
load the cross-platform widget into the runtime environment;
process, through the bridge interface, a communication from the cross-platform widget running within the shell;
determine, by the bridge interface, that a condition has been satisfied based on the communication; and
transmit, by the bridge interface, a message to the given application based on the condition being satisfied.

### Claim 2 (depends on 1)

The system of claim 1, the memory further comprising executable instructions that, when executed by the one or more processors, cause the system to:
receive, from the cross-platform widget, an additional message to transmit to the application server, the additional message including an indication of a function to be invoked at the application server; and
transmit the additional message to the application server.

### Claim 3 (depends on 1)

The system of claim 1, the memory further comprising executable instructions that, when executed by the one or more processors, cause the system to:
receive, from the application server, a second workflow definition identifying an additional cross-platform widget to be loaded into the runtime environment;
determine that the additional cross-platform widget is different than the cross-platform widget;
unload the cross-platform widget from the runtime environment;
load the additional cross-platform widget into the runtime environment; and
expose functionality of the additional cross-platform widget to the given application.

### Claim 4 (depends on 3)

The system of claim 3, wherein a function comprises a transition by the given application from the cross-platform widget to the additional cross-platform widget.

### Claim 5 (depends on 1)

The system of claim 1, wherein the communication comprises a message to invoke a function at the given application and data from the cross-platform widget.

### Claim 6 (depends on 1)

The system of claim 1, the memory further comprising executable instructions that, when executed by the one or more processors, cause the system to process, through the bridge interface, a given communication to the cross-platform widget running within the shell from the given application, wherein the given communication specifies a function to be invoked at the cross-platform widget.

### Claim 7 (depends on 6)

The system of claim 6, the memory further comprising executable instructions that, when executed by the one or more processors, cause the system to transmit, by the bridge interface, parameters for executing the function at the cross-platform widget based on the given communication.

### Claim 8

A method for widget integration, comprising:
receiving, from an application server, 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 cross-platform widget;
obtaining, from the application server, the cross-platform widget;
instantiating the runtime environment for the 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, wherein the given application runs outside of the shell;
loading the cross-platform widget into the runtime environment;
processing, through the bridge interface, a communication from the cross-platform widget running within the shell;
determining, by the bridge interface, that a condition has been satisfied based on the communication; and
transmitting, by the bridge interface, a message to the given application based on the condition being satisfied.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
receiving, from the cross-platform widget, an additional message to transmit to the application server, the additional message including an indication of a function to be invoked at the application server; and
transmitting the additional message to the application server.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
receiving, from the application server, a second workflow definition identifying an additional cross-platform widget to be loaded into the runtime environment;
determining that the additional cross-platform widget is different than the cross-platform widget;
unloading the cross-platform widget from the runtime environment;
loading the additional cross-platform widget into the runtime environment; and
exposing functionality of the additional cross-platform widget to the given application.

### Claim 11 (depends on 10)

The method of claim 10, wherein a function comprises a transition by the given application from the cross-platform widget to the additional cross-platform widget.

### Claim 12 (depends on 8)

The method of claim 8, wherein the communication comprises a message to invoke a function at the given application and data from the cross-platform widget.

### Claim 13 (depends on 8)

The method of claim 8, further comprising processing, through the bridge interface, a given communication to the cross-platform widget running within the shell from the given application, wherein the given communication specifies a function to be invoked at the cross-platform widget.

### Claim 14 (depends on 13)

The method of claim 13, further comprising transmitting, by the bridge interface, parameters for executing the function at the cross-platform widget based on the given communication.

### Claim 15

A method for widget integration, comprising:
receiving, from an application server, 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 cross-platform widget;
obtaining, from the application server, the cross-platform widget;
instantiating the runtime environment for the 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, wherein the given application runs outside of the shell;
loading the cross-platform widget into the runtime environment;
processing, through the bridge interface, a communication from the cross-platform widget running within the shell, wherein the communication comprises a result of executing a function;
determining, by the bridge interface, that a value associated with the communication exceeds a threshold; and
transmitting, by the bridge interface, a message to the given application based on the value associated with the communication exceeding the threshold.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
receiving, from the cross-platform widget, an additional message to transmit to the application server, the additional message including an indication of an additional function to be invoked at the application server; and
transmitting the additional message to the application server.

### Claim 17 (depends on 15)

The method of claim 15, further comprising:
receiving, from the application server, a second workflow definition identifying an additional cross-platform widget to be loaded into the runtime environment;
determining that the additional cross-platform widget is different than the cross-platform widget;
unloading the cross-platform widget from the runtime environment;
loading the additional cross-platform widget into the runtime environment; and
exposing functionality of the additional cross-platform widget to the given application.

### Claim 18 (depends on 17)

The method of claim 17, wherein a function comprises a transition by the given application from the cross-platform widget to the additional cross-platform widget.

### Claim 19 (depends on 15)

The method of claim 15, wherein the communication comprises a message to invoke an additional function at the given application and data from the cross-platform widget.

### Claim 20 (depends on 15)

The method of claim 15, further comprising processing, through the bridge interface, a given communication to the cross-platform widget running within the shell from the given application, wherein the given communication specifies the function to be invoked at the cross-platform widget.
