One of the reasons it makes so much sense to work on an application like gRSShopper even though I know it will never be a commercial product (or even widely used) is that it exposes me to the deep technical issues that are so important (and so often overlooked) in educational technology. This article describes one of them: the loading experience. How do you write applications so that all the components load in the right order, so that the user experience is slick and seamless? "There are metrics like total requests, page weight, time to glass, time to interactive, first input delay, etc. There are things to think about like asynchronous requests, render blocking, and priority downloading." Putting something useful on the screen as fast as possible is an art, and it is often overlooked.
Today: 4 Total: 4 [Direct link] [Share]
