After get off work, I saw the paragraph .Net Show: Inside CLR, don't laugh, my Soil is successful? Because "user experience". Although this is just a conversation program, the video has segmented, you can choose to play the content, next to the conversation of the entire program, you can even choose to position to a certain conversation content play, and the current conversation content will have Highlight, let you know what is going on. Lenovo has a lot of learning. Net is easier than Java, a large extent because .NET has localized help, documentation, and closer to developers. It is relatively easy to learn. I remember that I had a "bad interface" article in several phases of "Non-programmers", listed a lot of inexplicable UI, including well-known software. Many questions should be considered when developing. It should be avoided. We often focus on the architecture in the actual project, how much efforts have been truly under the UI? Each small detail is considered by the user, how can the button can make the user's mouse to move the shortest distance, how can each menu or other control icon clearly represents its function? Of course, it is very difficult to completely reach this goal, but give the user a better experience, not only in the response speed, function, but also in terms of UI, document, user training, technical support. Kung Fu, I think it can be done. The mess is a bunch, everyone can throw the bricks.
