Eliminate Unnecessary Setup Screens

A typical setup program has a collection of fairly standard screens. Some of these screens perform an essential function; others do not. Let's take a look at each type of setup screen and consider if it is necessary.

The Welcome Screen

The welcome screen introduces the user to the setup program. It serves to clearly identify what the setup program is about to install. It also "strongly recommends" that the user quit all other Windows programs before continuing. This is good advice, since Windows cannot overwrite a file while it's in use, so quitting all other programs eliminates the need to restart Windows when the setup is complete. However, this isn't much information for an entire screen. This screen can be eliminated.

The End-User License Agreement

Many setup programs display the familiar end-user license agreement, which says something to the effect that the user doesn't actually own the software (just a license to use it), that the user can't make illegal copies, and that the user can't sue the vendor if it doesn't work right. By the user clicking the Yes button or the I Accept button, the theory is that this is supposed to create a legally binding contract between the user and the vendor.

My recommendation is that if you are truly concerned about protecting your company, you should speak to a lawyer for advice on creating an enforceable end-user license agreement. I wouldn't take it for granted that the typical license agreement in a setup program would hold up in court, although there is currently proposed legislation that would make them enforceable. The problem is that the "agreement" usually occurs after the financial transaction takes place. Include this screen if you or your council feels you must, but don't do it because you think everybody else does. This screen can be eliminated.

The Readme File

In the bad old days of MS-DOS and Windows programs, the readme file played a critical role in the installation process. It explained the entire process to the user and helped the user solve any problems—and there were usually problems. Readme files also contained any changes to the documentation added after it was printed.

Today, things are different. The setup program has the responsibility of guiding the user through the installation process and handling any loose ends. Any instructions necessary to perform installation should be in the setup user interface itself or its Help file. Most documentation is online, so there is no excuse for asking the reader to view the readme file for the latest changes because you couldn't update the documentation in time. Consequently, the role of the readme file has changed. The readme file is best regarded as your last defense against technical support calls. So now the key question: does the user need to see the readme file during the installation process? The answer is clearly no. The user is not interested in this information unless the installation process failed. You shouldn't overexpose the readme file during the setup process. This screen can be eliminated.

TIP

---

Don't overexpose the readme file during the setup process.

User Information

This screen asks the user his name, company, and serial or registration number. Notice that the user name and company information is readily available in the registry. This screen can be eliminated unless a serial or registration number is required. At the very least, use registry settings to provide defaults for this screen.

Choosing the Destination Folder

This screen displays the default destination folder and gives the user the ability to choose another folder instead. If the default destination folder is well chosen, there is little reason to change it. Surprisingly, I find that the default folder is often poorly chosen. Common mistakes include using 8.3 filenames, not using a Program Files subfolder, and using awful-looking names like Expl Flder or EXAMPLE FOLDER. Another good reason to change the default destination folder is to install to another hard disk. Since it's important for the user to have control over his hard disk, this screen is required.

Choosing the Setup Type

This screen allows the user to select the type of installation. The choices are usually Typical, Compact, or Custom. As hardware improves, the exact meaning of Typical and Compact should probably change with time. With disk space costing pennies per megabyte, there's really no need to give the user options to save 100 KB of disk space. Laptops are now just as powerful as desktops, so there is no longer a reason to have a distinct setup type for laptops. Furthermore, CD-ROM drives have much better performance now, so there is less of a need to bother the user about caching files for CD-ROM-based programs. However, the larger the footprint of the program, the more important these choices are. Again, since it's important for the user to have control over his hard disk, this screen is required for large programs.

Selecting the Start Menu Program Folder

This screen gives the user the opportunity to select the name of a new Start menu program folder or to select an existing program folder. By installing to an existing program folder, users can eliminate some of the clutter in the Start menu. Since it's important that the user have control over the desktop, this screen is helpful.

Summary of Current Settings

This screen summarizes the current settings and gives the user a last chance to change them before copying files. However, unless the user is performing a complex custom install, the user simply hasn't made enough choices for such a verification to be necessary. This screen can be eliminated.

Setup Completion

This last screen indicates that the installation was successful and typically gives the user options to display the readme file or immediately launch the program. As I noted previously, if the program was successfully installed, the user should have little need for the readme file at this point. Of course, the reason users install programs is to use them, so if the program were to automatically launch immediately after installation, that would be a clear indication that the installation was successful. This screen can be eliminated.

Setup Failed

This alternative last screen indicates that the installation failed and gives the reason why. Now is the time to give an option to display the readme file. This screen is required.

Online Registration

Many setup programs have online registration as a bonus screen once the program has been installed. The most interesting observation about online registration is that it benefits the vendor, not the user. The user would just as well not fill in another form. I rarely perform online registrations. When I do, it is because the vendor has made an effort to present a clear and compelling benefit to registration. Saying something like Register to Win! or Register for Free Support usually does the trick.