Adaptive User Interface Mode Switching for Touch and Hardware Input

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing devices face challenges in seamlessly transitioning between touch input and hardware-based input modes, leading to suboptimal user interface element configurations and user interactions.

Innovation Solution

A UI manager system that automatically or manually switches between touch input and hardware-based input modes, optimizing user interface elements accordingly, based on device docking status, input type, and user settings, using a system-on-a-chip architecture to integrate input detection and mode switching logic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the computing device uses a fixed user interface configuration optimized for hardware-based input, then hardware-based input interactions function properly, but touch input interactions are suboptimal and challenging

Engineering Contradiction:
Improvetouch input interactionVSAvoidhardware-based input interaction
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The user interface configuration dynamically changes based on the detected input mode. The system monitors input device status and automatically adjusts UI element properties (size, spacing, layout) to optimize for either touch input or hardware-based input, ensuring both interaction types function properly without manual reconfiguration

Inventive Principle:
Principle #15Dynamics

2Productivity

If the computing device automatically switches between touch input mode and hardware-based input mode, then user interaction efficiency is enhanced, but system complexity increases

Engineering Contradiction:
Improveuser interaction efficiencyVSAvoidmode switching system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system automatically detects the connected input device type and autonomously switches between touch input mode and hardware-based input mode without user intervention. The UI manager monitors device status changes and triggers appropriate mode transitions, reducing manual configuration complexity while maintaining high interaction efficiency

Inventive Principle:
Principle #25Self-service

3Ease of operation

If the user interface elements are optimized for touch input, then touch input usability improves, but hardware-based input interactions may not function properly

Engineering Contradiction:
Improvetouch input usabilityVSAvoidhardware-based input interaction
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system changes UI element parameters (size, spacing, layout configuration) based on the active input mode. When touch input mode is detected, UI elements are enlarged and spaced appropriately for finger interaction. When hardware-based input mode is active, the system reverts to the original UI configuration optimized for precision devices like mice and trackballs

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10430917B2Input mode recognition
Publication Date: 2019.10.01 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10430917B2 patent drawing
  • US10430917B2 patent drawing
  • US10430917B2 patent drawing

AI summary

A touch input mode may be entered and exited automatically and/or manually. When the touch input mode is entered, user interface (UI) elements are optimized for touch input. When the touch input mode is exited, the user interface (UI) elements are optimized for hardware based input. A user may enter the touch input mode by manually selecting a user interface element and/or by entering touch input. Settings may be configured that specify conditions upon which the touch input mode is entered/exited. For example, the touch input mode may be configured to be automatically entered upon undocking a computing device, receiving touch input when in the hardware based input mode, and the like. Similarly, the touch input mode may be configured to be automatically exited upon docking a computing device, receiving hardware based input when in the touch input mode, and the like.