ServicesProduct design
Discovery, structure, user flows, wireframes, prototypes, and the finished interface. We work out what the product needs to do and how people will move through it, then design every screen and state, so whoever builds it isn’t guessing.
Opened before it expires?
Yes
No
What we do
The expensive mistakes in a product are usually made early, in what it does and how it’s organized, long before anyone picks a color. So that’s where we start.
Structure
Who it’s for, what they’re trying to get done, what they use today, and the constraints you’re really working under. If what you asked for won’t solve the problem, we’ll say so.
What the product needs to do and, just as important, what it doesn’t. The content, the things people work with, and how they relate, before there are any screens.
Wireframe
The paths people take to get something done, including the unhappy ones: errors, empty states, permissions, and coming back tomorrow to finish.
Plain layouts that settle hierarchy and placement while changes are still cheap to make.
Prototype
Clickable prototypes you can try on your own phone or laptop, so decisions get made by using the thing.
Phones get layouts of their own. Contrast, type size, focus, and touch targets are designed in from the first screen.
Interface
Typography, color, spacing, and motion for every screen and state, in light and dark when the product needs both.
Specs, components, and every state, ready for whoever builds it. Often that’s us, which keeps the design honest about what’s practical.
Proof
Every screen in a shipped product is a stack of decisions. Here are a few from two of our iPhone apps, and the reasons behind them.
iPhone app
iPhone app
Interface design
Once the structure holds, the interface gets the same attention. These measurements come from the live Burn After site.
Design systems
A design system turns one-off screens into reusable decisions, so the hundredth page looks like it belongs with the first. Small products often need just a handful of shared styles. We size it to the product.
This page’s colors and type styles start from tokens like these, in both themes.
Open source
A generator for style guides and documentation sites.
We built it so a design system’s documentation can hold the live components themselves, right next to the guidance for using them.
Read the case study: MDX Docsmdxdocs.com (opens in a new tab)
Good fit
And when you want it built too, we do that as well: websites, web apps, and iPhone and Mac apps.
From the blog
Good design does more than look good. It reduces the amount of mental effort required to understand what is happening, decide what to do next, and get something done.
Quiet Mind is not about minimalism or a particular design style. It is about the confidence that comes from knowing the work is handled.
Before you ask
Both. Most of what we design, we also build, which keeps the design honest about what’s practical. If you have developers of your own, we’ll hand off designs they can build from.
Whatever the build needs: flows, wireframes, a clickable prototype, finished designs for every screen, state, and size, and a component library or design system if the product calls for one.
Not always. It pays off when several people build screens over time, or when the product is big. A small site may only need a few shared styles, and we’ll tell you which you are.
Yes. We start by learning how it works today and where people struggle, then change what needs changing. If someone else built it, taking over existing software covers how we get to know it.
From the first screen: contrast, type size, focus states, touch targets, and reading order are part of the design. That’s much easier than fixing them after launch.
Contact
Tell us about the product and the people it’s for. We’ll get back to you as soon as possible.