Intuitive UI on the Web

I read this blog some time back and just loved the small things which the author considers.

He makes few good points:
  • Auto saving to prevent data loss.
  • Providing "undo" on the web which allows users to correct their mistakes.
  • The simplest thing to do in a modal overlay would be to have a cancel button on the top right.










Well, I have been working on the web for almost over a couple of years now. And to be honest, with all the development efforts which go into the application, I think UI takes a back seat. Unless of course, you have full time dedicated designers.

UI to me should be measured with 2 parameters,
  1. how intuitive is it functionally?
  2. how attractive is it visually?
We can keep the 2nd point for professional designers. As for developers, making the UI intuitive seems to be the key.

Comments

Post a Comment

Popular posts from this blog

Introduction to functional programming

I vaguely remember reading something about functional programming back in my engineering days. We did study Lisp and Prolog a bit, but it was done at a very abstract level. Ever since i joined the industry i have been writing object oriented code, or so i like to believe :) The point being that am completely new to this paradigm. Functional programming languages have largely been emphasized in academics rather than in commercial software development. However lately, few functional languages have gained popularity. Erlang - used by Facebook for their Instant Messaging. OCaml - used for financial analysis Scheme - used for training simulation software and telescope control Scheme (which is a dialect of Lisp) was in fact used in early macintosh computers. What exactly is functional programming? Its difficult to give a precise definition, but generally speaking: In functional programming the basic method of computation is the application of functions to arguments. It also avoids sta...
Read more

Identifying IE browser usage correctly

How was IE browser usage being captured? The user agent string that IE identifies itself with includes the name and version number. For eg, IE 7 user agent will include MSIE 7.0, IE 8 will include MSIE 8.0 and so forth. The Splunk query that we used extracted this “name followed by version” token and derived usage statistics. Why did my team re-analyze at the browser usage statistics? For a particular client, we noticed heavy and consistent traffic from IE 7.Our Splunk query suggested around 550 users using IE 7, while the client claimed to have migrated to higher versions of IE. What was the observation after analysis of raw HTTP headers sent by IE? IE 8 onwards Microsoft started shipping every newer version of IE along with “compatibility mode”. If a page was working in IE 7 and breaks after IE 8 upgrade, user can switch to “compatibility mode”. However, in this mode, IE 8 (and all higher versions) user agent contains name and version as “MSIE 7.0”.  Hence, th...
Read more

Comparison operators in JavaScript

Another pretty weird but some may argue powerful feature of JavaScript is the way it handles comparisons. In JavaScript, (false==0) , (null==undefined), (""==0) all result in TRUE! Weird? You bet it is! What JavaScript does behind the scene? It uses pretty confusing and complicated set of rules while comparing values. In most cases it just tries to convert one of the values to the type of the other value. However, when null or undefined occur, it only produces true if both sides are null or undefined. For cases where you do not want any automatic type conversions to happen, there are two extra operators: === and !==. The first tests whether a value is precisely equal to the other, and the second tests whether it is not precisely equal. So now, (false===0) , (null===undefined), (""===0) will all return false as expected! Amusing, isn't it? Reference: http://eloquentjavascript.net
Read more