Server-Side Mobile A/B Testing Without App Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional A/B testing on mobile applications is hindered by the long 'tail' of mobile application version upgrade cycles, leading to increased resource expenditure and delayed testing due to users not updating their applications, which complicates the implementation of new test variations.

Innovation Solution

An experimentation system dynamically controls A/B testing on mobile devices by selecting test variations server-side, allowing mobile applications to execute different experiences without requiring re-compilation or version updates, using a server-based system to manage and deliver user interface configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional A/B testing is performed on mobile applications, then test results can be obtained, but the long upgrade cycle delays testing and increases resource expenditure

Engineering Contradiction:
Improvetesting efficiencyVSAvoidupgrade cycle time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent extracts the test variation logic from the mobile application binary and places it on the server side. The mobile application contains only a framework to receive and execute server-generated test variations, eliminating the need to recompile or update the application for each test variation. This allows rapid A/B testing without being constrained by application update cycles.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent moves the test variation dimension from the application code level to the server configuration level. Instead of creating different application versions for different test variations, the system generates different test variations dynamically on the server and delivers them to the same application framework, adding a new dimension of flexibility to the testing process.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If mobile application version updates are required for each test variation, then testing can be performed, but resource costs increase and iteration speed decreases

Engineering Contradiction:
Improvetest variation flexibilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent creates a universal mobile application framework that can execute any test variation generated by the server. The application contains a generic test execution engine that adapts to different test variations without requiring modification, allowing the same application binary to serve multiple testing purposes across different experiments and variations.

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

3Stability of the object's composition

If users do not update their mobile applications, then current versions are maintained, but A/B testing cannot be implemented or is delayed

Engineering Contradiction:
Improveapplication version stabilityVSAvoidtesting implementation speed
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent introduces a server as an intermediary between the test variation definition and the mobile application execution. The server generates test variations in a standardized format and delivers them to applications that already have the execution framework installed. This intermediary layer decouples the testing implementation from application updates, allowing testing to proceed even when users have not updated their applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250225063A1A/b testing for mobile applications
Publication Date: 2025.07.10 EBAY INC
  • US20250225063A1 patent drawing
  • US20250225063A1 patent drawing
  • US20250225063A1 patent drawing

AI summary

A machine may be configured to perform A/B testing on mobile applications. For example, the machine receives an identifier of a user from a mobile device that requests a layout description of a user interface, determines the layout description that provides a configuration of one or more elements of the user interface according to an experiment variant associated with an experiment, and causes display of the one or more elements of the user interface on the mobile device based on the layout description.