Designing an AI studio
for collaborative prototyping.

01 / THE OPPORTUNITY

Shorten the distance
between an idea and a decision.

A design is easier to discuss when people can experience it. But turning an idea into a working flow often means moving between briefs, design tools, code, and scattered feedback.

I created Phluffle to bring that work together: start with a prompt or an existing screen, generate a multi-screen prototype, and keep refining it in the same workspace. The audience includes designers and engineers exploring alternatives, founders making an idea tangible, and teams reviewing work together.

02 / THE EXPERIENCE

Give people visibility.
Keep them in control.

Show the work as it happens.

Generation reveals the plan, progress, and emerging screens. People can follow what is happening and stop the process instead of waiting behind an unexplained spinner.

Change the part that needs changing.

Users can select a screen or element and describe an edit. Targeted regeneration supports focused iteration while preserving the surrounding design.

Keep feedback attached to the work.

Shared workspaces, presence, live cursors, and pinned comments bring collaborators into the same context. A multi-screen canvas makes the broader flow visible.

03 / USED IN MY OWN PRACTICE

Build with it.
Keep learning from it.

I designed and iterated CandyBark, OneTapJobs, and GigSchedule in Phluffle. Using the studio across commerce, job search, and scheduling keeps the work connected to different product needs.

Those projects make Phluffle part of my own design practice: a place to explore screens, refine flows, and move ideas toward implementation.

04 / DELIVERY & RELEASE JUDGMENT

Built end to end.
Released deliberately.

My ownership spans product strategy, interface design, the design system, AI behavior, engineering, and release review. I work with AI coding agents while retaining responsibility for direction, evaluation, and the resulting experience.

The platform is built and operational. Advanced capabilities—including exports, GitHub integration, and Live Deploy—are implemented and undergoing reliability testing before public access. Availability is being phased in.

Speed makes iteration possible. Reliability determines when the experience is ready for more people.

THE PUBLIC EXPERIENCE

A clear invitation
to start making.

The landing page introduces the core promise, offers a prompt or screen import as a starting point, and shows how the studio supports ongoing iteration.