The judgment behind the screen — what I treat as the problem, what I decide on, and how those decisions survive as a system.
Hi, I'm Kijoong — a UI/UX designer in Seoul. Before I open a canvas I write the problem down: what isn't working, why it isn't, and which condition has to change for it to resolve. A screen that looks right is the result of that, never the starting point.
Interfaces for apps and services — car sharing inside a single community, vehicle access sold by the day, screens that carry a brand's identity all the way into the product. The surface changes; the job doesn't. I sort out what the user actually has to decide, then turn those decisions into an order of screens.
Every value should be defensible: why this spacing is 24 and not 20, why this button sits here, why this step is gone. Taste is impossible to hand over — the next person cannot follow it. A rule can be followed. So I design the rules that produce the screens, not only the screens.
The shared layer: tokens, type scales, responsive rules — the part several screens depend on at once. Then I build it in code myself to check it, because the holes in a rule only show up once something is actually running.
Ten years on interfaces. ~30 repositories, 440+ commits, one site running in three languages. The numbers are not the point — they mark where the decisions piled up, and every one of them had a reason at the time.