The browser is a hostile development environment and supporting a wide range of desktop browsers can be tough work.
One of the immediate challenges we discovered when we first started the responsive news prototype was the large range of devices that we would have to support. It terrified us. This article is about a solution we use to alleviate this problem.
I recently attended the An Event Apart SF. It was eye opening and mind blowing. The web industry has some extremely smart people in it. The majority of the speakers focused on pushing mobile first but without forgetting the content. I must admit while Nicole Sullivan while talking about how our best practices are killing us. I felt extremely guilty that some of my “best” CSS is wrong in her books. Guilt wasn’t the only feeling I had during the week, I saw felt a sense of awe.
There is a lot of talk around the web about always have a responsive design for any web project that you create. But one thing we never seem to talk about is how to actually design for this space. So people are doing an amazing job of this like Think Vitamin/Treehouse, Simon Collison to name a few. But what really makes these great and easy to navigate through.
Well it’s the spacing and size of buttons. So often we talk in desktop screens about hierarchy and whitespace around elements, but when we get into our responsive designs all of this can change. We navigate responsive designs differently. We’re using our big thick fingers to click on buttons and navigate information. So then why when we design for these smaller screens do we also make the buttons that much smaller.