Messaging App AR Experience Integration via Shared Component State

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Messaging applications lack interoperability between components, leading to disjointed user experiences and inefficient resource usage due to the need for repeated operations across different components, such as AR experiences and web-based applications, which reduces user engagement.

Innovation Solution

A system that enables seamless data sharing and interaction across multiple components of a messaging application, allowing components like AR experiences and web-based applications to launch programmatically based on user interactions or goals, and synchronize states using a shared data structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If components are configured to be separately launched, then each component can function independently, but interoperability between components is lacking leading to disjointed user experiences

Engineering Contradiction:
Improvecomponent independenceVSAvoiduser experience continuity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a shared data structure as an intermediary that enables communication and state synchronization between separately launched components. This mediator allows AR experiences, web-based applications, and other components to share data and maintain consistent states without being tightly coupled, thus preserving component independence while enabling interoperability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If components operate independently, then system modularity is maintained, but resource usage becomes inefficient due to repeated operations across different components

Engineering Contradiction:
Improvesystem modularityVSAvoidresource utilization efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent merges the data storage and state management functionality across multiple independent components by implementing a shared data structure that is accessible by all components. This allows different components (AR experiences, web applications, etc.) to access and synchronize their states through this unified data structure, eliminating redundant operations and improving resource utilization while maintaining the modular architecture.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of manufacture

If components are separately launched, then each component can be independently developed and maintained, but user engagement reduces due to disjointed experiences and repeated operations

Engineering Contradiction:
Improvecomponent development independenceVSAvoiduser engagement
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The shared data structure serves as a universal interface that enables multiple components to interact and share states. This multi-functional mechanism allows independently developed components to work together seamlessly, providing a unified user experience that enhances user engagement while preserving the benefits of independent component development and maintenance.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250342669A1Integrating augmented reality experiences with other components
Publication Date: 2025.11.06 SNAP INC
  • US20250342669A1 patent drawing
  • US20250342669A1 patent drawing
  • US20250342669A1 patent drawing

AI summary

Methods and systems are disclosed for generating AR experiences. The methods and systems access a first component of a plurality of components implemented by the messaging application, the plurality of components comprising an AR experience, each of the plurality of components being configured to be separately launched by the messaging application. The methods and systems store a first state of the first component in a data structure that is shared across the plurality of components; launching. The methods and system launch, by the messaging application, a second component of the plurality of components in response to determining that an interaction has been performed using the first component; and configure a second state of the second component based on the interaction that has been performed using the first component.