Interface Modification Systems for Web Application Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing graphical user interfaces (GUIs) for web applications often include features that are not intuitive or overly complex, making it difficult for users to view and interact with information effectively.

Innovation Solution

An interface modification system that provides a graphical representation of a web application with a first layer for primary interactions and a second layer for secondary interactions, including feedback mechanisms, which receives user feedback, generates incident records, and stores them in a database, allowing for modifications to be identified and implemented using machine learning to improve the interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional graphical user interfaces are used to display web application components, then information can be communicated to users, but the interfaces become overly complicated and non-intuitive, reducing ease of operation

Engineering Contradiction:
Improveinformation communicationVSAvoidinterface usability
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The interface is divided into multiple layers: a first layer displaying primary web application components and a second layer for secondary interactions and feedback. This segmentation allows information to be organized hierarchically, presenting essential elements first while maintaining access to additional functionality without overwhelming the user with a single complex interface.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If comprehensive feedback mechanisms are added to the interface, then user feedback can be collected for improvements, but the interface complexity increases

Engineering Contradiction:
Improvefeedback collection capabilityVSAvoidinterface structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A second layer is introduced as an intermediary between the user and the primary interface components. This intermediary layer houses feedback mechanisms and secondary interactions, allowing comprehensive data collection while keeping the primary first layer clean and focused on core functionality. The intermediary layer mediates between user needs and system responses without adding complexity to the main interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple layers of interaction are implemented, then secondary interactions and feedback can be accommodated, but the device complexity increases

Engineering Contradiction:
Improveinteraction capabilityVSAvoidlayered structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The interface transitions from a two-dimensional flat structure to a multi-layered three-dimensional structure. By adding the vertical dimension of layers, the system can accommodate primary interactions in the first layer and secondary interactions plus feedback mechanisms in the second layer. This dimensional change allows comprehensive functionality without increasing horizontal complexity within each layer.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11989395B1Interface modification systems and methods
Publication Date: 2024.05.21 UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)
  • US11989395B1 patent drawing
  • US11989395B1 patent drawing
  • US11989395B1 patent drawing

AI summary

An interface modification system includes one or more processors configured to provide, to one or more client devices, a graphical representation of a web application. The graphical representation has a first layer including one or more components of the web application and a second layer configured for secondary interactions with the one or more components. The one or more processors are configured to receive, via the second layer and from the one or more client devices, feedback associated with the one or more components. Additionally, the one or more processors are configured to generate an incident record including the feedback and store the incident record in an incident database.