How can it be regarded as a good UX software?

In the previous article,Windows VistaDiverse menu Appreciation"(I don't know why I'm not on the homepage ...... Cold ~~~~) Microsoft's menu was reviewed. Some netizens asked what should they do? In fact, this is a very complicated problem. Even if you doUX GuideTherefore, the requirements can only look good.Program. OneUXThe fundamental principle of good software is very simple-"easy to use, easy to use" (yourselfYY). Why is a dummies camera so popular? Click a button to take a picture. This is enough.

 

But on the software, this "easy to use, easy to use" is not so easy. Easy to use, it will take a look,IPhoneOne reason for popularity is ease of use. You don't need to read the instruction manual. When you want to perform an operation, you feel that it should be done in this way, so it will succeed. This is what users think. What programmers are most likely to do is to look at the software from the programmer's perspective and think about problems. But not from the user's point of view. It is also a dummies-level user perspective.

 

It's easy to say, but when it comes to software, there will be more to do. BelowYYSome. For reference only.

 

1.Nice looking. It's better to have an animated effect. From the programmer's point of view, it is still difficult to do anything practical. However, this is a trend, and users do not care about it.

2.ConfigurableShortcut Keys. Is the shortcut key.

3.ReasonableAccess key. It is an underscore in the menu.

4.CompleteTooltipSystem, inEnableAndDisableThere must be differentTooltip. You need to tell the user why to disable one item.

5.Verify user input and useBalloon tipOtherwise, the user is prompted for illegal input.

6.The data control should support drag and drop. For exampleTreeview, listviewControlItemYou can drag it.

7.The data entered by the user, such as the user name, should have a historical list.

8.Unlimited supportUndo/Redo.

9.Status system: displays the current state of the program in the status bar when performing the operation.

10.Complete help documentation. And can be used in the programF1Key to call up the most appropriate help document page.

11.Extract all the configuration items and let the user decide the program behavior.

12.Control. Disable or hide invalid controls. It should be disabled.

13.When the startup time of the program is long, first display the sputtering window (Splash Screen).

14.For long-time operations, cancellation must be supported in the middle.

15.Multi-language support.

16.For personal software, it is also important to support theme colors and skin replacements.

17.The interface meets the requirements released by Microsoft.UX GuideTo provide a flexible and adjustable interface layout.

18.Supports automatic upgrade or reminder upgrade.

19.......

 

If the software also involves documentation. Consider the following.

1.Document correctness test. Verify the correctness of the document data before loading it.

2.The robustness of the program must at least meet the requirement that the document data is not damaged or lost when the program ends abnormally. Or it can be repaired after being damaged.

3.The document must be compatible with the following parameters. Or provide automatic upgrade of document files.

4.Open a document file in exclusive mode, or monitor changes to the document file during runtime.

 

Good UX certainly has many things to do. You are welcome to add.