Cloud Workflow Service for Third-Party App UI Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in managing user interaction flows within third-party applications, particularly when integrating with API services. These challenges include maintaining compatibility with changing API versions and supporting multiple user interaction flows, which can lead to complex development and maintenance processes.
Innovation Solution
A system and method that utilize a cloud-managed workflow service to guide client-implemented user interfaces. This involves processing a directed graph data model of user interaction workflows on a backend server, rendering UI data, and serving it to client applications. The system includes a workflow configuration that defines nodes and edges, allowing for the delegation of workflow management and versioning to the backend, reducing the burden on client applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If code and logic are developed within the application to enable API provider features, then the application can utilize API services, but the code needs to be constantly updated to accommodate API changes and new versions
Solution Approach 1:
The patent extracts the workflow management logic from the client application code and relocates it to a server-side workflow service. The client application only needs to invoke predefined workflow templates, while the server handles the complex logic of coordinating multiple API services. This separation allows the client code to remain simple and stable even when APIs change, as the adaptive logic resides on the server where it can be updated independently.
Solution Approach 2:
The patent implements dynamic workflow templates that can be configured and updated on the server side without requiring changes to the client application. The workflow templates define parameterized interaction flows that can adapt to different API versions and service changes. This dynamic configuration approach allows the system to remain adaptable while keeping the client codebase stable and simple.
2Adaptability or versatility
If an API service provider rolls out new features and updates, then the service capabilities are enhanced, but the development process of customer applications is complicated
Solution Approach 1:
The patent pre-configures workflow templates on the server side that encapsulate common interaction patterns with multiple API services. These templates are prepared in advance and can be selectively invoked by client applications. When new API features are released, the service provider can create new workflow templates or modify existing ones on the server side, allowing customers to adopt new features by simply changing their workflow configuration rather than rewriting integration code.
Solution Approach 2:
The patent creates universal workflow templates that can serve multiple purposes and work with different API service combinations. A single workflow template can be configured to work with various versions of APIs and different service providers through parameterization. This multi-functionality allows the same template framework to accommodate service feature updates without requiring separate development efforts for each scenario.
3Reliability
If SDK version support is maintained for older API versions, then backward compatibility is preserved, but changes to the API service can break functionality of older SDK versions
Solution Approach 1:
The patent introduces a server-side workflow service as an intermediary layer between the client SDK and the API services. The SDK remains stable and versioned, while the workflow service on the server handles the adaptation to different API versions. The workflow templates can specify which API version to use and handle any necessary transformations, allowing the SDK to maintain backward compatibility while the server-side logic adapts to new API features and versions.
Data Source
AI summary
A system and method for cloud management of user interactions on a client device comprising: initiating, in response to an initiation request of a client application, processing of a workflow configuration with an initial session state, wherein the workflow is a data model of a graph of nodes connected with directed edges, where the nodes include a set of node types that includes at least a pane node; iteratively processing the workflow configuration, initially using the initial session state, and thereby generating rendered panes for use in a user interaction flow of a client application, which comprises: following a next edge of the workflow configuration to determine a next workflow node, processing the next workflow node, which comprises, when the next workflow node is a pane node, rendering the pane node into a rendered pane, and sending the rendered panes to the client device.