Interface modification systems and methods

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.

BACKGROUND

Interfaces, such as graphical user interfaces, may communicate information to users to allow viewing of and interaction with such information. In some instances, the interfaces may include features that are not intuitive or that are overly complicated. For example, the interfaces may include too much information or may be organized in a manner that is difficult to understand. It is now recognized that there is a need to improve such interfaces to facilitate viewing and interaction with the information.

BRIEF DESCRIPTION

In certain embodiments, 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.

In certain embodiments, a method includes providing, to one or more client devices, a graphical representation of a web application. The graphical representation includes 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 method also includes receiving, via the second layer and from the one or more client devices, feedback associated with the one or more components, generating an incident record including the feedback, and storing the incident record in an incident database.

In certain embodiments, a non-transitory computer-readable medium includes computer readable instructions, that when executed by one or more processors, causes the one or more processors to perform operations including providing, to one or more client devices, a graphical representation of a web application. The graphical representation includes 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 operations also include receiving, via the second layer and from the one or more client devices, feedback associated with the one or more components, generating an incident record comprising the feedback, and storing the incident record in an incident database.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

The present disclosure relates generally to a web application system, and more particularly to an interface modification system of the web application system that provides a graphical representation (e.g., a graphical user interface (GUI)) of a web application to client devices, receives feedback associated with the web application from the client devices, and generates and stores an incident record including the feedback. For example, the graphical representation may include a first layer that displays components of the web application, such that a user may view and/or interact with the components via the first layer. In certain embodiments, the first layer may allow primary interactions with the components (e.g., the first layer may provide a primary/central purpose for each component). Additionally, the graphical representation may include a second layer configured for secondary interactions with the components, such as providing feedback associated with the components. For example, the second layer may include, for each component, one or more feedback mechanisms (e.g., a data entry field configured to receive a text entry, a rating selector configured to receive a rating, a drop-down menu, and/or other suitable feedback mechanisms).

In an example embodiment, the graphical representation may depict a component, via the first layer, that allows a user to filter data related to the web application, such as data stored by the web application and/or data generated by the web application. A user viewing the graphical representation may not understand how to use the filtering mechanism and/or may have an idea to improving a functionality of the filtering mechanism. The user may provide, via a feedback mechanism of the second layer, feedback including a comment explaining that they do not understand how to use the filtering mechanism and/or their thoughts on a potential improvement to the filtering mechanism. The interface modification system may receive the feedback and generate and store an incident record including the feedback.

In certain embodiments, the interface modification system may identify a modification to the graphical representation based on the feedback, such as via machine learning. The interface modification system may generate and store a ticket indicative of instructions to implement the modification, such that a developer of the web application and/or other technical personnel may implement the modification based on the ticket. Thereafter, the interface modification system may generate and/or provide an additional graphical representation of the web application including the modification. In some embodiments, the interface modification may automatically implement the modification to the graphical representation without input from a developer or other technical personnel.

In certain embodiments, the interface modification system may provide a GUI including components of the web application that are configured to display information of the web application and/or that are configured for interaction with the web application. The interface modification system may receive input data indicative of user interaction with the GUI and determine an incident associated with the web application based on the data. For example, the input data may indicate that a user is switching between tabs of the GUI (e.g., between tabs of one component and/or tabs corresponding to multiple components) without taking an additional action, such as interacting with a component in a particular tab. Accordingly, the interface modification may determine that information in the tabs is confusing to the user, that the GUI does not include adequate instructions regarding the tabs, or another incident based on the input data. The interface modification system may generate and store an incident record indicative of such an incident, such that the incident may be resolved by a developer, other technical personnel, and/or by the interface modification system itself. Accordingly, the systems and methods described herein may facilitate modifying an interface based on user feedback to improve the functionality and ease of use of the interface.

With the foregoing in mind,FIG.1illustrates a block diagram of a web application system100including an interface modification system102that may provide a web application to client devices104and receive feedback corresponding to the web application. Additionally, the web application system100may include an incident database106, an interface database108, and/or an external website database110. In certain embodiments, the web application system100may include one or more of the client devices104. In some embodiments, the interface modification system102may include one or more of the client devices104, the incident database106, the interface database108, and/or the external website database110.

As illustrated, the interface modification system102includes an interface generation logic120, an interface modification logic122, an incident analysis logic124, and a user interface126. In some embodiments, the interface generation logic120, the interface modification logic122, the incident analysis logic124, and/or the user interface126may be omitted from the interface modification system102. The interface modification system102may provide, via the interface generation logic120and/or the interface modification logic122, a GUI (e.g., a graphical representation, an interface) of a web application to the client devices104. For example, in response to receiving a request for the GUI from a particular client device104, the interface generation logic120may generate a representation of the GUI, and the interface modification system102may transmit the representation of the GUI to the client device104.

In some embodiments, the interface modification system102and/or the interface generation logic120may retrieve the GUI from the interface database108and/or the external website database110and transmit the GUI to the client device104in response to receiving the request. The interface database108may include interfaces (e.g., GUIs, graphical representations) corresponding to certain web applications and/or interfaces of various types (e.g., tabbed interfaces, windowed interfaces), and the interface modification system102may select a particular interface from the interface database108based on the request received from the client device104(e.g., the request may indicate a particular web application and/or a type of interface). The external website database110may include a listing of external websites corresponding to web applications, such that the interface modification system102may determine the GUI to be provided to the client device104based on an external website corresponding to the particular web application.

The client devices104may display the GUI of the web application for viewing by users of the client devices104. The GUI may display components of the web application for viewing and/or interaction by the users. For example, the GUI may include a first layer displaying the components and that is configured for primary interactions between the users and the components. Such primary interactions may generally correspond to a primary function (e.g., purpose) of the components. For example, a primary function of a data filter may be to allow the user to filter and select data provided by the web application. Additionally, the GUI may include a second layer configured for secondary interactions with the components. The secondary interactions may include providing feedback regarding the components displayed via the first layer. For example, the second layer may include one or more feedback mechanisms, such as a data entry field configured to receive a text entry, a rating selector configured to receive a rating, a drop-down menu, and/or other suitable feedback mechanisms.

The client device104may display the GUI, and a user of the client device104may perform primary interactions with the web application via the first layer and secondary interactions with the web application via the second layer. In certain embodiments, the GUI may be configured to allow the user to toggle between the first layer and second layer. In some embodiments, the GUI may default to displaying the first layer to the user, and the user may select an option that displays the second layer, thereby allowing the user to provide feedback for a component initially displayed via the first layer. The second layer may not be visible while the first layer is displayed, and/or while the first layer is being used (e.g., interacted with) by the user. Additionally or alternatively, the second layer may be overlaid onto the first layer when prompted/selected by the user, such that the user may see the feedback mechanism for a particular component overlaid on the particular component and/or overlaid on the first layer generally. For example, a user may provide an input indicating that they wish to provide feedback regarding a particular component, and in response, the GUI (e.g., the interface modification system102via the GUI) may display the second layer including the feedback mechanism for that particular component.

The interface modification system102may receive the feedback provided by the user, such as via the interface modification logic122(e.g. at the interface modification logic122). The feedback may include an incident for the particular component selected or identified by the user, and for which the feedback mechanism was provided in the second layer of the GUI. In some embodiments, the feedback may correspond to multiple components. The feedback may include a potential issue with the component, a potential improvement to the display and/or function of the component, a comment, a rating, and/or other suitable feedback.

The interface modification system102, such as via the interface modification logic122or the incident analysis logic124, may generate an incident record indicative of the feedback. The record may include the feedback, information identifying the component, information about the user that provided the feedback (e.g., name, title, rank, age, location), information regarding the client device104of the user (e.g., type, brand, serial number, and/or a time and date that the feedback was provided). The interface modification system102may store the incident record in the incident database106, which may be a repository storing incident records for the particular web application corresponding to the feedback and/or a repository for incident records corresponding to multiple, related web applications.

In certain embodiments, the user interface126may display the incident record for viewing by a user of the interface modification system102, such as a developer of the web application and/or other technical personnel (e.g., personnel of a company's IT department). For example, the user interface126may provide an interface allowing the user to retrieve and/or view the incident record. The user may then determine a modification to the GUI and implement the modification, thereby addressing the feedback provided by the user of the client device104. The user interface126may include an electronic display to provide a visual representation of information, for example, via a GUI, an application interface, text, a still image, and/or video content. The user interface126may be configured to receive inputs from a user (e.g., the developer of the web application and/or other technical personnel).

Additionally or alternatively, the incident analysis logic124may analyze the incident identified based on the feedback (e.g., as indicated in the incident record) to determine the modification to the GUI. For example, using machine learning, the incident analysis logic124may determine that a particular modification to the first layer of the GUI would address the feedback, such as replacing a component of the GUI, adding or removing a component, modifying a font or size of text in the component, modifying an interactive function (e.g., a drop-down menu, a free text field, a rating selector) of a component, or another suitable modification. In certain embodiments, the interface modification system102, via the incident analysis logic124, may train and/or enhance a machine learning model based on the feedback from the user (e.g., the developer of the web application and/or other technical personnel) received via the user interface126.

For example, some processes (e.g., analyzing feedback received from one or more users of the client devices104, determining modifications to the GUI, analyzing the input data indicative of user interactions described below) described herein may be performed by machine learning circuitry using the feedback, the incident records, and/or input from a user. The machine learning circuitry (e.g., circuitry used to implement machine learning algorithms or logic) may access the mapping data and the additional information to identify patterns, correlations, or trends associated with the data. The feedback may be sourced from a multitude of diverse client devices104and users of the client devices104, and new data patterns not previously attainable based on feedback without machine learning may emerge. As used herein, machine learning may refer to algorithms and statistical models that computer systems use to perform a specific task with or without using explicit instructions. For example, a machine learning process may generate a mathematical model based on a sample of the clean data, known as “training data,” in order to make predictions or decisions without being explicitly programmed to perform the task.

Depending on the inferences to be made, the machine learning circuitry may implement different forms of machine learning. In some embodiments, a supervised machine learning may be implemented. In supervised machine learning, the mathematical model of the feedback and modifications to the GUI contains both the inputs and the desired outputs. The feedback and modifications to the GUI is referred to as “training data” and is essentially a set of training examples. Each training example has one or more inputs and the desired output, also known as a supervisory signal. In a mathematical model, each training example is represented by an array or vector, sometimes called a feature vector, and the training data is represented by a matrix. Through iterative optimization of an objective function, supervised learning algorithms learn a function that can be used to predict the output associated with new inputs. An optimal function will allow the algorithm to correctly determine the output for inputs that were not a part of the training data. An algorithm that improves the accuracy of its outputs or predictions over time is said to have learned to perform that task.

Supervised learning algorithms may include classification and regression. Classification algorithms are used when the outputs are restricted to a limited set of values, and regression algorithms are used when the outputs may have any numerical value within a range. Similarity learning is an area of supervised machine learning closely related to regression and classification, but the goal is to learn from examples using a similarity function that measures how similar or related two objects (e.g. common feedback between two client devices104, common modifications for the same or different GUIs) are.

Additionally and/or alternatively, in some situations, it may be beneficial for the machine-learning circuitry to utilize unsupervised learning (e.g., when particular output types are not known). Unsupervised learning algorithms take feedback that contains only inputs, and find structure in the data, like grouping or clustering of feedback (e.g., types of feedback, common subject matters within feedback). The algorithms, therefore, learn from test data that has not been labeled, classified or categorized. Instead of responding to feedback, unsupervised learning algorithms identify commonalities in the feedback and react based on the presence or absence of such commonalities in each new piece of feedback.

Cluster analysis is the assignment of a set of observations (e.g., feedback) into subsets (called clusters) so that observations within the same cluster are similar according to one or more predesignated criteria, while observations drawn from different clusters are dissimilar. Different clustering techniques make different assumptions on the structure of the feedback, often defined by some similarity metric and evaluated, for example, by internal compactness, or the similarity between users of the same cluster, and separation, the difference between clusters. Predictions or correlations may be derived by the machine learning circuitry. For example, groupings and/or other classifications of the feedback may be used to identify potential modifications to GUIs. The predictions may be provided to downstream applications, which may perform actions based upon the predictions. The actions that are performed may be mediated through a controller, either directly or through a coupled secure system, that has access to the feedback.

After determining the modification to the GUI, such as based on user input provided via the user interface126and/or via incident analysis logic124, the interface modification logic122may implement the modification to the GUI to generate an additional, modified representation of the GUI (e.g., an additional graphical representation of the web application). The additional representation of the GUI may include the first layer and the second layer of the previous representation, along with the modification to the GUI described above. The interface modification system102may provide (e.g., send, transmit) the additional representation of the GUI to the client devices104, which may then display the GUI for viewing and/or interactions by the users of the client devices104. The users may provide additional feedback regarding the same component and/or other components of the GUI, and the interface modification system102may generate additional incident records indicative of the feedback and/or determine/implement additional modifications to the GUI that address the feedback, such that the process described herein may be performed iteratively by the interface modification system102until users of the client devices104stop providing feedback.

In certain embodiments, the interface modification system102may determine whether certain feedback has been received from a threshold number of the client devices104and/or a threshold number of users of the client devices104, and in response, generate the incident record. The interface modification system102may determine the threshold number of client devices104and/or the threshold number of users based on a type of the feedback, a significance of the feedback, and/or an amount of the client devices104generally.

Additionally or alternatively, the interface modification system102may aggregate the feedback received from the client devices104. The interface modification system102may determine whether feedback received from multiple (e.g., 2, 3, 4, 5, 6, 10, 15, 20, 50, 100, 1000) client devices104is exceeds a threshold level of similarity, and in response, generate the incident record. The interface modification system102may determine the threshold level of similarity based on a type of the feedback, a significance of the feedback, and/or an amount of the client devices104generally. In some embodiments, the interface modification system102may use machine learning to determine whether feedback received from multiple client devices104exceeds the threshold level of similarity, such as by comparing text within the multiple instances of feedback.

In certain embodiments, the interface modification system102may receive input data indicative of user interactions with the GUI from the client devices104and identify an incident based on the input data. For example, the input data may indicate selections (e.g., clicking or otherwise selecting) of certain components of the GUI, selections of the portions of the components, time periods between two or more user interactions, scrolling, and/or other types of user interactions with the GUI. In certain embodiments, the input data may include data from a secondary device, such as a smartphone, a smartwatch, and/or a webcam. The input data from such devices may include heart rate data, motion data, user interactions on the smartphone and/or the smartwatch, and other data that may be obtained from such devices.

The interface modification system102may determine an incident based on the input data, such as a component of the GUI, a portion of a component, and/or another aspect of the GUI that may not be optimized for user interaction and/or for which the user may have an issue. By way of example, the input data may indicate that the user is clicking/switching between multiple tabs without taking an additional action in a particular tab. Additionally, the input data may indicate a time period that the user views each tab (e.g., a time period between two or more instances of user interactions). The interface modification system102, via the incident analysis logic124, may determine that there is a potential issue with the one or more of the tabs and generate and store an incident record indicative of the incident. In certain embodiments, the interface modification system102may determine that there is an incident based on the time period exceeding a threshold amount of time. The interface modification system102may determine the threshold amount of time based on one or more types of user interactions associated with the multiple instances of user interaction, a length of the particular time period, and/or a user input. A user of the interface modification system102may review the incident record to determine if the incident is appropriate (e.g., valid) and/or may determine the modification of the GUI that addresses the incident. In certain embodiments, after identifying the incident and/or generating the incident record, the interface modification system102may determine the modification to the GUI and/or implement the modification, as described herein.

In another example where the input data may include heart rate data of the user (e.g., received via the user's smartwatch) and/or motion data (e.g., received via the user's smartphone, smartwatch, and/or webcam), the interface modification system102, via the incident analysis logic124, may determine that the user's heart rate changed (e.g., increased, decreased) when viewing and/or interacting with a particular component of the GUI and/or that the user's motion (e.g., movement of head, arms, upper body) changed (e.g., increased, decreased) when viewing and/or interacting with the particular component. The interface modification system102, via the incident analysis logic124, may determine that there is potentially an issue with the component and may generate and store an incident record indicating the potential issue. For example, the interface modification system102, via the incident analysis logic124, may determine that the user's heart rate increased beyond a threshold heart rate and/or beyond a threshold percentage and determine that the user experienced stress while using a particular component of the GUI. Accordingly, the interface modification system102, via the incident analysis logic124, may determine that there is potentially an issue with the particular component and may generate and store an incident record indicating the potential issue in response to the user's heart rate increasing beyond threshold heart rate and/or the threshold percentage and/or in response to determining that the user experienced stress while using the particular component. In some embodiments, the interface modification system102may automatically determine and/or implement the modification to the GUI based on the incident, as described herein.

In certain embodiments, the interface modification system102may provide a modified (e.g., additional) GUI (e.g., graphical representation) to only certain client devices104based on the feedback being received from those client devices104and/or from similar client devices104. For example, the GUI may initially be the same for all client devices, and the interface modification system102may customize the GUI to include different modifications for different client devices104and/or different groups of client devices104.

To provide an example of the feedback and modification to an interface described above,FIG.2illustrates a graphical representation200(e.g., a GUI) of a web application, an incident record202corresponding to the graphical representation200, and the incident database106that may store the incident record202. The graphical representation200may generally display information, metrics, selectable options, and/or other aspects of the web application. For example, the graphical representation200includes tabs204(e.g., a performance tab206, a finance tab208, a rewards tab210, a help tab212, a settings tab214). In certain embodiments, the graphical representation may include more or fewer tabs and/or tabs other than the illustrated tabs204. One or more of the client devices104may display the graphical representation200to allow users of the client devices104to view and/or interact with the web application.

In the illustrated embodiment, the performance tab206is selected and is displaying components220of the web application, including a dial component222, a panel component224, and a document component226, among others. The components220may be displayed via a first layer of the graphical representation200, such that the user of the client device104may view and/or interact with the components220via the first layer. Additionally, the first layer may include a selectable option230for one or more of the components220. As illustrated, the user has selected the selectable option230for (e.g., adjacent to, associated with) the dial component222, as indicated by a mouse curser232. The dial component222includes a knob that allows a user to adjust a value between 0 and 100.

Selection of the selectable option230may cause the graphical representation200to display at least a portion of a second layer including a feedback mechanism240for the dial component222. Accordingly, the second layer is displayed in the illustrated embodiment. The feedback mechanism240is a free text field configured to allow the user of the client device104to provide feedback regarding the dial component222. For example, the user may believe that the dial component222may function better as a slider, such as a slider that also allows the user to adjust a value between 0 and 100. Accordingly, in the illustrated embodiment, the user has entered text indicative of this feedback into the feedback mechanism240, which includes options242allowing the user to send the feedback or to cancel the feedback. Selection of the send option242causes the feedback to be sent to the interface modification system102. In other embodiments and/or for other components220, the feedback mechanism may include a drop-down menu, a rating selector, or another suitable mechanism configured to allow the user to provide feedback.

In response to receiving the feedback from the client device, the interface modification system102may generate the incident record202. In the illustrated embodiment, the incident record includes a title250(e.g., IT TICKET), the feedback of the user in a feedback section252(e.g., CLIENT FEEDBACK), an identifier254of the dial component222(e.g., DIAL100), and selectable options256allowing a user of the interface modification system102to approve or disapprove storing the generated incident record202. In other embodiments, the incident record202may include more, fewer, and/or different sections.

In response to the user selecting the “Y” selectable option256(e.g., a YES option), the interface modification system102may store the incident record202in the incident database106, thereby allowing the user to view and approve the incident record202. The incident indicated by the incident record202may then be resolved by a developer and/or other technical personnel. In certain embodiments, the interface modification system102, via the interface modification logic122, may proceed to determine and/or implement a modification to the graphical representation200after receiving the feedback from the client device104and/or generating the incident record. For example, the interface modification logic122may automatically determine that the dial component222should be replaced by a slider component based on the feedback provided by the user. Accordingly, the interface modification logic122may generate and send an additional graphical representation of the web application including a slider component in place of or in addition to the dial component222. An example of a graphical representation including a modification is described below in reference toFIG.6.

In certain embodiments, the interface modification system102, via the interface generation logic120and/or the interface modification logic122, may traverse a markup document of the web application to determine which portions of the markup document and/or which components of the web application may potentially receive feedback from the users of the client devices104. After identifying such components, the interface modification system102may insert an identifier code into the markup document that causes the client devices104to display the selectable option230for such components (e.g., the components220in the illustrated embodiment).

Additionally or alternatively, after the user provides the feedback to the feedback mechanism240, a comment may be inserted into the markup document indicative of the feedback, and the markup document including the feedback may be transmitted to the interface modification system102. Accordingly, the interface modification system102may traverse the markup document to determine the feedback provided by the user of the client device104. In some embodiments, the interface modification system102may insert the comment into the markup document after the user provides such feedback (e.g., after the user selects the send option242of the feedback mechanism240).

In certain embodiments, the interface modification system102may receive input data indicative of user interactions with the web application (e.g., with the graphical representation200) from the client devices104. The user interactions may include interactions with the tabs204, the components220, and/or other portions of the graphical representation200. The incident analysis logic124may analyze the input data to determine a potential incident associated with the graphical representation. By way of example, the input data may indicate user interactions with the tabs204, such as a user selecting and switching between the tabs204. Additionally or alternatively, the input data may indicate a time period between the user interactions (e.g., a time period between selections of tabs204).

The incident analysis logic124may analyze the input data to determine a potential incident. For example, the incident analysis logic124may determine that the user has switched back and forth between the tabs204without interacting further with a specific tab204(e.g., with a component220in a specific tab204). Accordingly, the incident analysis logic124may determine that one or more tabs204are confusing to the user, that a particular component220and/or particular information in the tabs204is difficult to find and/or not present, or another suitable incident based on the input data. The incident analysis logic124may generate an incident record indicative of such an incident and store the incident record in the incident database106.

Additionally or alternatively, interface modification logic122may determine and/or implement a modification to the graphical representation200based on the identified incident. For example, the interface modification logic122may determine that the tabs204should be rearranged and/or that the components220within the tabs204should be rearranged (e.g., rearranged within the same tab204and/or moved to other tabs204). The interface modification system102provide an additional graphical representation of the web application to the client devices104including such a modification.

FIG.3illustrates a block diagram of components that may be part of the interface modification system102ofFIG.1. For example, the interface modification system102may include a communication component300, a processor302, a memory304, a storage306, input/output (I/O) ports308, an output device310(e.g., a display or a speaker), or any of a variety of other components that enable the interface modification system102to carry out the techniques described herein. The communication component300may be a wireless or wired communication component that may facilitate communication between the interface modification system102, the client devices104, the incident database106, the interface database108, and/or the external website database110.

The processor302may be any suitable type of computer processor or microprocessor capable of executing computer-executable code. The processor302may also include multiple processors that may perform the operations described below. The memory304and the storage306may be any suitable articles of manufacture that can serve as media to store processor-executable code, data, or the like. These articles of manufacture may represent computer-readable medium (e.g., any suitable form of memory or storage) that may store the processor-executable code used by the processor302to perform the presently disclosed techniques. The memory304and the storage306may also be used to store the data, various other software applications, and the like. The memory304and the storage306may represent non-transitory computer-readable medium (e.g., any suitable form of memory or storage) that may store the processor-executable code used by the processor302to perform various techniques described herein. For example, the non-transitory computer-readable medium may store computer readable instructions, that when executed by the processor302, causes the processor302to perform operations, such as the operations described below in reference toFIGS.4and5. It should be noted that non-transitory merely indicates that the medium is tangible and not a signal.

The I/O ports308may be interfaces that may couple to other peripheral components such as input devices (e.g., keyboard, mouse), sensors, input/output (I/O) modules, and the like. The output device310may operate to depict indications associated with software or executable code processed by the processor302. In one embodiment, the output device310may be an input device. For example, the output device310may include a touch display capable of receiving inputs from a user of the interface modification system102. The output device310may be any suitable type of display, such as a liquid crystal display (LCD), plasma display, or an organic light emitting diode (OLED) display, for example. In one embodiment, the output device310may depict or otherwise provide the indications described above regarding the asset protection plans and adjustments to the asset protection plan. In certain embodiments, the output device310may include and/or may display the user interface126. It should be noted that the components described above with regard to the interface modification system102are exemplary components, and the interface modification system102may include additional or fewer components as shown.

FIG.4illustrates a flow chart of a method400for receiving feedback associated with a web application and generating and storing an incident record including the feedback, which may be performed using the interface modification system102ofFIG.1. The following description of the method400will be described as being performed by the interface modification system102, but it should be noted that any suitable processor-based device may be specially programmed to perform any of the methods described herein. Moreover, although the following description of the method400is described as including certain steps performed in a particular order, it should be understood that the steps of the method400may be performed in any suitable order, that certain steps may be omitted, and/or that certain steps may be added.

At block402, the interface modification system102, via the interface generation logic120and/or the interface modification logic122, may provide a representation of a GUI (e.g., a graphical representation of a web application) to the client devices104. For example, in reference toFIG.2, the interface modification system102may provide the graphical representation200to the client devices104.

At block404, the interface modification system102, via the incident analysis logic124, may receive feedback associated with the web application via a second layer of the GUI and from the client devices104. For example, the interface modification system102may receive the feedback shown in the feedback mechanism240.

At block406, the interface modification system102, via the incident analysis logic124, may generate an incident record including the feedback, and at block408, store the incident record. For example, the interface modification system102may generate the incident record202and store the incident record202in the incident database106.

FIG.5illustrates a flow chart of a method for providing a graphical user interface (GUI) for a web application, receiving input data indicative of interaction with the GUI, and identifying an incident based on the input, which may be perform using the interface modification system102ofFIG.1. The following description of the method500will be described as being performed by the interface modification system102, but it should be noted that any suitable processor-based device may be specially programmed to perform any of the methods described herein. Moreover, although the following description of the method500is described as including certain steps performed in a particular order, it should be understood that the steps of the method500may be performed in any suitable order, that certain steps may be omitted, and/or that certain steps may be added.

At block502, the interface modification system102, via the interface generation logic120and/or the interface modification logic122, may provide, to the client devices104, a GUI including interactive components configured for interaction with a web application. For example, in reference toFIG.2, the interface modification system102may provide the graphical representation200to the client devices104.

At block504, the interface modification system102, via the incident analysis logic124, may receive input data indicative of interaction with the GUI from the client devices104. For example, the interface modification system102may receive input data indicative of user interactions with the tabs204, the components220in the tabs204, and/or other portions of the graphical representation200ofFIG.2.

At block506, the interface modification system102, via the incident analysis logic124, may determine an incident associated with the web application based on the input data. For example, based on the user interactions with the tabs204and/or the components220, the interface modification system102may determine a potential incident with the graphical representation200, such as an incident associated with a particular tab204and/or a particular component220for which a user is having an issue (e.g., the incident may identify a potential issue and/or improvement for the tab204and/or the component220).

At block508, the interface modification system102, via the incident analysis logic124, may generate an incident record including the feedback, and at block510, store the incident record. For example, the interface modification system102may generate an incident record indicating the potential issue with the particular tab204and/or the particular component220and store the incident record in the incident database106.

FIG.6illustrates a graphical representation600and an additional graphical representation602of a web application before and after a modification, respectively, which may be implemented using the interface modification system102ofFIG.1and/or implemented based on an incident record generated using the interface modification system102ofFIG.1. The graphical representation600may generally display information, metrics, selectable options, and/or other aspects of the web application. For example, the graphical representation600includes tabs604(e.g., a statement tab606, a rewards tab608). In certain embodiments, the graphical representation600may include more or fewer tabs and/or tabs other than the illustrated tabs604. One or more of the client devices104may display the graphical representation600to allow users of the client devices104to view and/or interact with the web application.

The graphical representation600may generally be for a user's bank, such that the graphical representation600may be provided by the bank or by a third party on behalf of the bank. In the illustrated embodiment, the graphical the statement tab606includes a listing620of deposits and withdrawals in a text format. The deposits generally indicate monetary additions/increases to a balance of a user's account, and the withdrawals may generally indicated monetary subtractions/decreases to the account. Additionally, the rewards tab608includes a listing622of additions to points in a text format that correspond to the deposits of the listing620in the statement tab606. For example, the points may earned by the user for making deposits to the account. In certain embodiments, the points may be earned for withdrawals from the account and/or for expenditures from the account. The points may be used by the user for travel coupons and/or other suitable rewards.

A user of the graphical representation600may provide feedback regarding the portion(s) of the graphical representation600, such as the statement tab606, the rewards tab608, the listing620, and/or the listing622. For example, the user may not understand what “DEPOSIT” and/or “WITHDRAWAL” mean/indicate in the listing620and/or what “POINTS” means/indicates in the listing622. The user may provide feedback via a feedback mechanism (e.g., a data entry field configured to receive a text entry, a rating selector configured to receive a rating, a drop-down menu) indicating that they do not understand these aspects of the graphical representation600. The interface modification system102may receive the feedback, generate an incident record including the feedback, and/or store the incident record in the incident database106.

The incident record may be presented to a user of the interface modification system102, such as via the user interface126, and the user may determine and/or generate a modification to the graphical representation600that addresses the feedback. For example, the user may determine that adding graphical elements to the graphical representation600and/or replacing portions of the graphical representation600with such graphical elements may address the feedback (e.g., may improve a client device user's understanding of the terms “deposit”, “withdrawal”, and/or “points”). In the illustrated embodiment, the user may determine that graphical elements630shown in a listing632of the additional graphical representation602may address the feedback, and/or that graphical elements634shown in a listing636of the additional graphical representation602may address the feedback. Accordingly, the user may generate the additional graphical representation602including this modification, and the additional graphical representation602may be transmitted to the client devices104, thereby providing an interface that the user of the client device104may better understand. In certain embodiments, the user may provide only the modification to the graphical representation600, and the interface modification logic122may generate the additional graphical representation602including the modification.

Additionally or alternatively, the interface modification system102may automatically determine the modification to the graphical representation based on the feedback. For example, the interface modification system102may determine (e.g., via machine learning) that providing the graphical elements630and/or634would address the feedback by provided by the user of the client device104. As such, the interface modification logic122may generate the additional graphical representation602including the modification and/or transmit the additional graphical representation602to the client device104for viewing and/or interaction by the user.

Accordingly, the web application system, via the interface modification system described herein, may provide a graphical representation (e.g., a GUI) of a web application to client devices, receive feedback associated with the web application from the client devices, and generate and store an incident record including the feedback. For example, the graphical representation may include a second (e.g., additional, background) layer that allows users to provide feedback via feedback mechanisms. The interface modification system may allow a user to determine and/or generate a modification to the graphical representation based on the feedback, and/or the interface modification system may automatically determine and/or generate the modification. The interface modification system may provide an additional graphical representation (e.g., an additional representation of the GUI) including the modification to the client device, thereby allowing the user of the client device to view and/or interact with the modified, additional graphical representation. Accordingly, the web application system, via the interface modification system, may facilitate improvements to interfaces, thereby providing users of such interfaces improved and faster interface experiences.