Feedback Manager for Software Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users often uninstall software applications due to lack of familiarity, leading to uncollected valuable feedback that could improve the application, as they are not encouraged to provide ratings or feedback.

Innovation Solution

A feedback manager system that tracks user interactions to determine familiarity and satisfaction levels, prompting users to rate or provide feedback through notifications and forms, thereby increasing meaningful user feedback for developers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If users are not prompted for feedback, then the application has simpler operation and fewer interruptions, but valuable user feedback is lost and cannot be collected

Engineering Contradiction:
Improveuser feedbackVSAvoiduser interaction
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system performs preliminary actions by tracking user interactions and determining familiarity levels before prompting for feedback. This ensures feedback is requested at the optimal moment when users are most likely to provide meaningful input, rather than randomly interrupting usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism that monitors user interactions, determines when feedback is needed based on familiarity thresholds, and prompts users accordingly. This creates a closed-loop system that adapts to user behavior and requests feedback at appropriate moments.

Inventive Principle:
Principle #23Feedback

2Loss of information

If feedback is requested immediately after installation, then user feedback can be collected quickly, but users who are not familiar with the application may not provide meaningful feedback

Engineering Contradiction:
Improveuser feedback timingVSAvoidfeedback relevance
Core Design Contradiction:
Loss of informationVSMeasurement precision

Solution Approach 1:

The system performs preliminary tracking of user interactions and determination of familiarity levels before requesting feedback. This preliminary action ensures that feedback is only requested when the user has demonstrated sufficient familiarity with the application, ensuring both timely collection and relevance of feedback.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the parameter of feedback request timing based on the detected user familiarity level. By adjusting when feedback is requested according to the user's interaction history and familiarity threshold, the system optimizes both timing and relevance of feedback collection.

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If the system continuously monitors user interactions to determine feedback timing, then feedback can be requested at optimal moments, but the system complexity increases

Engineering Contradiction:
Improvefeedback collection accuracyVSAvoidfeedback management system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system segments the feedback management into distinct components: interaction tracking, familiarity determination, and feedback prompting. This segmentation allows each component to perform its specific function independently, making the overall system more manageable and maintainable while achieving accurate feedback collection.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10365798B1Feedback manager for integration with an application
Publication Date: 2019.07.30 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10365798B1 patent drawing
  • US10365798B1 patent drawing
  • US10365798B1 patent drawing

AI summary

The disclosed embodiments provide a method, apparatus, and system for obtaining user ratings and/or feedback for a software application. During operation, the system tracks one or more interactions between a user and the application, wherein the application is configured to execute on an electronic device. While tracking the interactions, the system determines whether the interactions meet or exceed a familiarity threshold, wherein meeting or exceeding the familiarity threshold indicates that the user would be more likely than not to provide an informed rating for the application. Next, if the one or more interactions meet or exceed the familiarity threshold, the system displays a message that asks the user whether the user likes the application. If the user likes the application, the system assists the user in rating the application. Otherwise, the system assists the user in providing feedback for the application.