Posts tagged “progressive enhancement” 

When I opened my inbox this morning, I nearly fell over: Browser makers are considering supporting the WebKit vendor prefix (-webkit-*) because the web development community can’t be bothered to use the equivalent experimental properties for other browsers.

Last week I shared a link about progressive enhancement for mobile on Forrst and it elicited quite a reaction from one reader which, in turn, prompted a lengthy response from me. I thought it was a conversation worth archiving here.

Google’s over-engineering of the G+ button led us to drop support for G+ sharing when we re-launched the mobile-first version of this blog. We’ve anabled it now thanks to some help from the code spelunkers at TechLifeWeb.

After a whirlwid trip to 4 countries, I am back to a rock-solid internet connection and got a moment to take a breath and post my slides from the first stop on the trip: Beyond Tellerrand in Düsseldorf, Germany.

In the past few months, I’ve spent an inordinate amount of time discussing the differences between the “adaptive” and “responsive” web design philosophies. Don’t get me wrong, I love having these discussions, but I felt the need to set the record straight: these two philosophies are not at odds.

I just finished Day 1 of Future of Web Design here in NYC and wanted to post my slides before I crashed for the night. Enjoy!

This past week, Kelly and I were in Brooklyn for the ExpressionEngine CodeIgniter conference. We had a great time, met some awesome people, and I got to talk about my favorite topic: progressive enhancement.

You may not have noticed, but we just turned this blog on it’s head, design-wise. Those of you browsing on something other than a desktop browser should now be enjoying a much better reading experience. Here’s what’s changed and how we did it.

Last week, Steve Jobs resigned and Twitter launched a resource for quickly building prototypes and apps. Also: solar power keeps getting cheaper and airports are going to the bees.