Related to: How not to do progressive enhancement.
I actually heard from Paramore|Redd today—a very nice surprise! Joel Steidl from P|R pointed me to the jQuery History plug-in, which seems to make possible just the sort of functionality I was getting at. Turns out, P|R was well aware of the small issue I pointed out, and is using the plug-in to great effect on their “Peeps” section, e.g. Joel’s own page. Browse through the employees using the forward and back buttons on the page and you’ll find that, while the page never reloads, the browser’s forward and back buttons work just fine. Bravo! Thanks for the reply, Joel.
http://layertennis.com/090501/04.php
I also spotted some exemplars on the El this weekend, including an ad for a Spanish cultural center and another brilliant example that, sadly, I’ve forgotten. Would have been a good time to own an iPhone
I had a somewhat unfortunate experience with JavaScript-based progressive enhancement today. It came at the hands of Nashville’s Paramore|Redd. To be clear, I’m not hating on the company; they obviously do great work.Their website just happened to exemplify a pretty common usability shortcoming.…
A few weeks ago, I signed up for Userfly, a screen capture webapp for usability testing. I elected to sign up or the free plan, which allows 10 captures of 10 or more seconds per month. After a pretty painless sign-up process, Userfly gave me a few lines of JavaScript code. This code allows Userfly to create video captures of users’ mouse movements, scrolling, and clicks on my site. Since I was just giving it a spin, I put this code on my index page only. Here’s what happened:…
Zeldman links to this study on the importance of various usability factors correlating to gender: http://www.websiteoptimization.com/speed/tweak/usability-criteria/. Well worth a read (and it’s short), but why does this website completely ignore other factors of optimization, such as measure (line length)?