Deep-Linking Mechanism for Seamless App Launch from Web Content

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies face challenges in directly promoting mobile applications by linking them to relevant content items on web pages, making it difficult for advertisers to drive user interest and sales through deep-linking, as users are primarily interested in products rather than applications.

Innovation Solution

A method that involves receiving a content item with data elements identifying an application and a product, displaying it, and upon user selection, automatically checking if the application is installed, transmitting a request to install it, and launching the application with product-related content, facilitating deep-linking and purchase transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users are directed to landing pages with additional information on web pages, then users can access product information, but the user experience is fragmented and conversion rates are lower

Engineering Contradiction:
Improveuser experienceVSAvoidconversion time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent introduces a deep-linking mechanism that acts as an intermediary between web page content items and mobile applications. When a user selects a content item, the system checks if the associated application is installed and launches it directly with the product data element, or directs to an application store if not installed. This mediator approach eliminates the fragmentation of viewing content on web pages and then navigating to separate landing pages, providing a seamless user experience while reducing conversion time.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If advertisers create content items that link to web pages, then product information can be provided, but direct promotion of mobile applications is difficult

Engineering Contradiction:
Improvepromotion capabilityVSAvoidapplication install rate
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent makes content items universal by enabling them to serve dual purposes: providing product information and directly promoting mobile applications. Each content item is associated with both a product data element and an application identifier. When a user selects the content item, the system checks for application installation and launches it directly, or directs to the application store. This multi-functional approach allows advertisers to promote both products and applications through a single content item, increasing versatility and productivity simultaneously.

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

3Ease of operation

If the system checks whether an application is installed and launches it automatically, then user convenience is improved, but system complexity increases

Engineering Contradiction:
Improveapplication launch processVSAvoidsystem processing logic
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a self-service mechanism where the user device automatically checks whether the associated application is installed and launches it without requiring additional user actions. The system retrieves the application identifier from the content item, checks installation status, and either launches the application directly or directs the user to the application store. This automation improves ease of operation by eliminating manual steps while the complexity is managed through standardized system APIs and protocols.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9355186B2Launching applications from webpages
Publication Date: 2016.05.31 GOOGLE LLC
  • US9355186B2 patent drawing
  • US9355186B2 patent drawing
  • US9355186B2 patent drawing

AI summary

This specification describes technologies relating to launching applications from content items in webpages. In general, one aspect of the subject matter described in this specification can be embodied in methods that include receiving a content item including a first data element that identifies an application and a second data element that identifies a product. The methods may further include displaying the content item, receiving a user selection of the content item, and, in response, automatically checking if the application is installed on a user device. The methods may further include transmitting a request, including the first data element, to a server and installing the application identified by the first data element on the user device. The methods may further include launching the application with the second data element as an input so that the first content displayed by the application relates to the product.