Each week, new devices appear with varying screen sizes, pixel densities, input types, and more. As developers and designers, we agree to use standards to mark up, style, and program what we create. Browser makers in turn agree to support those standards and set defaults appropriately, so we can hold up our end of the deal. This agreement has never been more important. That’s why it hurts when a device or browser maker does something that goes against our agreement—especially when they’re a very visible and trusted friend of the web like Apple. Peter-Paul Koch, Lyza Danger Gardner, Luke Wroblewski, and Stephanie Rieger explain why Apple’s newest tablet, the iPad Mini, creates a vexing situation for people who are trying to do the right thing and build flexible, multi-device experiences.
More from A List Apart
Business communications benefit from better, tighter delivery—a technique we learned from fairy tales, Anne Gibson reminds us.
The same typefaces crop up everywhere on the web. But why? Jeremiah Shoaf thinks the answer might lie in cognitive biases.
User testing is a necessary part of the design process, not a luxury.
Tim Baxter encourages us to move beyond the “measles of markup” to write rich, semantic HTML and CSS. Only habit is stopping us.
Before you plan the trip, make sure you know who’s coming. Sophia Voychehovski tells us why action-first design is risky business.
Seeing clients as clueless or “difficult” is a red flag—for us. How to turn client confusion into better experiences.
Translate analytics into product paths with narrative structures. New excerpt from Donna Lichaw’s The User’s Journey.
In an excerpt from Design for Real Life, Eric A. Meyer and Sara Wachter-Boettcher discuss designing for stress cases.