Touch Interface Translation for Legacy Mobile Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy software applications designed for non-touch enabled displays on mobile devices require inefficient input methods, such as pressing numeric keys multiple times for typing, due to the difference in user experience between non-touch and touch-enabled interfaces.
Innovation Solution
A UI/UX enhancement system that generates a touch interface from a non-touch interface, translating touchscreen inputs into commands for non-touchscreen enabled applications, allowing users to interact with legacy applications on touchscreen devices without the need for new UI or command interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a non-touchscreen enabled application is used on a touchscreen device, then the application can run on legacy software, but the user experience deteriorates due to inefficient input methods requiring multiple key presses
Solution Approach 1:
A translation layer is introduced between the touchscreen interface and the non-touchscreen application. This intermediary component captures touchscreen gestures (taps, swipes, pinches) and translates them into simulated keypad inputs that the legacy application can process, thereby maintaining application compatibility while improving user input efficiency
Solution Approach 2:
The system creates a universal interface layer that can handle both traditional touchscreen gestures and legacy keypad input protocols. This multi-functional approach allows the same application to operate efficiently whether the underlying input mechanism is a physical keypad or a touchscreen, eliminating the need for separate input methods
2Ease of operation
If a new touch interface is developed for legacy applications, then user experience improves, but development overhead and complexity increase
Solution Approach 1:
Instead of creating entirely new touch interfaces for legacy applications, the system creates a virtual copy of the original keypad interface that runs on top of the touchscreen. This copied interface replicates the familiar keypad layout and behavior, providing users with a familiar interaction model without requiring developers to redesign the entire application interface
Solution Approach 2:
The interface system is segmented into distinct layers: the original application layer remains unchanged, while a new translation layer is added above it. This segmentation allows the legacy application to continue functioning as-is while the new layer handles all touchscreen interaction complexities, thereby reducing development overhead for individual applications
Data Source
AI summary
Systems and devices for providing a non-touchscreen enabled application through a touchscreen. One embodiment provides a touchscreen and an electronic processor communicably coupled to the touchscreen. The electronic processor configured to generate a touch interface comprising a representation of a non-touch interface provided by a non-touchscreen enabled application, provide the touch interface to the touchscreen, receive a command from the touchscreen corresponding to an interaction with the representation of the non-touch interface, translate the command into at least one event for updating a state of the non-touchscreen enabled application, and provide the at least one event to the non-touchscreen enabled application.