![]() Is it always kept in sync in the background? Does the page have to be manually refreshed by the user every now and then? Think of loading feedback mechanisms that are appropriate for the frequency and user involvement of the event. Something to factor in is how and when the data is fetched. Is data synchronized? Or do we need a refresh mechanism? You know your users and your content best. Keep typical user scenarios in mind when thinking about this. It might make more sense to extend the loading experience until you have, say, 12 items ready to show. Maybe it makes sense to bring the content up as it loads, one by one. How does the server return the info to the page?Īsk yourself what makes the most sense to return to your user. What’s the scope of the end result? A list of 3 cards requires a different reflection for the loading experience than a 10,000-item table that potentially involves pagination or a “Load More” button, etc. What is the range of objects that need to be loaded? You might want to consider breaking a long loading task into smaller chunks with different messaging or visuals. How much visibility do you have on the amount of time the task requires to complete? Can you estimate it accurately? Is it valuable to communicate that to the user? What’s the expectation for how long it should take to load?Ĭan we initiate different behaviours based on timing thresholds that we set? If it’s a critical task that, even if it’s easy for the system to manage, is a high-stake operation in the user’s context, then a full-page loading mechanism might bring a sense of security and trust for them.Ĭan we predict the timing of the content to load? If it’s something unobtrusive that doesn’t require user input, they would naturally expect this to be done quietly in the background. It’s important to ask yourself exactly how much space does this loading interaction deserve. You want to inform them that the request has been understood by the system before displaying an appropriate loading pattern to show progress.ĭo you need to block out the whole screen? In this case, immediate feedback is primordial. Or you might be creating a loading interaction that follows a user-initiated action like them submitting a form or requesting to export a large document. Here, you need to set expectations as users might not be familiar with the page that’s about to be displayed. You might be dealing with an upfront loading situation, for example when the user first loads a page and expects to see existing content show up. These prompts should help you think about how you want to apply loading best practices to your specific scenario. Things to consider when designing loading feedbackįollow these prompts along with your team as you embark on tackling loading UX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |