AI summary by TwinMind

Why Progress Bars Don't Move Smoothly ▓▓▓░░░░░░

Tom Scott

5m 10s

Real-World vs Digital Progress Indicators

  • Real-world progress bars work well (pedestrian crossings, elevators, queues)
    • Physical signs show progress happening
    • Can estimate wait times based on observable movement
    • Provide reassurance that things are moving forward
  • Computers are "mysterious boxes" without visual progress indicators
    • Impossible to tell if task barely started, finishing, or stuck
    • Need progress bars to show something is happening

Simple Progress Bar Mechanics

  • Basic concept: show completed items out of total items
  • Video progress bar example: 1 minute 24 seconds of 5 minutes 10 seconds total
  • Video players have single job: display frames at steady pace
  • Works because task is predictable and consistent

Complex Installation Process Challenges

  • Program installation involves multiple unpredictable steps:
    • Download files from internet
    • Decompress files
    • Save files to disk
    • Read/delete existing files
    • Modify system settings
  • Each step varies dramatically between machines:
    • Download speed depends on internet connection
    • File operations depend on disk speed and file states
    • Physical spinning disks: location of data affects speed
    • System changes depend on operating system
  • Impossible to create smooth progress bar for complex processes

File Copying Progress Bar Problems

  • Counting files approach fails when file sizes vary dramatically
  • Counting data transferred fails because:
    • Many small files take longer than few large files
    • Extra time needed to switch between files
  • Even simple tasks cause progress bar speed fluctuations

Time Remaining Estimation Issues

  • Based on elapsed time vs remaining work
  • Fails because transfer/processing speeds change constantly due to:
    • User switching to other applications (games, videos)
    • Background notifications and downloads
    • Device thermal throttling from overheating
    • Automatic system maintenance processes
  • Rolling average approach: use last 10-20 seconds instead of total time
    • Still wrong but "differently wrong"

Philosophy of Progress Bar Design

  • Perfect accuracy not essential for progress bars
  • Smooth progress bars can indicate artificial delays (scammy websites with ads)
  • Progress bars should be "little bit janky" to reflect real processes
  • Primary purpose: reassure users that progress is happening
    • Not precise time estimates
    • Prevent users from rebooting due to perceived crashes
    • Show "things are happening, progress being made, calm down"

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome