Embedded Instant Applications for On-Demand Feature Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing applications require full downloads, consuming significant computing resources and often involve lengthy and inefficient processes for users to access specific functionalities, leading to waste of network and storage resources.

Innovation Solution

Instant applications, which are portions of full applications, are downloaded and executed on demand, leveraging interactable elements and machine learning to determine context-based surfacing, allowing quick access to discrete functionalities without full application installation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full applications are downloaded for security and authentication reasons, then application functionality and security are improved, but network resource consumption and storage requirements increase significantly

Engineering Contradiction:
Improveapplication securityVSAvoiddata consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments applications into modular components that can be downloaded and executed independently. Instead of requiring full application downloads, the system divides applications into smaller functional units that can be delivered on-demand, reducing network resource consumption while maintaining security through controlled access to segmented application parts.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts essential application functionalities from full applications and delivers only the necessary portions to user devices. This extraction approach allows the system to provide specific application features without requiring users to download complete applications, thereby reducing data consumption while maintaining the core functionality and security requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If full applications are downloaded, then complete application functionality is available, but access time and user efficiency deteriorate due to lengthy download processes

Engineering Contradiction:
Improveapplication functionalityVSAvoidaccess time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

By segmenting applications into smaller functional components, the system enables faster delivery and execution of specific application features. Users can access individual application parts immediately without waiting for complete application downloads, significantly reducing access time while maintaining the ability to provide full functionality through aggregated segments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-processing and preparing application segments for rapid deployment. Application components are prepared in advance in a condensed format that enables quick transmission and execution, allowing users to access application functionality almost immediately without lengthy download and installation processes.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If full applications are installed on devices, then all embedded functionalities are accessible, but device storage resources are consumed unnecessarily

Engineering Contradiction:
Improvefunctional accessibilityVSAvoidstorage space
Core Design Contradiction:
Ease of operationVSVolume of stationary object

Solution Approach 1:

The patent extracts only the necessary application components that are needed for specific functionalities and delivers them to user devices. This approach allows users to access required application features without storing complete applications, significantly reducing device storage requirements while maintaining ease of operation for accessible functionalities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements local quality by delivering application segments tailored to specific user needs and device contexts. Each user device receives only the application parts relevant to their specific usage scenarios, optimizing storage utilization while ensuring that accessible functionalities are fully operational for local operations.

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If traditional application delivery methods are used, then comprehensive application features are provided, but resource efficiency and user experience deteriorate due to waste of network and storage resources

Engineering Contradiction:
Improveapplication functionalityVSAvoidresource efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent applies segmentation to divide applications into deliverable units that can be transmitted and executed efficiently. This segmentation enables the system to provide comprehensive application functionality through selective delivery of only necessary segments, dramatically improving resource efficiency by eliminating transmission and storage of unnecessary application parts.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the delivery parameters from complete application packages to segmented, on-demand components. This parameter change optimizes network resource utilization by transmitting only essential data portions and improves storage efficiency by maintaining application segments in a condensed, space-efficient format that can be expanded during execution.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12548094B2Embedded applications
Publication Date: 2026.02.10 BLOCK INC
  • US12548094B2 patent drawing
  • US12548094B2 patent drawing
  • US12548094B2 patent drawing

AI summary

Embedding applications, or parts thereof, into other applications, or parts thereof, is described. In an example, an engagement with a first application associated with a merchant can be detected, which can cause the first application to add a user to a waitlist associated with a merchant location of the merchant, and a notification can be sent to a user computing device of the user. Detecting an interaction with an interactable element of the notification can trigger a second application associated with the merchant to be initialized in response to the engagement. In at least one example, the first application can provisionally transition to the second application, or a part thereof. Based at least in part on detecting a user interaction with the second application, and a menu can be presented via a user interface associated with the second application via the user computing device.