Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like what you are referring to is a blog post by Alex McCaw who originally named it "Asynchronous User Interfaces" (AUIs):</p> <p><a href="http://blog.alexmaccaw.com/asynchronous-ui" rel="nofollow">http://blog.alexmaccaw.com/asynchronous-ui</a></p> <p>The reply posted by Joseph referring to a technique used in multiplayer games is actually called "dead reckoning." Back in the 1990s when we were using 56k dial-up modems, latency was a severe problem in real-time multiplayer games. To mask latency, "dead reckoning" was introduced in games such as Quake where a player's path was extrapolated based on his predicted direction, velocity, etc.</p> <p>Here's an article I remember from back then that used this jargon: <a href="http://www.gamasutra.com/view/feature/3230/dead_reckoning_latency_hiding_for_.php" rel="nofollow">http://www.gamasutra.com/view/feature/3230/dead_reckoning_latency_hiding_for_.php</a></p> <p>Dead reckoning is still used today. The innovation primarily involved the use of extrapolation over interpolation: rather than waiting for packets to arrive and interpolating (which would always be behind the real events), extrapolation is used to try and predict where a player or object might be. However, the real event does <em>not</em> "replace" the prediction. If the previous prediction was incorrect, we use any new data that arrived to try and create a more accurate new prediction rather than just "teleporting" the player or object to the correct new position.</p> <p>The same principles should be applied to UI design. How can you design your asynchronous UI so it provides the best prediction? If the prediction fails, how can you avoid "teleports?" For example, in a poll, if you're providing predicted poll results, and your predictions are way off and you subsequently "correct" your prediction by providing substantially different results, it would only serve to confuse the user when the "correction" arrives. So while it's up to your creativity here, you can use existing techniques such as "prefetching" in the poll example.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload