Input Interface Selection for Data Type Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data input mechanisms, such as those in HTML5, require users to perform complex operations to switch between input devices like virtual keyboards and address books, as they only display the user interface for the specified data type, lacking easy access to other relevant input applications.
Innovation Solution
An information processing apparatus with an inclusion relation memory, correspondence relation memory, data type identifying unit, and display controller that analyzes data types and corresponding software applications, allowing for the display and selection of multiple input software applications based on inclusion relations and correspondence tables, enabling seamless switching between input devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If only the user interface for the specified data type is displayed, then the interface simplicity is improved, but the ease of operation deteriorates because users cannot easily access other relevant input applications
Solution Approach 1:
The user interface is segmented into multiple selectable input device options. Instead of showing only one input device interface, the system divides the interface into separate selectable options (e.g., virtual keyboard, address book, camera) that users can choose from, allowing easy access to different input methods while maintaining interface organization.
Solution Approach 2:
The input interface is designed to support multiple functions and input device types within a single unified interface. The system provides a universal input interface that can switch between different input devices (keyboard, address book, camera, microphone) based on user selection, making the interface versatile for various data input needs without requiring separate applications.
2Ease of operation
If multiple input software applications are displayed and selectable, then the ease of operation is improved, but the device complexity increases
Solution Approach 1:
The user interface dynamically adapts its content based on the selected input device type. When a user selects a specific input device (e.g., address book), the interface automatically updates to show relevant options and controls for that device. This dynamic behavior allows multiple input applications to be accessible while maintaining a simple, context-appropriate interface at any given moment.
Solution Approach 2:
A selection interface acts as an intermediary between the user and multiple input software applications. Instead of directly presenting all input applications simultaneously, the system provides a mediation layer (selection screen) that allows users to choose which input device to use, thereby managing complexity while maintaining ease of access to multiple functions.
3Adaptability or versatility
If the system supports multiple data types and corresponding software applications, then the adaptability is improved, but the device complexity increases
Solution Approach 1:
The system performs preliminary analysis of the acquired information to identify the data type before presenting input options. By pre-identifying the data type (e.g., text, number, email, URL) and determining the corresponding suitable input software applications in advance, the system reduces the complexity of real-time decision-making and provides a streamlined user experience with pre-organized input options.
Solution Approach 2:
The system changes the parameter of interface presentation based on the identified data type. When different data types are detected, the system adjusts which software applications are displayed and how the interface is configured. This parameter-based adaptation allows the system to support multiple data types and applications while maintaining manageable complexity through context-sensitive interface variations.
Data Source
AI summary
An information processing apparatus includes an inclusion relation memory, a correspondence relation memory, a data type identifying unit, a software application identifying unit, and a display controller. The inclusion relation memory stores inclusion relation between multiple data types. The correspondence relation memory stores correspondence relation between the data types and software applications used in input of data. The data type identifying unit analyzes acquired information to identify a data type corresponding to an input area of the acquired information. The software application identifying unit identifies a software application corresponding to each data type included in the identified data type in accordance with the inclusion relation and the correspondence relation. The display controller displays a display part in which the identified software application is used in a display.