Partial Application Data Collection via Blur Counter Timer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application systems face high abandonment rates due to length, complexity, connectivity issues, and design flaws, resulting in lost user data when users partially complete forms without completing the entire process.

Innovation Solution

A method and system for capturing application data in near-real time as users fill out form fields, storing it on a device hosting the application, allowing for pre-screening and pre-approval processes even if users do not complete the form, by using a session ID and a blur counter timer to collect data after a field is no longer in focus.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the application form is made comprehensive to collect all necessary user information, then the data completeness is improved, but the application length and complexity increase leading to higher abandonment rates

Engineering Contradiction:
Improveuser data completenessVSAvoidapplication complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system performs preliminary data capture by storing user inputs in near-real-time as they are entered into form fields, using a blur counter timer to trigger storage when users move away from a field. This preliminary action ensures data is saved before the user potentially abandons the application, allowing for later follow-up without requiring users to complete the entire form.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The application data collection is segmented into individual form field events, with each field's data captured and stored independently when the user interacts with it. This segmentation allows the system to collect usable data incrementally rather than requiring complete form submission, reducing the perceived complexity while maintaining data completeness.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If the application form is shortened to reduce abandonment rates, then the ease of operation is improved, but the data completeness deteriorates

Engineering Contradiction:
Improveapplication completion easeVSAvoiduser data completeness
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system captures and stores user data in near-real-time as they type or fill in form fields, using a blur counter timer to trigger storage when users move away from a field. This preliminary action ensures data is preserved even if users abandon the application early, allowing the form to be shorter while maintaining data completeness through incremental capture.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If the system waits for complete form submission to collect data, then the data accuracy is improved, but the response time and user engagement opportunity are lost due to abandonment

Engineering Contradiction:
Improvedata accuracyVSAvoidapplication processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary data capture and storage in near-real-time using a blur counter timer that triggers when users move away from form fields. This preliminary action captures data incrementally throughout the application process, allowing the system to have usable data ready for follow-up even if the user abandons the application, eliminating the need to wait for complete submission.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback by storing and preserving user inputs as they are entered, creating a record that can be used for later follow-up. This feedback mechanism ensures that partial completions are not lost, allowing the system to maintain data accuracy through incremental capture and enable timely follow-up actions.

Inventive Principle:
Principle #23Feedback

4Reliability

If the application requires full completion before processing, then the data reliability is improved, but the productivity and user engagement are reduced due to high abandonment rates

Engineering Contradiction:
Improveapplication data reliabilityVSAvoidapplication processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary data capture and storage in near-real-time using a blur counter timer that triggers when users move away from form fields. This preliminary action ensures data is saved incrementally, allowing the system to process and follow up on partial completions, thereby improving productivity without sacrificing data reliability through the use of session IDs and structured storage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The data collection process is segmented into individual field events, with each field's data captured and stored independently. This segmentation allows the system to accumulate reliable data incrementally rather than requiring complete form submission, improving processing efficiency while maintaining data reliability through systematic capture of user inputs.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11769000B2Method and system for partial application data collection
Publication Date: 2023.09.26 BREAD FINANCIAL PAYMENTS INC
  • US11769000B2 patent drawing
  • US11769000B2 patent drawing
  • US11769000B2 patent drawing

AI summary

Methods and systems for partial application data collection are disclosed. The method stores a network accessible application having a plurality of form fields. One or more processors generate a session identifier (ID) and timestamp for a user accessing the application. The one or more processors determine that a state within a form field of one of the plurality of form fields is in focus, the state of the form field being in focus when the user selects the form field. Additionally, it is determined when the state within the form field is no longer in focus. At that time, a countdown timer is initiated. When the countdown time reaches zero, any data entered into the form field is collected. The collected data and the session ID are then combined into a single user data file.