Here are some things to think about when you're evaluating an application:
- Is it easy to use? If it uses a standard interface (that is, if it follows the conventions described in Chapter 3), it will be easier to learn than an application with an unconventional user interface. A good manual is another thing that makes an application easier to learn. As important as it is, don't make simplicity your only criterion. Sometimes an application is easy to learn because it doesn't do much. If you find a simple application, make sure it also has the features you want.
- Does it take advantage of Apple IIGS features, or is it designed to run on all models of the Apple II family? Applications designed especially for the Apple IIGS can take advantage of super-high-resolution graphics and other Apple IIGS specific features. If that's important to you, look for new applications or applications that have been revised to take advantage of Apple IIGS features. If, on the other hand, it's important that the applications work on other models of the Apple II, make sure the application is advertised as Apple IIe-compatible, Apple Ilc-compatible, or Apple II Plus-compatible.
- Is it compatible with other applications you have? Can you insert a list created with your data base into a letter written with your word processing application? Applications designed to work together and share information are called integrated software.
- Does it work automatically with your printer? The key word here is automatically. Hackers can make all sorts of different devices talk to each other, but if troubleshooting isn't your idea of a good time, look for software that's already configured for your printer.
- Does it do exactly what you want it to do? Sometimes it's worth sacrificing ease of use and the standard user interface to get an application that does exactly what you need to do.
- If the application is complicated, are there classes you can take to learn how to use it?
