As usual, really enjoyed your breakdown of a simple but effective technique. In practice, the time it takes to load content on a new page is often variable, so having a predetermined time for a loading state may not be ideal. Have you encountered this and what would an engineer's solution be? Just a thought, having some colab with an engineer would be a great addition to your channel. Not suggesting you don't collaborate with devs but it's so often the missing component when planning motion for experiences. Hearing how they might build out this gallery loading example would be really interesting - to me at least.
Love this comment. You’re totally right, this example I shared is of an indeterminate loading time (meaning unknown length) vs determinate (known length) Which is why the loading animation is one that loops endlessly to cover any amount of time. When working on an experience like this it will be typical that you could pull some data to get an average and min/max time of latency. It could be an average of 6 seconds but fastest would be 3 and slowest would be 12. And you can decide to design for the average or for the awful edge case of 12 seconds and that will drive your design decisions. As far as collating with an Eng/Dev all of the content on this channel comes directly from my work day to day with Eng and dev folk. I’ll try to incorporate those nuggets of how to collaborate most effectively as a motion designer with those roles on future videos. In how they would build this gallery loading example would be taking my motion specs and building it in their environment. it would be set to when all the data is loaded then transition out the skeleton ui and transition in the gallery images.
Thirty seconds per pulse seems a bit long… 😉 This was an excellent explanation of how to control perceived latency, and I enjoyed watching your discovery process of implementing different solutions and testing them.
