Companion Window Architecture for Context Retention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face difficulties in seamlessly performing companion activities while maintaining an immersive full-screen experience across various applications, as there is no standardized way to interact with related tasks without switching away from the source application context.
Innovation Solution
The implementation of a companion window architecture that allows users to perform side tasks within a target application while retaining the visual context of the source application, providing a predictable and consistent experience across all applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the user switches to a target application to perform companion activities, then the user can complete related tasks, but the user loses the visual context of the source application
Solution Approach 1:
The display is segmented into multiple regions: a source application region and a companion window region. This allows the source application to maintain its visual context in one region while the companion activity occurs in another region, resolving the contradiction by spatially separating the two functions.
Solution Approach 2:
The companion window is nested within the source application experience, appearing as an overlay or embedded window. This nesting allows the companion activity to be performed while the source application remains visible in the background, maintaining visual context while enabling related tasks.
2Adaptability or versatility
If the user uses a standardized companion window architecture, then the user experience is consistent across applications, but the implementation complexity increases
Solution Approach 1:
The companion window architecture is designed as a universal system that can be applied across multiple applications and devices. By creating a standardized interface and behavior model that works consistently across different applications, the system achieves adaptability while managing complexity through reuse of the same architectural patterns.
3Loss of information
If the companion window is rendered proximate to the source application, then the user maintains visual context, but the source application's full-screen experience is reduced
Solution Approach 1:
The display is divided into different regions with different qualities: the source application occupies the majority of the screen in a full-screen-like region, while the companion window occupies a smaller, localized region. This local quality approach allows the source application to maintain its immersive experience while the companion window provides contextual support in a localized area.
Data Source
AI summary
Architecture that generates a companion window in combination with a source application experience to enable the accomplishment of a side task yet not switch away from the context of the source application. The companion window experience is a window that is rendered proximate (e.g., beside) a user's source application experience, in a predictable location, and with a predictable user model for invocation and dismissal. The companion window allows the user to retain full visual context of the associated source application experience, while rendering activities that directly pertain to the source application experience or activities that allow the user to interact with two applications.