Tactile. Posted: December 12th, 2012 Author: Shaun Progressive enhancement is a Front-end Development practice that ensures your clients can still operate a webpage without (for instance) JavaScript support.JS-driven widgets typically have styling applied, so it’s important to only add those styles if JavaScript is supported. One of the better ways to do this is by adding the relevant classes via JavaScript, but leaving the control of these classes in the HTML.
Let me explain… Read the rest of this entry » Posted: December 11th, 2012 Author: Shaun After building the front-end on a number of web apps, I’ve noticed there are a number of common functions or helpers each web app needs for Front-end development purposes. Some tasks are trivial to solve, by virtue of being included in some web app frameworks, others are repeat offenders that you find yourself building for each and every web app. App-wide needs The web app should set a default language code This acts as the basis for an i18n setup. Conclusion. Tactile » Blog Archive » Another SA UX Cape Town meet-up in the bag. Posted: February 25th, 2010 Author: Shaun I don’t know how we do it, but each event we have for the SA UX Forum in Cape Town just seems to be better than the last. 60 chairs were laid out at the Bandwidth Barn tonight, we had wine sponsored by the CITI and snacks + drinks available.
We were expecting less than 60, but in the end 75 UX-keen people showed up. This meant a dash for more space and seating, somehow we just managed to squeeze everyone in. Why all the interest? Phil Barrett’s infectious charm has a lot to do with it. The caterers were waiting patiently for us after the first talk which ended at 8:30pm. Jason Hobbs, one of the Johannesburg SA UX big-wigs, then gave a talk after the break on “The door, the wind, the bird and the valise.”. User Experience and its varied disciplines are very much in their infancy, when compared to established industries such as medical or financial ones. What next? We’re taking notes and had a lot to learn from tonight. Until the next time… Www.mantaray-it.com. SA UX forum. Groups. The $300 Million Button. By Jared M. Spool Originally published: Jan 14, 2009 Editor's note: Thanks to Marco Dini, you can now read this article in Italian. [While Luke Wroblewski was writing his well-received book, Web Form Design: Filling in the Blanks, he asked if I could think of an example where a change in a form's design made a noticeable difference in business.
How Changing a Button Increased a Site's Annual Revenues by $300 Million It's hard to imagine a form that could be simpler: two fields, two buttons, and one link. The form was simple. The problem wasn't as much about the form's layout as it was where the form lived. The team saw the form as enabling repeat customers to purchase faster. "I'm Not Here To Be In a Relationship" We conducted usability tests with people who needed to buy products from the site. We were wrong about the first-time shoppers. Some first-time shoppers couldn't remember if it was their first time, becoming frustrated as each common email and password combination failed.