Multiplatform Experience Generation via Universal Definition Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mixed reality technologies face challenges in providing seamless interaction and synchronization across different platforms, such as personal computers and mixed reality devices, leading to varying user experiences and potential errors in communication and control of virtual objects.
Innovation Solution
A multiplatform based experience generation system that analyzes device capabilities and translates operations into a canonical format, allowing users on different platforms to interact with a common virtual environment through platform-specific actions, such as mouse clicks on PCs and gestures on mixed reality devices, while maintaining synchronization and reducing potential failure points.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If multiple platform-specific applications are developed separately for different devices, then each platform can have optimized user experience, but the system complexity and development time increase significantly
Solution Approach 1:
The patent implements a universal experience definition file that can be applied across multiple device platforms. This single file contains experience definitions that are platform-agnostic, allowing the same experience to be deployed on different devices (e.g., HoloLens, mobile phones, tablets) without creating separate platform-specific applications. The system achieves multi-functionality by making one experience definition file serve multiple platforms through adaptive rendering and input handling.
Solution Approach 2:
The patent introduces an intermediary layer consisting of the experience definition file and adaptive rendering system that sits between the core experience logic and platform-specific implementations. This intermediary translates high-level experience definitions into platform-specific renderings, eliminating the need for direct platform-specific development while maintaining optimized user experiences on each platform.
2Adaptability or versatility
If platform-specific implementations are created for different devices, then device capabilities can be fully utilized, but synchronization and communication between platforms become error-prone
Solution Approach 1:
By using a universal experience definition file that is platform-agnostic, the system ensures that the same experience logic is executed across all devices. This universality guarantees that experiences defined once will synchronize correctly across platforms without communication errors, as there is only one source of truth for the experience definition that all platforms adapt to their local capabilities.
Solution Approach 2:
The system applies local quality by allowing each platform to render the experience according to its specific capabilities (e.g., HoloLens renders in 3D spatial audio and visual context, while mobile phones render in 2D with touch controls). Each platform adapts the universal experience definition to its local characteristics, ensuring optimal utilization of device capabilities while maintaining synchronization through the common experience definition.
3Adaptability or versatility
If experiences are customized for each device platform, then hardware capabilities are maximized, but the number of failure points and potential errors increase
Solution Approach 1:
The experience definition file acts as an intermediary that contains the authoritative experience logic. This single source of truth is adapted by each platform rather than being replicated, reducing the number of failure points. Any errors in experience logic are centralized in one location rather than distributed across multiple platform-specific implementations, making the system more reliable while still optimizing for each hardware platform.
Solution Approach 2:
The system uses parameter changes to adapt the universal experience definition to different hardware platforms. Instead of creating different experience implementations, the system changes rendering parameters, input handling parameters, and display parameters based on the target platform's capabilities. This approach maintains a single experience logic while optimizing hardware utilization, reducing errors from multiple implementation versions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
According to examples, multiplatform based experience generation may include determining a set of connected devices that provide services related to virtual reality, and determining a platform type of each of the connected devices. Multiplatform based experience generation may further include receiving an indication of a modification to an intrinsic property of a virtual object on one of the set of connected devices, and generating, based on the received indication of the modification to the intrinsic property of the virtual object, a modification to a master version of the virtual object. Based on the platform type of another one of the set of connected devices and based on the modification to the master version of the virtual object, an indication of a modification to an intrinsic property of a virtual object on the another one of the set of connected devices may be generated.