Tag-Based User Input Detection in Mobile Applications

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users face difficulties interacting with applications on mobile devices due to differences in input environments compared to traditional devices, leading to reduced functionality and potential bugs when modifying application code to detect user inputs.

Innovation Solution

Embedding code within an application to detect user inputs and send associated data to either the same or another application, using tags and hierarchies to identify selected objects without modifying the existing code, allowing navigation back to the selected object.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If application code is modified to detect user inputs on mobile devices, then user input detection capability is improved, but development time and resource costs increase

Engineering Contradiction:

Improveuser input detection capabilityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system uses the existing application's own code structure and data models to detect user inputs, rather than requiring external modification or additional detection mechanisms. The application serves itself by leveraging its embedded code to identify user selections through tag-based object identification.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The embedded code within the application serves multiple functions: it maintains the application's core functionality while simultaneously enabling user input detection and object selection identification. This multi-functional approach allows a single code base to handle both original operations and input detection without requiring separate detection systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If application code is modified to detect user inputs on mobile devices, then user input detection capability is improved, but resource costs increase

Engineering Contradiction:

Improveuser input detection capabilityVSAvoidresource costs

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The application leverages its own existing code and data structures to perform input detection, eliminating the need for external detection tools or additional resource investment. The system uses its embedded code to identify user inputs through tag-based object recognition.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system uses tags that replicate the structure and identification methods already present in the application's data models. By copying existing data structure patterns into tag-based identifiers, the system enables input detection without requiring new resource-intensive detection mechanisms.

Inventive Principle:

Principle #26Copying

3Loss of time

If code embedding is used to detect user inputs, then development time is reduced, but code complexity increases

Engineering Contradiction:

Improvedevelopment timeVSAvoidcode complexity

Core Design Contradiction:

Loss of timeVSDevice complexity

Solution Approach 1:

The input detection functionality is extracted as a separate process that operates on top of the existing application code. Rather than embedding complex detection logic throughout the codebase, the system extracts user input detection as a distinct function that processes tag-based identifiers generated by the application's normal operations.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Tags serve as intermediary elements between the application's data structures and the user input detection mechanism. These tags translate user selections into identifiable objects without requiring direct modification of the application's core code, thereby reducing code complexity while enabling input detection.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If traditional input detection methods are used on mobile devices, then input detection works on traditional devices, but user interaction difficulty increases on mobile devices

Engineering Contradiction:

Improveinput detection reliabilityVSAvoiduser interaction ease

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system changes the detection parameter from traditional coordinate-based or event-based input detection to tag-based object identification. By using tags that are embedded in the application's data structures, the system adapts to mobile touch interactions while maintaining reliable object identification through tag matching rather than traditional input methods.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The tag-based detection system provides universal input detection that works across different device types and input modalities. The same tag-based mechanism handles both traditional device inputs and mobile touch inputs, enabling reliable object identification while accommodating the ease of mobile interaction patterns.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10613915B2Identification of user input within an application

Publication Date: 2020.04.07 LENOVO SWITZERLAND INTERNATIONAL GMBH

AI summary

One embodiment provides a method, comprising: embedding, using a processor, code within an application; detecting, at an electronic device, a user input within the application, wherein the user input selects an object within the application; receiving, using a processor, data associated with the selected object; and sending, using a processor, data associated with the selected object to an application selected from the group consisting of the application and another application. Other aspects are described and claimed.