Mobile App Content Delivery Optimization via Interaction Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile applications often deter users with intrusive third-party content, leading to lower adoption rates and user experience issues due to resource bottlenecks caused by static and unoptimized display of revenue-generating content.

Innovation Solution

Analyzing user interaction data to determine optimal display factors for third-party content, such as timing, size, and orientation, allowing for customized and non-obtrusive presentation within mobile applications, which can be processed locally or remotely, and stored for later retrieval to avoid system slowdowns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If third-party content is displayed immediately upon application launch, then revenue generation begins earlier, but user experience deteriorates due to intrusive content blocking valuable screen real estate

Engineering Contradiction:
Improverevenue generation timingVSAvoiduser experience
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by collecting and analyzing user interaction data during the initial application usage phase before third-party content is displayed. This allows the application to understand user behavior patterns and preferences in advance, enabling optimized content delivery that begins at the right moment rather than immediately, thus balancing revenue generation with user experience.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts third-party content delivery based on real-time analysis of user interaction data. Instead of static immediate display or delayed display, the system adapts content timing, position, and configuration based on observed user behavior, allowing the content delivery strategy to evolve with user interactions while maintaining optimal user experience and revenue generation.

Inventive Principle:
Principle #15Dynamics

2Productivity

If third-party content is displayed in prominent positions to maximize visibility, then revenue generation improves, but user experience worsens due to obstructed application functionality

Engineering Contradiction:
Improverevenue generationVSAvoidscreen real estate consumption
Core Design Contradiction:
ProductivityVSObject-generated harmful factors

Solution Approach 1:

The system applies local quality by analyzing user interaction patterns to identify specific regions or contexts within the application where third-party content can be displayed without obstructing core functionality. Content is positioned in locations that are less critical for user tasks, allowing revenue generation while preserving user experience by avoiding obstruction of valuable screen real estate needed for application operations.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system enables self-service by allowing the application to automatically analyze its own user interaction data and autonomously determine optimal content positioning. The application monitors user behavior, identifies non-critical display areas, and automatically configures third-party content placement, eliminating the need for manual optimization while balancing revenue and user experience.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If user interaction data is processed locally in real-time to optimize content delivery, then user experience improves through personalized content, but system resources deteriorate due to processing bottlenecks

Engineering Contradiction:
Improvecontent personalizationVSAvoidsystem resource utilization
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system extracts the computationally intensive data processing function from the mobile application by implementing a hybrid architecture where user interaction data is collected locally but processed remotely on server infrastructure. This separates the lightweight data collection function (remaining in the application) from the heavy analysis function (moved to the server), reducing device complexity while maintaining content personalization capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces an intermediary processing layer that acts as a mediator between the mobile application and final content delivery decisions. This intermediary handles the complex data analysis and optimization calculations, allowing the application to maintain simple resource usage while still achieving personalized content delivery through the intermediary's processing capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If third-party content SDKs are integrated into application code to enable revenue generation, then developer income improves, but user experience worsens due to intrusive content display

Engineering Contradiction:
Improvedeveloper revenueVSAvoiduser adoption rate
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system applies parameter changes by dynamically adjusting multiple content delivery parameters including timing, position, configuration, and selection based on user interaction data analysis. Instead of fixed intrusive content display, the system modifies these parameters in real-time based on user behavior, enabling revenue generation through optimized content delivery that adapts to user preferences and maintains better user experience.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10863324B2Mobile content delivery optimization
Publication Date: 2020.12.08 YAHOO AD TECH LLC
  • US10863324B2 patent drawing
  • US10863324B2 patent drawing
  • US10863324B2 patent drawing

AI summary

Systems and methods provide for optimizing content delivery in mobile applications. A mobile application executing on a mobile computing device can obtain application interaction data that corresponds to user inputs and sensor data detected by the mobile computing device during execution times of the mobile application. The mobile computing device can send the interaction data to a remote server device that is configured to analyze the data and determine one or more optimal content display factors that are based on identified usage characteristics of the mobile application. The remote server device can then send the determined optimal content display factors back to the mobile computing device, where the timing, sizing, positioning, orientation, and other configurations of third-party content displays are influenced based on this information.