Intermediate Module for Webview to Scrollview Image Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Providing webview type content to a scrollview type interface in mobile applications leads to performance degradation, such as slowed frame rates, due to direct content insertion.

Innovation Solution

An intermediate module fetches and captures images from the webview module and provides them to the scrollview module, avoiding latency and performance issues by acting as an intermediary between the webview and scrollview modules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If webview content is directly inserted into scrollview interface, then content display functionality is achieved, but performance degradation occurs with slowed frame rates

Engineering Contradiction:
Improveframe rateVSAvoidcontent display stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces an intermediate module that captures screenshots from the webview and converts them into images for display in the scrollview. This intermediary layer isolates the webview rendering process from the scrollview update process, preventing direct content insertion performance issues while maintaining both content display functionality and smooth scrolling at 60 FPS.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If webview content is directly inserted into scrollview, then content integration is achieved, but latency effects increase

Engineering Contradiction:
ImprovelatencyVSAvoidcontent integration flexibility
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The patent uses screenshot capture to create a copy of the webview content as an image. This copying approach eliminates latency by converting dynamic webview rendering into static image frames that can be efficiently displayed and scrolled without real-time rendering delays, while still providing full content integration flexibility.

Inventive Principle:
Principle #26Copying

3Productivity

If webview content is directly inserted into scrollview, then functionality is achieved, but performance degradation occurs

Engineering Contradiction:
Improveframes per secondVSAvoidmodule integration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the content display system into distinct functional modules: a webview module for content rendering, a screenshot capture module for converting webview output to images, and a scrollview module for displaying the captured images. This segmentation allows each module to operate independently at optimal performance, achieving 60 FPS while managing complexity through clear module boundaries and responsibilities.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10220301B1Providing content to a scrollable user interface
Publication Date: 2019.03.05 ZYNGA INC
  • US10220301B1 patent drawing
  • US10220301B1 patent drawing
  • US10220301B1 patent drawing

AI summary

Systems and methods for displaying dynamically changing content within scrollview class applications are described. In some example embodiments, an intermediate module fetches images from an underlying layer of a webview module, and provides the images to a scrollview module, which presents the images via a scrollable user interface on a computing device, such as a scrollable user interface within a game application presenting an online game via a user interface of a mobile device.