http://www.nagarro.com/blog/the-usability-of-programs-part-2-of-2/ Nagarro blog: software development, design, architecture and usability Fri, 23 Dec 2011 18:21:47 -0800 http://wordpress.org/?v=2.8.4 hourly 1 http://www.nagarro.com/blog/the-usability-of-programs-part-2-of-2/comment-page-1/#comment-854 steve Fri, 23 Dec 2011 18:21:47 +0000 http://blogs.nagarro.net/kayser/the-usability-of-programs-part-2-of-2/#comment-854 pears color pears color

]]> http://www.nagarro.com/blog/the-usability-of-programs-part-2-of-2/comment-page-1/#comment-833 » What makes easy things … easy? Sequence Mediaworks Sun, 09 Oct 2011 05:29:16 +0000 http://blogs.nagarro.net/kayser/the-usability-of-programs-part-2-of-2/#comment-833 [...] the web (or any device) have consistent, predictable interfaces. (I’m not the only one with this view.) Users will only need to get used to one visual layout, which means the organization of the [...] [...] the web (or any device) have consistent, predictable interfaces. (I’m not the only one with this view.) Users will only need to get used to one visual layout, which means the organization of the [...]

]]> http://www.nagarro.com/blog/the-usability-of-programs-part-2-of-2/comment-page-1/#comment-689 Sequence Mediaworks Blog » What makes easy things … easy? Tue, 24 Aug 2010 18:40:22 +0000 http://blogs.nagarro.net/kayser/the-usability-of-programs-part-2-of-2/#comment-689 [...] the web (or any device) have consistent, predictable interfaces. (I’m not the only one with this view.) Users will only need to get used to one visual layout, which means the organization of the [...] [...] the web (or any device) have consistent, predictable interfaces. (I’m not the only one with this view.) Users will only need to get used to one visual layout, which means the organization of the [...]

]]> http://www.nagarro.com/blog/the-usability-of-programs-part-2-of-2/comment-page-1/#comment-172 Nidhee Pathak Thu, 25 Oct 2007 11:14:33 +0000 http://blogs.nagarro.net/kayser/the-usability-of-programs-part-2-of-2/#comment-172 Assumptions on behavior of an entity which is external to the current scope of context is a dangerous thing. This holds good in mostly all cases whether it is the user interface design, integration with external systems or integration between different components. It is important to make sure that the component in question should be independant in its own right and even if it is required to work in conjuction with another, it should be completely usable (and re-usable!) on its own. Assumptions on behavior of an entity which is external to the current scope of context is a dangerous thing. This holds good in mostly all cases whether it is the user interface design, integration with external systems or integration between different components.
It is important to make sure that the component in question should be independant in its own right and even if it is required to work in conjuction with another, it should be completely usable (and re-usable!) on its own.

]]> http://www.nagarro.com/blog/the-usability-of-programs-part-2-of-2/comment-page-1/#comment-171 Ramesh Soni Mon, 22 Oct 2007 09:18:56 +0000 http://blogs.nagarro.net/kayser/the-usability-of-programs-part-2-of-2/#comment-171 Regarding "Avoid modality", there is another instance when the user is closing a edit dialog without saving the change. In this case we usually ask user for saving the changes done by him. This is usually done by adding dirty ability to our object. I read an article (http://www.codinghorror.com/blog/archives/000075.html) by Jeff Atwood, which says that your application should not ask for this. It should automatically save and version your changes. What is the most appropriate way of doing this? Almost all of the projects I worked so far don't have this feature. Regarding “Avoid modality”, there is another instance when the user is closing a edit dialog without saving the change. In this case we usually ask user for saving the changes done by him. This is usually done by adding dirty ability to our object.
I read an article (http://www.codinghorror.com/blog/archives/000075.html) by Jeff Atwood, which says that your application should not ask for this. It should automatically save and version your changes. What is the most appropriate way of doing this? Almost all of the projects I worked so far don’t have this feature.

]]>