Web View AR Launching Through a Messaging Client Bridge
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing messaging clients lack the ability to seamlessly integrate augmented reality (AR) components directly from web view applications, limiting user interaction and engagement with AR technology.
Innovation Solution
A web view AR system is developed to load AR components directly from web view applications, enabling users to access and interact with AR features through a camera view interface, utilizing a Software Development Kit (SDK) with APIs for deep linking and validation, and a bridge method to integrate AR components into the messaging client.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If AR components are integrated directly into web view applications, then user access and interaction capability is improved, but system complexity increases
Solution Approach 1:
The patent introduces a messaging client as an intermediary layer between web view applications and AR components. The messaging client provides a standardized interface that receives AR component identifiers from web views and retrieves the corresponding AR components from remote servers, eliminating the need for direct integration between web views and AR systems while simplifying the overall architecture.
Solution Approach 2:
The messaging client is designed as a universal platform that can handle multiple types of content including text, images, videos, and AR components through a single unified interface. This multi-functional approach allows web view applications to access AR components without requiring application-specific integration code, reducing system complexity while improving ease of operation.
2Adaptability or versatility
If AR components are loaded directly from web view applications, then functionality and interactivity are improved, but validation and security requirements increase complexity
Solution Approach 1:
The messaging client serves as a security intermediary that validates AR component identifiers before retrieving and executing the actual AR components. This centralized validation mechanism in the messaging client eliminates the need for complex validation logic within web view applications themselves, maintaining security while simplifying the overall system architecture.
3Adaptability or versatility
If deep linking support is added for AR components, then navigation and integration capability are improved, but system complexity increases
Solution Approach 1:
The messaging client implements a universal deep linking mechanism that handles various types of content links (text, images, videos, and AR components) through a single standardized processing pipeline. This universal approach allows AR component deep linking to work through the same infrastructure used for other content types, improving capability while avoiding the need for separate complex linking mechanisms.
Data Source
AI summary
A methodology is described that provides access to an augmented reality (AR) component maintained by a messaging server system directly from a web view application. When a user activates, from a web view application executing in the messaging client, a user selectable element that references an AR component, a web view AR system obtains the identification of the AR component, performs validation of the identification and of any additional launch data, and launches a camera view user interface (UI) with the AR component loaded in the camera view UI. Content captured from the camera view UI can be shared to other computing devices.