m o t i o n l e s s
m o t i o n l se s
m o t i o n sle s
m o t i osn l e s
m o t i so n l e s
m o t si o n l e s
m ost i o n l e s
m so t i o n l e s sm o t i o n l e s s om t i o n l e s s o m t i no l e s s o m t ni o l e s s o m nt i o l e s s o m n t oi l e s s o m n oti l e s s o m n o t lie s s o m n o lt i e s s o m n o l it e s
I've been tracking my listening habits with last.fm since I was in high school. As I'm about to turn 30, it's nice to be able to look back on almost my entire adult life – to see how I've changed and how my tastes have changed with me.
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?