151
spacem
7y

Someone asked me once to put a timer in an installer to slow it down because apparently it would make the software seem to be more important if it took longer to install.

Ever since being asked this I now wonder does why it takes so long to install some software.. Do developers actually do this?

Comments
  • 7
    All the software I make is installed using .NET installutil from command line.

    "Installation complete. Press any key to continue" Take as long as you like.
  • 4
    In my first year of college I really couldn't be bothered to do any work so I made an "installer" that would infinitely loop, it looked real as hell and I could COMPLETELY imagine some developers doing this to make their application seem more important.
  • 6
    Actually, it could be an interesting feature consumer-oriented. The "feel" in "look and feel" is quite important for the user.
  • 6
    @Kalvin Expanding on your point, I wonder if there is a generic "sweet spot" that a user expects to wait for. Not so short that it's over in a flash, and not so long that they get bored. My gut feeling would be around 30s... just enough time to throw in an advertising loop and high-five Satan
  • 1
    @DevDez I'm sure there is. Also, the user will be more willing to wait if there is feedback from the installation. That high five sounds interesting as a feedback method.
  • 25
    For the full authentic Windows installer experience, the progress bar needs to get to 95% quickly, and then take 20 minutes for the remaining 5.
  • 1
    That's like adding a roaring exhaust to a bobby-car...
Add Comment