Native App Rendering Performance Measurement via Video Frame Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users of networked publication and ecommerce systems face difficulties in finding items of interest due to slow content rendering times on client devices, which can be exacerbated by limited computational capabilities of mobile devices, leading to inaccurate manual measurements and reduced effective throughput.
Innovation Solution
An automated system measures user-perceived rendering performance by converting display device content into video frames, detecting key frames with no changes, and calculating rendering duration, allowing for real-time data collection and analysis across various devices, enabling application developers to identify performance issues and optimize content rendering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If manual timing methods are used to measure rendering performance, then measurement simplicity is maintained, but measurement precision deteriorates due to user reaction time delays
Solution Approach 1:
The patent replaces manual mechanical timing (user reaction time with stopwatch) with an automated electronic measurement system. The system uses software hooks and event listeners to automatically record start and end times of rendering operations, eliminating human reaction time delays and achieving precise millisecond-level measurements without increasing user-facing complexity
Solution Approach 2:
The patent introduces an intermediary measurement system that sits between the rendering process and the user. This system uses performance monitoring APIs and event-driven architecture to capture rendering start and end events automatically, serving as a mediator that provides accurate measurements without requiring direct user involvement in the timing process
2Adaptability or versatility
If content rendering is performed on mobile devices with limited computational capabilities, then device accessibility is improved, but rendering speed deteriorates
Solution Approach 1:
The patent implements progressive rendering where content is rendered in prioritized portions rather than waiting for complete rendering. Critical content elements are rendered first while less important elements follow, allowing users to perceive useful content sooner on resource-constrained mobile devices without requiring full rendering completion
Solution Approach 2:
The patent divides content rendering into separate renderable units or segments that can be processed independently. This segmentation allows the rendering system to prioritize and execute critical segments on mobile devices with limited computational resources, improving perceived rendering speed while maintaining overall content completeness
3Speed
If rendering performance measurement is implemented, then rendering speed improvement can be achieved, but system complexity increases
Solution Approach 1:
The patent implements self-service measurement where the rendering system automatically monitors and reports its own performance metrics without requiring external measurement tools. The system uses built-in performance APIs and event hooks to autonomously track rendering times, eliminating the need for separate complex measurement infrastructure while enabling continuous performance optimization
Data Source
AI summary
A system, method, and computer program product are provided for determining a duration of time required to render a web page or other content displayed by a native application running on a user device. One embodiment captures screenshots of the application's displayed output on a user device as video frames, and determines when the displayed output image content stabilizes. Another embodiment measures the number of service calls from a mobile client machine and the data requested and/or sent in response to such calls to determine native application performance. In another embodiment, a configuration file updates application executables and runs batch content rendering performance tests. Embodiments timestamp and store test results for subsequent visual depiction, evaluation, and analysis by developer teams and/or users. Performance variations due to changes to a native application or content may be routed to a particular application developer or content designer for possible correction and improvement.