In 2000, Jason Grigsby got his first mobile phone. He became obsessed with how the world could be a better place if everyone had access to the world’s information in their pockets.
Those mobile dreams hit the hard wall of reality: WAP was crap. So Jason went to work on the web until 2007, when the iPhone made it clear the time was right. He joined forces with the three smartest people he knew and started Cloud Four.
Since co-founding Cloud Four, he has had the good fortune to work on many fantastic projects, including the Obama iPhone App. He is founder and president of Mobile Portland, a local nonprofit dedicated to promoting the mobile community in Portland, Oregon. Jasonis a sought‐after speaker and consultant on mobile. You can find him blogging at cloudfour.com; on his personal site,userfirstweb.com; and on Twitter as @grigs.
So you’ve convinced your organization to implement a responsive design. Now you face the harsh reality that while responsive design consists of three simple techniques, doing responsive design well requires much more than just those three techniques. It requires changing the way you think about design, where design decisions are made, and how your team collaborates. Worse, most responsive designs are built poorly resulting in bloated, slow sites.
In this workshop, we’ll talk about the major hurdles organizations face when moving to responsive design, the key techniques for building performant responsive design, and the importance of mobile first responsive design.
Windows 8. Chromebook Pixel. Ubuntu Phone. These devices shatter another consensual hallucination that we web developers have bought into: mobile = touch and desktop = keyboard and mouse.
We have tablets with keyboards; laptops that become tablets; laptops with touch screens; phones with physical keyboards; and even phones that become desktop computers. Not to mention new forms of input like cameras, voice control and sensors.
One of the core things that responsive design has taught us is that we have to be comfortable with the ambiguity of not knowing what the size of our canvas is going to be. Input has that same ambiguity. It is transient. It is unknowable. Reconciling that understanding from a design and implementation perspective is going to be as big a challenge if not bigger than the one we faced coming to grips with responsive design.
We’ve learned how to respond to screen size. Our next challenge is learning how to adapt to different forms of input.