Remote Client Interface Segmentation for Small Screen Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face difficulties interacting with remote applications designed for desktop environments on client devices with small screens, as rewriting applications for native functionality and user interface on client devices is resource-intensive and impractical.
Innovation Solution
A system that renders a composite view on the client device, combining a local graphical user interface (GUI) for controlling a remote application with the remote application view, allowing user inputs to be translated into command messages sent to the server for remote application control, optimizing the user experience without requiring extensive rewriting of applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If a remote application designed for desktop environment is accessed from a client device with small screen, then the application can run on powerful server resources, but the user interaction becomes very difficult due to screen size limitations
Solution Approach 1:
The interface is segmented into two distinct parts: a local GUI component rendered on the client device for easy interaction, and a remote application view component showing the actual application output. This segmentation allows each component to serve its specific function optimally - the local GUI provides touch-friendly controls while the remote view displays the application content.
Solution Approach 2:
A local GUI acts as an intermediary between the user and the remote application. Instead of directly interacting with the remote application's desktop interface, users interact with the local GUI which then translates user inputs into commands for the remote application, bridging the gap between mobile interaction patterns and desktop application functionality.
2Ease of operation
If the application is rewritten to run natively on the client device, then the user interface can be optimized for small screens, but the development time and resources required become prohibitively large
Solution Approach 1:
Instead of rewriting the application code for native client execution, the system creates a copy of the application interface locally. The local GUI replicates the essential control elements and interaction patterns needed for mobile devices, while the actual application logic continues to run on the server, avoiding the time-consuming process of complete application porting.
Solution Approach 2:
The system creates a universal architecture that can work with any remote application regardless of its original platform. The local GUI framework provides a standardized interface layer that adapts to different remote applications, making the solution broadly applicable without requiring application-specific development for each case.
3Adaptability or versatility
If the application is rewritten for client device, then native functionality can be achieved, but the complexity and cost of the undertaking increase significantly
Solution Approach 1:
The local GUI serves as an intermediary layer that provides native-like functionality without requiring native application rewriting. It translates mobile interaction patterns into remote application commands, achieving adaptability to client devices while keeping the application logic on the server, thereby reducing complexity.
Solution Approach 2:
Instead of moving the application to the client device (traditional approach), the system inverts the architecture by bringing a simplified interface copy to the client while keeping the full application on the server. This reversal achieves native interaction capabilities without the complexity of full application porting.
Data Source
Figure 1A
Figure 1B
Figure 1C~1E
AI summary
Examples of systems and methods are provided for communicating events at a server to a remote client device. A system may allow communication and may provide, to a remote client device, a message related to an event at a server. The system may comprise an agent module configured to receive notification of the event at the server, configured to determine an action, based on the event, to be performed by the remote client device on a graphical user interface (GUI) at the remote client device or a remote view at the remote client device, configured to generate the message based on the determined action, and configured to direct the message to the remote client device. The GUI may be a GUI for controlling an application running on the server from the remote client device, and the remote view may be a view of the application running on the server.