Browse Prior Art Database

Method to adapt loading indication based on historical execution data Disclosure Number: IPCOM000243287D
Publication Date: 2015-Sep-18
Document File: 2 page(s) / 42K

Publishing Venue

The Prior Art Database


Method to adapt load animation behaviour in an evolving system

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 2

Method to adapt loading indication based on historical execution data

When transitioning between two panels in a Graphical User Interface (GUI or UI), it is sometimes desirable to add a loading animation, because it takes some time to transition and we want the user to know that something is happening.

    Equally, it can be annoying if a loading animation is inserted when the load is actually pretty fast, and the user only sees 0.5s of the animation.

We suggest the following new solution, which builds upon known solutions

acknowledged at the end of this publication.

    Provide a default "display or don't display" for loading animation on a UI transition. Set a threshold (which could be the amount of time that you were

considering coding as the "minimum loading time" to pad to), and then record each time the user initiates the transition whether it is above or below this threshold. Use this to decide the loading-animation-display behaviour for the transition.

    For example, if it's always below the threshold, don't display the loading animation. If it's always above, do display it. If it varies, display with threshold used as a minimum load padding, or look at the most recent results (as the changed load time could be a result of the system changing). This idea becomes particularly interesting if we consider an example where loading behaviour changes over time as a user adds to a system.

    Consider as an example a web UI for a product where Internet of Things (IoT) devices are connected to a central management hub. There may be UI panels that a user can switch between e.g. "Devices" and "API Keys". As an example…

1 User is on the Devices tab. They click on the API Keys tab - the transition takes 0.5s to load the new panel.

2 They go back to Devices - the load takes 0.5s.

3 They add 1000 Devices.

4 They click the API Keys tab - the load takes 0.5s.

5 They click Devices - this time there is a lot more data to load in: the transition takes 6s.

    Now, although both transitions were fast when the user first started, one of them has become slower. As the user continues...