1. 9

While a general podcast, this episode has a segment on the psychology of loading screens and progress bars, which I believe fits the intent of the site.

  1.  

  2. 3

    Great podcast, great episode, and I already started using its lessons.

    For a report that takes a while to load, I made a percent-complete bar graph that ticks up to an upper-end estimated completion time. It’s basically fake - the loader doesn’t know anything about the report’s progress or when it’ll be done. But people like it! They’re much happier to sit and wait and less likely to click on something else out of impatience.

    Since I aim high on the time estimate, it usually finishes and displays the report before the loader graph fills completely. Seems bad, right? The loader’s not accurate, after all. But instead, people are happy it finished early. Under promise and over deliver.

    1. 1

      Do your users know that you’re intentionally lying to them? Wouldn’t a simple statement like, “please hang on, this will take a little bit” be more honest and just as effective? Are there any other ways of achieving the same thing possible without deceiving anyone?

      1. 1

        To me this doesn’t seem like a lie, but rather like an effective form of visual communication. It wouldn’t be a lie to display a hardcoded message saying “please wait, this usually takes about X time.” @observator’s loading bar has essentially the same informational content, the only difference being that the hardcoded “X” estimate is presented graphically, along with a helpful timer indicating how much of “X” has already elapsed.

    2. 1

      While a general podcast

      true, but it’s one of my (very few, I have maybe 2) favorite podcasts. Recommended if you like stories in the general direction of architecture and design.

      1. 1

        While most times progress bars and splash screens are good, occasionally they get in the way of what’s important: https://lwn.net/Articles/299483/

        “We hate splash screens. By the time you see it, we want to be done.” The development time that distributions spend on splash screens is much more than the Intel team spent on booting fast enough not to need one.