"Content is definitely a tricky thing to manage when it comes to crafting adaptive experiences, but it’s all about prioritization. Blogs are easy—I wrote about flipping the Easy Designs blog on its head a few months back (http://blog.easy-designs.net/a... sites are a bit more complicated. Over the years, I’ve become a big believer in a mobile first approach where you begin with the critical content needed to understand and complete necessary tasks and then build up from there. That approach fits in neatly with progressive enhancement and also gets you huge accessibility wins right out of the gate."
- Aaron Gustafson
"I have not dug into the particulars of the setup, but Ben & Dion (of FunctionSource) mentioned (in their Future of Web Design talk earlier this year) that they are using the same JS on the server side as on the client and the decision as to which avenue the server goes down is made when the user first hits the site. I’d love a detailed write-up from them at some point as to how they did it and where the decision points are in terms of how to handle the client."
- Aaron Gustafson
"Oh, and I forgot to mention that I think the idea of using Node.js in conjunction with front-end JS is a really interesting idea and offers a very appealing solution: No JS on the client? Run it on the server."
- Aaron Gustafson
"As a major proponent of both Progressive Enhancement and JavaScript, I think the answer to your question is _it depends_. I would wager that 80-90% of the websites out there are completely capable of using JavaScript in a progressively enhanced way to accomplish their goals. These are the sites for which JavaScript simply provides an enhanced experience by means of widgets and other UI niceties. As for the other 10-20% of sites out there are likely web applications (a la GMail, Basecamp, etc.). While a certain percentage of these apps certainly *could* be built progressively, from a practical business standpoint, that may not be tenable. My feeling for these sites/apps is that if they require some form of sign-up to use them, they can require a bit more of their users in terms of browser and technology support (provided they are upfront about it). What I don’t like to see is general-use websites (brochure-ware sites especially, but also critical "apps" like online banking) that..."
- Aaron Gustafson
"I hadn't really thought of that as a use case, but I can see how it'd be valuable. I'll consider adding it in. Unless I'm missing something in the source, it doesn't appear that SmartStorage actually supports older IE versions using userData (which works back to IE5.5). It's pretty trivial to establish parity between the two and provide a unified wrapper."
- Aaron Gustafson
"I hadn't really thought of that as a use case, but I can see how it'd be valuable. I'll consider adding it in. Unless I'm missing something in the source, it doesn't appear that SmartStorage actually supports older IE versions using userData (which works back to IE5.5). It's pretty trivial to establish parity between the two and provide a unified wrapper."
- Aaron Gustafson
"I do like a good Mint Julep, too bad most bars haven't a clue how to make one. @maddow:twitter had a great tutorial on her show though: http://www.msnbc.msn.com/id/26..."
- Aaron Gustafson
"I do like a good Mint Julep, too bad most bars haven't a clue how to make one. @maddow had a great tutorial on her show though: http://www.msnbc.msn.com/id/26..."
- Aaron Gustafson
Testing 1, 2. Test your site's content to improve usability, and design a mobile test bed to be sure your site works in more than just iPhone and Android.
- Aaron Gustafson