01
learn more about
me personally
Don't navigate my portfolio. Ask it.
Most portfolios make the visitor do the retrieval. You land on a wall of projects, open a few, and try to figure out which one answers the question you actually came with.
I wanted to reverse that.
Ask what you want to know, and the portfolio brings back both the answer and the work that supports it. The conversation gives you the story. The artifacts beside it give you the evidence.
Try a question ↓
frieda ✦
I don't use it to make pictures faster. I use it to hold the flow, the edge cases and the states on one canvas — so I built the tool that does it.
why these → she builds the tools she wishes existed, in code, and uses them on real work
Four of the questions people actually ask.
02
context, gathered
in one place
Design work doesn't fit down a single column.
The first version of this portfolio was a chat window.
A thread is optimized for turn-taking: one question, one answer, then the next. But design work depends on relationships. You want the previous screen beside the next one. The prototype beside the explanation. It's how designers naturally build visual context and connect the dots.
So I stopped treating the conversation as the interface. On the canvas, every exchange becomes an object in a shared space. Answers, screens, prototypes, and the questions that surfaced them stay visible together. You can pan across the thinking instead of reconstructing it from a transcript.
v1 — a chat window
now — the canvas