"Don’t gloss over any part of your website. Every pixel, every word, every color and every picture matters."
"One of the greatest strength of Web as a platform is the ubiquity of access. A device, no matter how small or big, that ships without a built-in web browser is quickly becoming a thing of the past, a curiosity, a gadget at a severe disadvantage in the fiercely competitive landscape. This landscape is seeing a lot of experimentation in the physical screen size, aspect ratio and pixel density. Designing your structure around a few “well-known” pixel widths of a small subset of popular devices is a losing proposition."
Pushing Pixels (via adactio)
"One of the temptations with the MVP approach is to build a bridge that only goes halfway across a ravine and then to ship it so you can get iterative feedback. The feedback amounts to “this bridge sucks” even if a bridge across a ravine is a brilliant idea. Without the end-to-end experience, the product simply feels broken or nonsensical to the user or, in the case of the bridge, very dangerous."
Figuring out the best way to optimise navigation for mobile devices is downright challenging. Our community has come up with a ton of different approaches for addressing this issue, each with its own set of pros and cons.
— Build a smart mobile navigation without hacks
"If you click a link or type a URL, you should get content you requested. Hopefully it’s optimized for whatever device/browser you have, but at the minimum it’s about basic access. If you click on a link to cute kitties, you should get cute kitties. Even on your phone. Or your iPad. Or your Nook. Or your Google TV. Or Internet Explorer. Or your Galaxy Note (*shudder*). Or your Blackberry. Or your Chumby."
— Brad Frost, Content Parity
"Sadly, instead of trying to DISCOVER which choice of tablet is right for us (or for those whom we are advising), these discussion always degenerate into battles where we DEFEND the choices that we have already made."
— FalKirk in a comment on iPads Vs. Android: 3-Way Tablet Shootout in InformationWeek
"[C]hoosing responsiveness, as a characteristic shouldn’t necessarily define the wider implementation approach. Device Experiences (i.e. standalone sites, aimed at a group of devices) can also be responsive, providing the flexibility to support a much wider range of devices. While this on the one hand seems obvious, far too many sites still design either a single width or generically stretchy web site."
— Stephanie Rieger in Responsiveness is a characteristic
Cathy Davidson has been arguing recently that we should teach a 4th ‘R’, algorithms, on par with literacy and math. To my delight, what she talks about is not just teaching existing algorithms to kids (“first we’re gonna memorize bubble sort, then on to merge sort“), but rather teaching them how to think about the world algorithmically.
The distinction is an important one. As Cathy says: Algorithmic thinking is less about “learning code” than “learning to code.”
— Teaching Algorithmic Thinking