Image for post
Image for post

Just a heads up, I’m going to start this post off with a personal story. If you’re not interested and just want to learn more about the product we are working on, please feel free to jump forward. 😄

In 2013, after years of waiting, I won the lottery. Well, not the lottery, lottery. But the season ticket waitlist lottery. Finally, I received the opportunity to purchase tickets for the upcoming Chicago Bulls season.

Having just come off of a Derrick Rose-less second-round playoff loss the previous season to Lebron James and his Miami Heat, I couldn’t have been more excited. The Bulls would be getting their MVP back and were primed for a deep playoff run. …


Sure.

Why not?

I have wrestled with how to answer this question for a year or so now. At first, I was a hard no. As a designer at a digital agency I thought it felt cheap, lazy, and a misuse of a client’s trust to re-use components, modules and page styles between projects. I felt, pretty strongly, that each project should have its own unique experience and this experience started with a custom design system.

While this statement holds some truth, I’ve come to realize that it’s not about the style of interface elements on the page, but rather how those interface elements get a user from point A to point B that crafts the unique experience each project demands. …


As a front-end designer at a service-oriented development firm it can be hard to maintain a design to code work flow that is both efficient and practical. While there are more tools and plugins than ever at our disposal, there are also more tools and plugins than ever.

At Made by Munsters, our design team is proficient in both standard web design tools as well as front-end development — HTML, CSS (Sass) and basic JavaScript. They are responsible for turning their component-first, modular web application designs into actual code.

But similar to other designers in our position, our team struggles with maintainability and consistency. The work flow of turning static designs into responsive web components is tough. Type sizes are forced to change based on content overflow issues, viewport sizes cause well-defined design components to break, and spacing is never correct (no matter how hard we try). This puts our designers in a precarious position. To what extent should their design elements match the product’s font-end components? Moreover, how much time should be invested into creating pixel perfect parity? …

About

Kurt Cunningham

Product Designer & Developer | Made by Munsters | College Football Enthusiast | Native of Iowa | Destroyer of Taco Bell

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store