Interface design
Screens and flows for web apps. Drawn and built by the same person, so nothing gets lost between the file and the browser.
UX Design · Colorado Springs, CO
UX design
Interfaces you do not have to think about.
I design the interface and I build it, so the decision and the code are the same piece of work. Most of it comes down to two things I care about a lot: a design system your team will actually use, and finding out where people really look instead of guessing.
- 2002
- Building the web since
- HEC
- MicroMaster in UX Design
How the pieces fit
One set of parts, used everywhere.
A design system is not a folder of components. It is a short list of decisions that everything else inherits. Spacing, type scale, color, how deep a shadow is allowed to go, what a disabled thing looks like.
I build them as tokens first. One value for page padding, one for the content column, one for the rhythm of a section. Change the token and the whole site moves together. Hardcode it once and you spend the next year hunting for the copies.
This site runs on that idea. Every section on every page shares the same width, the same padding and the same left edge, because they all read from the same handful of variables.
- Page padding
- One value, every section
- Content column
- One width, every page
- Type scale
- Display, body, label
- Color
- Black, white, grey
A tool I built
Where people actually look.
Opinions about layouts are cheap and I have plenty of my own. I got tired of arguing about what draws the eye, so I built something to measure it instead.
It crawls a set of pages, renders them the way a browser would, and records where attention goes across a session. The output is not a heatmap poster for the wall. It is a list of which elements got looked at, in what order, and which ones were skipped entirely.
What it changed most is the order of things. Plenty of times the headline everyone argued over was fine, and the real problem was that nothing led the eye from it to the next step. That is a layout fix, not a copy fix, and you only see it when you measure.
It is a working tool, not a product. I use it on my own builds, and on client work when a page is not doing well and nobody can say why. Building it taught me more than reading about it ever did.
- 01
Crawl and render
It renders each page properly, not just the HTML, so what gets measured is what people actually see.
- 02
Record
Where attention lands, and in what order.
- 03
Change one thing
Fix the order, move the action, cut the step. Then measure again. One change at a time or you learn nothing.
What working together looks like
Design that ships.
Design systems
Tokens, components and the rules that hold them together, documented well enough that someone else can pick it up.
Attention audits
Run the eye tracking tool over your pages and get a plain list of what people look at and what they miss.
Front end build
Nuxt and Vue, server rendered, accessible, and fast enough that speed never becomes the next project.
Got something that is not working?
Send me the page and tell me what it is meant to do. I will tell you what I think is getting in the way, and whether it is worth paying anyone to fix it.
Start a projectConnect
Let's work
together.
Whether you need a full project scoped and estimated, or just want to start a conversation. Pick your path.
If you have something you're working on, whether it's a new project, something that needs fixing, or just an early idea. Feel free to reach out. No pressure, no sales pitch.