Voice-Forward Mode Management for Seamless Task Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic devices face inconvenience in switching between touch-forward and voice-forward operation modes, often disrupting user experiences, especially when transitioning from touch-based to voice-based interactions, such as when a device is docked or used in different environments.

Innovation Solution

Implementing a system that manages device operation modes based on application settings and voice inputs, allowing seamless transitions between touch-forward and voice-forward modes without interrupting ongoing tasks, and automatically adjusting user interfaces to optimize interactions according to the user's context, such as docking or distance from the device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the device automatically switches operation modes based on docking status or environment, then the adaptability improves, but the user experience deteriorates due to interruptions in ongoing tasks

Engineering Contradiction:
Improveoperation mode adaptabilityVSAvoidtask continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary detection of the current active application and its state before executing a mode switch. It proactively identifies tasks that should be preserved and prepares to maintain them during the transition, preventing interruptions before they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The mode switching mechanism is made dynamic and context-aware. Instead of rigid automatic switching, the system adapts the switching behavior based on real-time task state, application type, and user interaction patterns, allowing flexible adjustment between adaptability and task continuity.

Inventive Principle:
Principle #15Dynamics

2Reliability

If the device requires manual password entry for security, then the security improves, but the ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidaccess convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system uses voice recognition technology to enable users to authenticate and access protected content through natural speech rather than manual password entry. The voice interface serves the user's need for convenient access while maintaining security through voice-based authentication mechanisms.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If the device switches to voice-forward mode when docked, then the adaptability improves, but the productivity deteriorates due to interruption of touch-based tasks

Engineering Contradiction:
Improvedocking mode adaptabilityVSAvoidtask completion efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

Before switching to voice-forward mode upon docking, the system preliminarily checks whether a touch-based task is actively being performed. If so, it delays or prevents the mode switch to avoid interrupting the user's workflow, thereby maintaining productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the switching parameter from a simple docking-status trigger to a composite parameter that includes task state, application type, and user behavior context. This allows the device to adapt to docking while considering the impact on ongoing tasks.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10885910B1Voice-forward graphical user interface mode management
Publication Date: 2021.01.05 AMAZON TECH INC
  • US10885910B1 patent drawing
  • US10885910B1 patent drawing
  • US10885910B1 patent drawing

AI summary

Systems, methods, and computer-readable media are disclosed for systems and methods for voice-forward graphical user interface mode management. Example methods include determining that a device is coupled to an accessory device, determining that being coupled to the accessory device causes the device to deactivate a first operating mode and activate a second operating mode, where the second operating mode has a lower content density than the first operating mode, and determining that an application setting of an application executing on the device is causing the device to remain in the first operating mode. Example methods may include determining that a new value is associated with the application setting, and causing the device to activate the second operating mode.