Today I would like to share with you about the 'Software Comfortableness' & 'how to identify good/bad software comfort' which will help you to test the UIs while moving with your projects.
S/w comfort is a pretty touchy-feely concept, which conveys the comfortable usage. Appropriateness,error handling and performance are some basic features of that. The very basic idea of these features as follows,
*Appropriateness, The proper look & feel of the software what it's doing and who it's for and also neither be too garish nor too plain for the task It's intended to perform.
*Error handling, It should warn users before a critical operation and allow users to restore data lost because of mistake
*Performance, It should be flashed error messages too quickly to read and If an operation is slow, It should at least give the user feedback on how much longer It will take & slow that It's still working like status bars.
Hope this tip will help you, because Software Comfortableness is one of the important trait of common good UI.
No comments:
Post a Comment