On 1st December 2015 Transport for London (TfL) unveiled its new design bible, the Design Idiom. Though the name may sound grandiose, the goal is simple: create a document that captures the design aesthetic of the Underground, so that good design can help drive decision-making at London Underground.
The document itself can be found here (PDF), and I whole-heartedly recommend reading through every part it. It’s an excellent example of a set of design guidelines that isn’t touchy-feely and alight with cockamamie buzzwords. Instead, it is the product of proper research that provides concrete examples of how to implement each high-level concept. In essence, it explains why the guidelines matter.
The article is great, too.
Wraith uses either PhantomJS, CasperJS or SlimerJS to create screen-shots of webpages on different environments and then creates a diff of the two images, the affected areas are highlighted in blue.
Made by the BBC News dev team.
A great piece on the unification of Google’s design process. I disagree with the title, though. I define good design (in the context of software) as UIs and accompanying UXs that are intuitive and easy to grasp for as many users as possible. Save for maybe Google+, I’ve never noticed a significant amount of uproar regarding older Google UIs/UXs. They were pretty good; it’s not like Google didn’t “get” design before Material Design.
Fontstand is a Mac OS X app that allows you to try fonts for free or rent them by the month for desktop use for just a fraction of the regular price. One-click font activation for all your OS X apps.
This is a really great concept. A few more foundries would be nice, but it’s early days yet.
As we refine our methods of responsive web design, we’ve increasingly focused on measure (another word for “line length”) and its relationship to how people read.
Sound advice, although I must admit I don’t follow the “max 75 characters per line” rule religiously.