Mobile App Recommendation Component Attribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile application recommendation systems fail to accurately attribute user recommendations to specific components of applications, leading to unclear intent and potential miscommunication of user preferences.

Innovation Solution

A method and system that generate a component reference table for each application, allowing users to select specific components they recommend through a user interface, and serve social annotations based on these selections to other users, ensuring accurate attribution of user recommendations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the system provides general application recommendations without component-level attribution, then the recommendation process is simple and fast, but the precision and clarity of user preferences are lost

Engineering Contradiction:
Improverecommendation attribution precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent segments the application into multiple identifiable components (e.g., features, functions, modules) and enables users to recommend specific components rather than the entire application. This segmentation allows the system to attribute recommendations precisely to individual components while maintaining a manageable structure through component reference tables that map component identifiers to their metadata.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces component reference tables as intermediary data structures that bridge the gap between simple application recommendations and detailed component-level attribution. These tables store component identifiers, names, and metadata, allowing the system to handle complex component information without requiring direct complex data structures in the recommendation flow itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If the system asks users to select specific components for recommendation, then the accuracy of preference communication improves, but the user interaction time and complexity increase

Engineering Contradiction:
Improveuser preference information accuracyVSAvoiduser interaction time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-defining application components, assigning them unique identifiers, and organizing them in component reference tables before the recommendation process begins. This preparation allows users to quickly select from pre-organized component lists during the recommendation interaction, rather than having to describe or categorize components in real-time, thus reducing interaction time while maintaining information accuracy.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If the system attributes recommendations to specific application components, then the relevance of recommendations to other users improves, but the data processing and storage requirements increase

Engineering Contradiction:
Improverecommendation relevanceVSAvoiddata volume
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent extracts essential component information (identifiers, names, and key metadata) into compact component reference tables, separating this reference data from the full application data. This extraction allows the system to work with minimal necessary data during recommendation processing while maintaining the ability to provide relevant, component-specific recommendations without storing or processing excessive information.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11087415B2Determining intent of a recommendation on a mobile application
Publication Date: 2021.08.10 GOOGLE LLC
  • US11087415B2 patent drawing
  • US11087415B2 patent drawing
  • US11087415B2 patent drawing

AI summary

Methods and systems are provided for determining the intent of a recommendation made by a user of a mobile application where the application includes a plurality of separable components, any one or more of which the recommendation can apply to. An application in which a user recommendation control is provided for presentation to a user also includes a tag indicating how a recommendation of the application should be interpreted with respect to the components included therein. The tag can be set by the application developer and can be in the form of text (e.g., a keyword or term) or a uniform resource locator (URL). Where a tag references multiple components of an application, a recommending user can be presented with a recommendation intent query. The recommendation intent query allows a user to designate one or more components of the application to which the user's recommendation should be attributed.