Portfolio / 2025

MAIK
skills & practice

A UX designer working at the intersection of productivity tools and cultural history. Minimal interfaces, careful typography, and a quiet preference for things that just work.

Role
UX Designer
Focus
Tools & Research
Based
Remote / EU
01 / About

A designer who likes reading footnotes and shipping tools.

I'm MAIK, a UX designer with a soft spot for productivity software and cultural history projects. Most of my work sits where those two worlds meet: interfaces that help people do focused work, and reading experiences that respect the source material.

My approach is Swiss-influenced and restrained. I build with grids, hairlines, and type, not decoration. I care about consistency, accessibility, and interfaces that feel calm even when the task underneath is complicated.

I work mostly in Figma and Sketch, and I prototype in code when a static frame won't tell the whole story. Lately I've been interested in subtle sound feedback, circular timers with alternating cycles, and inline citations that expand to show their source.

02 / Skills

What I bring to a project.

Six areas I keep sharp. The first three are where I'm most useful in a sprint; the last three are where I'm happiest spending a quiet afternoon.

01

Interaction Design

Flows, states, and transitions that make a tool feel predictable. I prototype interactions early, usually in code, because a static frame hides the hard parts.

FlowsStatesMotion
02

Design Systems

Tokens, components, and documentation that a team can actually maintain. I prefer a small system used consistently over a large one used loosely.

TokensComponentsDocs
03

Typography

Type scales, reading measure, hierarchy, and inline citations that expand on tap. Beautiful reading is functional, not decorative.

HierarchyScaleReadability
04

Accessibility

Keyboard-first flows, visible focus, ARIA where it earns its place, and contrast that holds up. Accessible interfaces are better interfaces for everyone.

KeyboardARIAContrast
05

Prototyping

Clickable frames get you so far. I build working prototypes - timers, dials, forms with validation - to test whether an idea survives contact with real input.

FigmaCodeTesting
06

Research

Interviews, competitive scans, and plain-language synthesis. I write findings as short documents with clear next steps, not slide decks.

InterviewsSynthesisWriting
Figma95
Sketch88
HTML / CSS82
Prototyping90
03 / Process

How I usually work.

01
Listen
Understand the problem, the people, and what's already been tried. Read everything before drawing anything.
Brief, notes
02
Sketch
Low-fidelity flows on paper or in Figma. Cheap frames, fast decisions, throw most of them away.
Wireframes
03
Build
High-fidelity components and a working prototype. Test with real input, not just a click-through.
Prototype
04
Refine
Polish type, spacing, and states. Document the system so someone else can maintain it without guessing.
Handoff
04 / Contact

Let's talk.

Working on a productivity tool, a reading experience, or something with a bit of cultural history in it? I'd like to hear about it.

Project brief

Send a message

Please enter your name.
Please enter a valid email.
Tell me a little about the project.

I usually reply within two working days. No newsletters, no follow-ups unless you ask.

Message sent.

Thanks, there. I'll get back to you shortly at the address you provided.

MAIK.