“Contrary to what you may read, peppering your form with nice buttons, color and typography and plenty of jQuery plugins will not make it usable. Indeed, in doing so, you would be addressing (in an unstructured way) only one third of what constitutes form usability.
In this article, we’ll provide practical guidelines that you can easily follow. These guidelines have been crafted from usability testing, field testing, website tracking, eye tracking, Web analytics and actual complaints made to customer support personnel by disgruntled users.”
“A couple of weeks ago, I shared an Employee Directory sample application built with jQuery Mobile and PhoneGap. That application was implemented ‘Ajax-style’, keeping the UI and the data access code cleanly separated. In other words: no server code intermingled in the HTML markup.
A number of people have asked for a similar example using a ‘classic’ (non-Ajax) implementation where pages (markup + data) are entirely built at the server-side before being delivered to the client.
So, here is simpler version of the same application built ‘sans Ajax’. I used PHP in this version, but you can of course use your favorite server-side technology (Java, .NET, CF, RoR, etc).”