<story><title>Why some apps use fake progress bars (2017)</title><url>https://www.theatlantic.com/technology/archive/2017/02/why-some-apps-use-fake-progress-bars/517233/?single_page=true</url></story><parent_chain><item><author>diplomatpuppy</author><text>I had a report in Microsoft Access that took about five minutes to run - and the users hated it.&lt;p&gt;I had the application throw up a fake dialog with fake messages about &amp;quot;Collating data, Cross checking, Sorting&amp;quot; and other such nonsense.&lt;p&gt;The report now took eight minutes to run because I had to abuse the &amp;quot;On Timer&amp;quot; event for it to work.&lt;p&gt;The users were delighted with the improvement.</text></item></parent_chain><comment><author>JoshMnem</author><text>That is one thing I dislike about sites that show no loading bar. On a slow connection it&amp;#x27;s impossible to tell if the page is still loading or already failed.&lt;p&gt;It&amp;#x27;s also one of the irritating things about &amp;quot;Material Design&amp;quot; websites, where responses to clicks are artificially delayed before speeding out with unnatural acceleration. &amp;quot;Nothing is happening. JUST KIDDING!&amp;quot; I&amp;#x27;m not sure if that is to mask the slowness of mobile devices or if it&amp;#x27;s the cause of them. It&amp;#x27;s the animation spam[1] of the current generation of UIs.&lt;p&gt;* [1] &amp;quot;Let&amp;#x27;s make our website sparkle. It will be &amp;#x27;delightful&amp;#x27;.&amp;quot; &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;dynamicdrive.com&amp;#x2F;dynamicindex3&amp;#x2F;snow.htm&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;dynamicdrive.com&amp;#x2F;dynamicindex3&amp;#x2F;snow.htm&lt;/a&gt;</text></comment>
<story><title>Why some apps use fake progress bars (2017)</title><url>https://www.theatlantic.com/technology/archive/2017/02/why-some-apps-use-fake-progress-bars/517233/?single_page=true</url></story><parent_chain><item><author>diplomatpuppy</author><text>I had a report in Microsoft Access that took about five minutes to run - and the users hated it.&lt;p&gt;I had the application throw up a fake dialog with fake messages about &amp;quot;Collating data, Cross checking, Sorting&amp;quot; and other such nonsense.&lt;p&gt;The report now took eight minutes to run because I had to abuse the &amp;quot;On Timer&amp;quot; event for it to work.&lt;p&gt;The users were delighted with the improvement.</text></item></parent_chain><comment><author>mrisoli</author><text>I remember reading long ago about how they did something similar at an airport(Dallas IIRC).&lt;p&gt;Basically, people complained about baggage claim taking too long, so they just moved the baggage claim area to the other side of the airport, so it took longer for passengers to reach it, by the time they did, their bags would already be there, so the complaints stopped.</text></comment>