My projects cover a lot of ground: websites, identities, apparel, live broadcasts, interactive experiences, physical products, and software. Working on this portfolio has given me a reason to look at them together. A recurring interest has become clearer: I like making things, and I like improving the tools that help people make things.
That second part is becoming a larger part of my work.
Creative projects often come with a surprising amount of coordination. A conversation lives in one app, the files in another, and the useful reference somewhere in a browser tab. Before you can do the next piece of work, you have to find the right material and remember how it all fits together. Each tool might do its own job well, but moving between them becomes a job of its own.
That is the kind of software bloat I’m interested in reducing. Overlapping features are part of it. So are repeated setup, duplicated information, and interfaces that require more attention than the task deserves. I want to build tools around a coherent activity and keep the things that belong together close enough to be useful.
Newton is one version of that idea. I’m building a desktop workspace for persistent AI teammates, bringing projects, conversations, roles, and recurring work into one place. It connects tools such as Codex CLI and Claude Code within a shared workspace. The design question is how to make that work easier to return to: what was happening, who was handling it, and what needs attention next? Keeping that context available is a big part of what I want Newton to do well.
Current approaches the same problem on a much shorter timescale. It’s a live rhyme studio that connects spoken or typed words with rhyme suggestions, related sounds, and phrase ideas. When you’re working on a line, a useful suggestion has a very small window to be helpful. I’m exploring how to keep those suggestions nearby while leaving room for the person using it to follow their own train of thought. The rhyme log, audio, and transcript tools also give the session somewhere to go afterward.
Vispix comes from another familiar part of creative work: choosing images. A photo library becomes more useful when you can search it, review options with a team, understand usage rights, and build a shortlist in the same place. Vispix brings those activities together. Its connection to AI tools extends access to the existing library, so the photos and their information can be useful within other workflows too.
These projects share a design challenge. Every additional feature has to earn the space it takes up. Putting five disconnected tools inside one window would still leave a lot of coordination to the user. The useful work is deciding what should share context, what should happen automatically, and what needs a clear human decision. A focused tool needs boundaries, and maintaining those boundaries is part of building it.
I can trace that interest through my earlier work as well. Producing live broadcasts for USA Archery involves graphics, scoring data, audio, video, and on-site production. I’ve built custom software to support that process and connect real-time scoring to the broadcast. In that setting, an interface has to make sense while an event is happening. The visual design and the underlying system have to work together under the same constraints.
PlayCase brings the question into the physical world. It adds real controls to an iPhone for playing classic games, with swappable faceplates for different button layouts. The work spans industrial design, prototyping, production, and the way the product is presented. It’s another example of how much the experience can change when you reconsider the interface between a person and something they already use.
There’s also room for exploration. With Arcadia, I’m investigating how an AI workspace and a simulated world might relate to each other—how software activity could become something you can see and navigate as a place. That gives me room to think about character, presence, and play alongside practical questions about coordination.
Newton and Current are still in active development, and Arcadia is an ongoing experiment. I’m working through where consolidation helps and where a tool should stay small. Building the software creates its own maintenance work, so reducing friction has to remain something I evaluate, rather than something I assume.
This is where creative work and technology meet for me. Understanding the activity helps me shape the interface; building the system lets me test whether that design actually helps. Across these projects, I want to make it easier to stay with an idea, find what it needs, and carry it through to something finished.