Ideas.

There are a few ideas floating around now to deal with images and media queries. There are all mostly inefficient ideas, so I’m throwing my hat in the ring.

So many responsive design solutions involve client-side detection, polyfills, data-attrs and event remapping. This all works fine, but as more and more sites begin to move toward a responsive design the importance of JavaScript optimization is more relevant than ever. More often than not, implementing a responsive design means more JavaScript and more logic. The Kb size debate for responsive sites is important, but often overlooked is the computational impact.

I’m not a micro-optimization troll (there’s plenty of that out there), but it’s shocking how some devices perform with the simple things we all take for granted. I would argue that for most devices, processing and latency are more important than Kb size.

So let’s take a look…

Interesting stuff coming out about js Classes in Alex Russell’s blog post.

I’m a of fan of classes for some things in js (modular widgets, mostly). So I hope this fight is not over. Max/Min is all I really want anyway.

Here’s a great response by Malte Ubl.

Update: Refactored to remove namespacing.

A lot has been said about Responsive Design lately. It’s primary a design movement, but the real problem it tries to solve is making content “flow like water.” To me it’s not about media queries, or 100% image widths, it’s about: one url, one codebase, and future-proofing new capabilities to maximize user experience.

Therefore, I give you: Responsive Modules.

I was recently asked to put together a list of the most important issues in UI development on the web today and here’s what I came up with:

Well now that I got your attention…

When looking for a good strategy for implementing a responsive design, web devs are bombarded with tons of techniques, libraries, polyfills, and workarounds. Most of the time, we don’t need them.

Well, let’s give this a go…