Mobile App View Mapping for Dynamic Content Insertion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile application developers face challenges in efficiently inserting and managing third-party content, such as ads, within their applications without requiring frequent updates, as existing methods often necessitate specific code integration and manual handling.

Innovation Solution

A system and method that involve processors to map and identify elements within a mobile application, determine view categories, and generate content insertion policies based on user interactions, allowing for automatic insertion of third-party content without requiring new app versions, by analyzing actions and transitions within the app.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual code integration and specific code integration methods are used to insert third-party content, then content insertion can be achieved, but frequent app updates and manual handling are required

Engineering Contradiction:
Improvecontent insertion automationVSAvoidcode integration complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent introduces a content slot as an intermediary element that serves as a placeholder for third-party content. This content slot is integrated into the app's view hierarchy and can be automatically populated with third-party content items without requiring manual code integration for each content insertion, thereby automating the process while maintaining app structure integrity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the app interface by introducing dedicated content slots that are separate from the primary content views. This segmentation allows third-party content to be inserted into specific designated areas without affecting the overall app structure, enabling automated content management while reducing integration complexity

Inventive Principle:
Principle #1Segmentation

2Productivity

If third-party content is inserted into mobile applications, then revenue opportunities and user engagement improve, but app stability and performance may deteriorate

Engineering Contradiction:
Improveuser engagement and revenueVSAvoidapp stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent establishes content slots as pre-defined placeholders during app development, before third-party content is actually inserted. This preliminary structuring ensures that content insertion points are predetermined and do not disrupt app stability, while still enabling dynamic content loading to improve user engagement and revenue opportunities

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies different qualities to different parts of the app by introducing content slots with specific properties that differ from primary content views. These content slots have dedicated characteristics for handling third-party content, allowing the app to maintain overall stability while enabling enhanced productivity through targeted content insertion in specific locations

Inventive Principle:
Principle #3Local quality

3Loss of time

If manual handling and frequent updates are used to manage third-party content, then content freshness can be maintained, but development time and resources increase

Engineering Contradiction:
Improvecontent update timeVSAvoidapp maintenance effort
Core Design Contradiction:
Loss of timeVSEase of manufacture

Solution Approach 1:

The patent implements a system where content slots automatically retrieve and display third-party content items without requiring manual intervention for each content update. The content slots self-manage the insertion process by communicating with third-party content providers, thereby reducing development time and maintenance effort while keeping content fresh and up-to-date

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10120839B2Methods and systems for identifying elements of a mobile application
Publication Date: 2018.11.06 GOOGLE LLC
  • US10120839B2 patent drawing
  • US10120839B2 patent drawing
  • US10120839B2 patent drawing

AI summary

Systems and methods for identifying elements of a mobile application are described. One or more processors can receive a request to identify elements of a mobile application. The processors can map a plurality of views included in the mobile application and associated transitions between the plurality of views. For each of the plurality of views, the processors can determine a category of the view. The processors can then store, for the mobile application, a data structure identifying each of the plurality of views, and for each of the plurality of views, the category of the view, and one more transitions to others of the plurality of views for use in responding to a request for content from the mobile application.