Capturing native application content rendering performance
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.
1. A method for automatically capturing user-perceived content rendering performance by a native application on a user device, the method comprising:
rendering a first content element in a display device at a start time;
repeatedly rendering subsequent content elements and converting the display device content into a succession of video frames;
detecting when the display device content stabilizes at a stop time after which a predetermined time span elapses without further content changes; and
outputting performance data comprising a rendering duration comprising the stop time minus the start time,
wherein a clock in the user device provides the start time and the stop time.
2. The method of claim 1 , wherein the native application enables use of a networked publication and ecommerce system.
3. The method of claim 1 , wherein the user device is a mobile device comprising at least one of a smart phone, a laptop computer, and a tablet.
4. The method of claim 1 , wherein the content element comprises at least one of a text field and an image.
5. The method of claim 1 , wherein the start time is based on when successive video frame grayscale content stabilizes.
6. The method of claim 1 , wherein the stop time is estimated from one of: when all maximum resolution images are rendered, when a model estimates all content will be rendered, and when a subsequent unrelated script begins.
7. The method of claim 1 , further comprising assigning the rendering duration to one of a predetermined error value and a negative value, if rendering progress is incomplete and comes to a halt.
8. The method of claim 1 , further comprising outputting at least one of a timestamp indicating when the content was rendered, and technical information describing the user device.
9. The method of claim 1 , further comprising storing and visually displaying the performance data, and detecting performance anomalies.
10. The method of claim 9 , further comprising notifying at least one of an application developer and a content designer of the performance anomalies.
11. A non-transitory computer-readable storage medium having embedded therein a set of instructions which, when executed by one or more processors of a computer, causes the computer to execute the following operations for automatically capturing user-perceived content rendering performance by a native application on a user device:
rendering a first content element in a display device at a start time;
repeatedly rendering subsequent content elements and converting the display device content into a succession of video frames;
detecting when the display device content stabilizes at a stop time after which a predetermined time span elapses without further content changes; and
outputting performance data comprising a rendering duration comprising the stop time minus the start time,
wherein a clock in the user device provides the start time and the stop time.
12. The medium of claim 11 , wherein the user device is a mobile device comprising at least one of a smart phone, a laptop computer, and a tablet.
13. The medium of claim 11 , wherein the content element comprises at least one of a text field and an image.
14. The medium of claim 11 , wherein the start time is based on when successive video frame grayscale content stabilizes.
15. The medium of claim 11 , wherein the stop time is estimated from one of: when all maximum resolution images are rendered, when a model estimates all content will be rendered, and when a subsequent unrelated script begins.
16. The medium of claim 11 , further comprising instructions causing assigning the rendering duration to one of a predetermined error value and a negative value, if rendering progress is incomplete and comes to a halt.
17. The medium of claim 11 , further comprising instructions causing outputting of at least one of a timestamp indicating when the content was rendered, and technical information describing the user device.
18. The medium of claim 11 , further comprising instructions causing storing and visually displaying of the performance data, and detecting of performance anomalies.
19. The medium of claim 18 , further comprising instructions causing notifying of at least one of an application developer and a content designer of the performance anomalies.
20. A system for automatically capturing user-perceived content rendering performance by a native application on a user device, the system comprising:
a processor and a memory that operate to:
render a first content element in a display device at a start time;
repeatedly render subsequent content elements and convert the display device content into a succession of video frames;
detect when the display device content stabilizes at a stop time after which a predetermined time span elapses without further content changes; and
output performance data comprising a rendering duration comprising the stop time minus the start time, wherein a clock in the user device provides the start time and the stop time.