Mouse Interface Summary."
Total Page:16
File Type:pdf, Size:1020Kb
Official Guidelines for User Interface Developers and Designers Welcome to The Microsoft Windows User Experience, an indispensable guide to designing software that runs with the Microsoft® Windows® operating system. The design of your software's interface, more than anything else, affects how a user experiences your product. This guide promotes good interface design and visual and functional consistency within and across Windows-based applications. © Microsoft Corporation. All rights reserved. Fundamentals of Designing User Interaction Windows Vista User Experience Guidelines Getting Started What's New? The Importance of a Well-Designed Interface The Need for Improving Simplicity Key Areas for Improvement Checklist for a Good Interface Design Principles and Methodology User-Centered Design Priciples Design Methodology Understanding Users Design Tradeoffs Basic Concepts Data-Centered Design Objects as Metaphor Putting Theory into Practice The Windows Environment The Desktop The Taskbar Icons Windows Input Basics Mouse Input Keyboard Input General Interaction Techniques Navigation Selection Common Conventions for Supporting Operations Editing Operations Transfer Operations Creation Operations Fundamentals of Designing User Interaction Windows Interface Components Design Specifications and Guidelines Appendixes and References © Microsoft Corporation. All rights reserved. Fundamentals of Designing User Interaction - Getting Started Getting Started This chapter includes an overview of the new features and controls provided by Microsoft Windows. It also includes a summary of the key design issues for applications written for the Windows interface. What's New The Importance of a Well-Designed Interface The Need for Improved Simplicity Key Areas for Improvement Checklist for a Good Interface Fundamentals of Designing User Interaction Windows Interface Components Design Specifications and Guidelines Appendixes and References © Microsoft Corporation. All rights reserved. Fundamentals of Designing User Interaction - Getting Started What's New This book includes information about designing user interfaces for applications that run on Microsoft Windows 98 and Microsoft Windows 2000. It also describes the new interfaces and conventions used in these operating systems. These features include the following: ● New input conventions ● Automatic (hover) selection, wheel mouse button actions — See Chapter 5, "Input Basics," and Chapter 6, "General Interaction Techniques." ● New controls ● Date picker, HTML control, toolbar frames — See Chapter 8, "Menus, Controls, and Toolbars." ● New file common dialog boxes ● File Open, File Save As, File Print, and Browse for File — See Chapter 9, "Secondary Windows." ● New Help support ● HTML Help, balloon tips, InfoTips, simple wizards — See Chapter 13, "User Assistance." ● New folder conventions ● My Documents, My Pictures, thumbnails, Web views, Active Desktop — See Chapter 11, "Integrating with the System." ● New system integration support and utilities ● Multiple file association support, NoOpen file registration, operating system-protected files, Quick Launch toolbar, multiple monitor support, Disk Cleanup, Windows Installer — See Chapter 11, "Integrating with the System." If you are designing an application to run on a previous version of Windows, a Windows Service Pack may be available. The Service Pack enables you to upgrade the system code to include some of these new features. This book also includes information about the evolution of application design and the impact of the Internet on conventional application design. While this book does not explicitly include Web page design guidelines, it does include recommendations about Web-style applications. Fundamentals of Designing User Interaction Windows Interface Components Fundamentals of Designing User Interaction - Getting Started The Importance of a Well-Designed Interface The usability of your application's design is not just a philosophical nicety for your consideration; it is essential to the success of your application. The investment you make in the design of your application contributes not only to supporting and keeping your existing customers, but also to expanding your customer base. Therefore, your investment in the design of your application directly affects your current and future bottom line. If you design or develop software for the Windows platform, you are part of an industry that is creating some of the most exciting and innovative applications available. More applications and more types of applications are being written for the Windows platform than for any other environment. In addition, increased support for accessibility and localization of applications means that applications are reaching a larger audience. New hardware initiatives and innovative technologies are making computers better for end users. The wide use of features such as common dialog boxes and controls has increased consistency between applications. In short, application developers for Windows are doing a great job of promoting the growth and use of computers everywhere. Fundamentals of Designing User Interaction Windows Interface Components Design Specifications and Guidelines Appendixes and References © Microsoft Corporation. All rights reserved. Fundamentals of Designing User Interaction - Getting Started The Need for Improved Simplicity Despite the popular support for Windows, there are still substantial challenges in providing the best experience for users. Computers are still too complicated to use, and support costs are high. Users frequently complain about the number of features they find in applications; they can't find the features they care about, and they can't figure out the features they do find. Many users expect a computer to be as easy to use, and as predictable and reliable, as an appliance. They want a computer to work in a way that is familiar to them. Therefore, simplicity of design involves issues that must be addressed by everyone building applications for Windows. Delivering simplicity does not mean just removing functions. It requires work. Even a simple interface can require a significant investment of code. However, the rewards and benefits are substantial, including reduced training and support costs and productive, loyal customers. Fundamentals of Designing User Interaction Windows Interface Components Design Specifications and Guidelines Appendixes and References © Microsoft Corporation. All rights reserved. Fundamentals of Designing User Interaction - Getting Started Key Areas for Improvement This book offers many recommendations for designing Windows-based applications. The most common design issues are summarized below. You can find more detail throughout the following chapters. Confusing or Awkward Setup and Uninstall Design Often, how users will install an application is not addressed until near the end of the development process. Yet because this is the first interface that users see, it is one of the most crucial elements of your application's design. Complex, Cluttered Setup Setup programs often have too many steps, requiring the user to click too many times. You can simplify your setup design by including typical and custom installation options. Use the typical installation option to provide a smooth, easy setup that doesn't overwhelm the user with options, and include default settings that give the user a reasonable configuration. For example, don't require that the user supply the target folder. Instead, you can display the recommended subfolder in the system's Program Files folder as the default. Whenever possible, reduce the number of mouse clicks and pages of options, especially for the typical installation. Bad setup design is also often characterized by the three "R's": reboots, Readme files, and random windows. Unless it is absolutely necessary, avoid requiring the user to restart the computer. Restarting is not only inconvenient for users, it could cause them to lose data because they didn't save changes to open files. To avoid the need to restart, the installation program should detect whether the currently running dynamic link libraries (.dll) or executable (.exe) files are to be replaced and give the user the opportunity to close any applications that might be affected. Programs that update system components typically require that the computer be restarted. Generally, this is a bad practice that can make the system unstable and confuse the users. To minimize the need for restarting the computer, avoid modifying core system components or installing files in the Windows System (or System32) folder. For more information, see the Microsoft Platform SDK on the MSDN Online Web site at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ shellcc/platform/shell/reference/ifaces/ishelllink/ishelllink.asp and the Windows Logo Program at http://msdn.microsoft.com/winlogo/. Whenever possible, avoid including unnecessary information in a Readme file. Plan your application's design far enough ahead so that users do not need to be aware of too many special circumstances. Do not include technical support information on the Start menu. This just adds clutter and makes it harder for users to access their applications. Similarly, don't include technical support information as an option in your setup program. Instead, add an entry to your Help menu that accesses this information, or just leave the file in your application's folder. Finally, avoid displaying unnecessary message windows while the user is installing