Hi, I'm Matt. Purveyor of Design and Human Interfaces, and building API developer tools at Runscope. Records, trees, and mountains make me tick. I live/work/play in Northern California and I ❤ APIs.

Transitional Interfaces

Design is more than picking colors. This is a good read if you’re unfamiliar with the depth of detail that goes into interface design.

Pixel Perfect Precision by ustwo

While I’ve been steadily moving away from designing detailed static pages in Photoshop and developing my designs with working code, Photoshop and Sketch are still key players in my design stack. The principles in Pixel Perfect Precision by ustwo, now 4 years old, remain relevant.

Often, people ascribe more weight to tangible variables such as crutches, whiteboards and Post-its. It’s much easier to do that than to apply pressure to their pain, in order to grow confident in their creative function. But that’s what organizations need: to trust their own gauge of what matters in a given situation and develop a custom-fit process for problems as they occur.

Jeremy Utley, d.school

By continuously improving the design of [an interface], we make it easier and easier to work with. This is in sharp contrast to what typically happens: little refactoring and a great deal of attention paid to expediently adding new features. If you get into the hygienic habit of refactoring continuously, you’ll find that it is easier to extend and maintain [an interface].

Joshua Kerievsky, Refactoring to Patterns (via Ian Storm Taylor)


A short animation I started on to illustrate API calls connecting to new Runscope Service Regions available across the globe.

A short animation I started on to illustrate API calls connecting to new Runscope Service Regions available across the globe.

Practice, practice, practice.

See the Pen Lukas Bulga’s Profile Card by Matthew Ginnard (@mginnard) on CodePen

I had a hard time sleeping last night, so I built Lukas Bulga’s Profile Menu from dribbble as practice.

My goals were to: 

1. Translate an idea to HTML/CSS as fast as possible (done);
2. Infer states from a static design (done);
3. Review, refactor, and improve the code and cross-browser compliancy (later).

While I get to #3 in the future, I thought I’d share the result as it stands.

One of the biggest flubs that product teams make is confusing designs that look great with designs that actually work well. It’s a simple mistake, but it can have grave consequences: If your product doesn’t work well, no one will even care how it looks, after all.

Braden Kowitz, in his article, “Why good storytelling helps you design great products,” describing the scenario every product and interface designer should face once, and early in their career, to learn that important lesson. It doesn’t matter how pretty it is; you have to provide affordances that allow your customers to do the thing they came to do.

Simply titled, "Buttons"

The task of changing the way people think about computing is in the hands of people like you and me – there’s no establishment preventing progress besides the enforcement of norms by a community.

We are in a stage of stunted development – using computers creatively is still unnecessarily hard, unjustly handicapping people with great ideas but neither time nor the ‘symbol manipulation’ skills currently required to ‘become programmers.’

1 of 42