Embedded API Explorer for Visualizing Attribute Relationships

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face challenges in learning and adapting to complex application programming interfaces (APIs), particularly due to their domain-specific nature and frequent updates, which require significant efforts to modify existing application code for compatibility with new API versions.

Innovation Solution

An embedded API explorer within a developer interface provides a graphical user interface that assists users by visually indicating relationships between API attributes and user interface components, allowing developers to easily identify how API code relates to application components and navigate between different API versions, using techniques such as metadata mapping and string similarity analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If developers manually learn and adapt to complex APIs through documentation and code modification, then they can achieve compatibility with new API versions, but the time and effort required increases significantly

Engineering Contradiction:
ImproveAPI compatibilityVSAvoidtime to modify code
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces an intermediary system consisting of metadata annotations and string similarity analysis that automatically maps relationships between API attributes and user interface components. This intermediary layer eliminates the need for developers to manually trace and understand complex API relationships, significantly reducing the time required to adapt code to new API versions while maintaining compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates simplified copies of API relationships through metadata annotations that capture the essential mappings between API attributes and UI components. These metadata copies serve as reference guides that developers can query to understand API relationships without needing to deeply comprehend the entire API structure, thereby reducing learning time and adaptation effort.

Inventive Principle:
Principle #26Copying

2Ease of operation

If comprehensive API documentation is provided to help developers understand domain-specific concepts, then learning effectiveness improves, but the complexity and length of documentation increases

Engineering Contradiction:
ImproveAPI learning easeVSAvoiddocumentation complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments comprehensive API documentation into discrete, queryable metadata annotations associated with individual API attributes and user interface components. Instead of presenting developers with a single large documentation corpus, the system divides information into small, context-specific units that can be retrieved on-demand through the development environment, making the documentation easier to navigate and understand while maintaining completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables self-service documentation delivery where the development environment automatically provides relevant API information contextually based on the code being written or reviewed. The system serves documentation needs directly at the point of use through metadata queries and string similarity matching, eliminating the need for developers to manually search through comprehensive documentation and reducing the perceived complexity.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If developers manually trace relationships between API code and user interface components, then they can understand the mapping, but the process becomes tedious and error-prone

Engineering Contradiction:
Improvemapping accuracyVSAvoidease of identifying relationships
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent introduces metadata annotations as an intermediary layer that automatically captures and stores the precise mappings between API attributes and user interface components. This intermediary metadata layer provides accurate relationship information without requiring developers to manually trace connections through code, thereby maintaining high mapping precision while dramatically improving ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the manual mechanical process of tracing API relationships with automated string similarity analysis and metadata querying. Instead of developers manually following code paths and identifying relationships, the system uses automated text analysis algorithms to match and identify relationships between API attributes and UI components, eliminating manual errors and reducing effort.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11126406B1Embedded application programming interface explorer
Publication Date: 2021.09.21 INTUIT INC
  • US11126406B1 patent drawing
  • US11126406B1 patent drawing
  • US11126406B1 patent drawing

AI summary

Certain aspects of the present disclosure provide techniques for providing a graphical user interface to assist a user of an application programming interface (API). Embodiments include determining that the user has selected an attribute of the API within an API explorer. The API explorer may be displayed with a developer interface of a web application. Embodiments further include identifying a user interface component of the web application that is related to the attribute of the API. Embodiments further include displaying an indication within the developer interface that the user interface component is related to the attribute of the API.