What exactly is a design playground?


A design playground is a small, custom tool you build to answer a specific design question. You create something that lets you manipulate variables and see their outcomes on an interface in real time, so you can view a bunch of variants at once (long text, short text, no text), play with options (big text, bold text, red text), and actually interact with designs.

For example, here's one I use for tuning background animations. Every slider (buoyancy, swirl detail, fade out, and so on) changes the animation live on the canvas.

And here's another for exploring a visual design language and generating brand assets from particle simulations.

So how is this different from a mockup? A playground runs in the same environment your software does: the Web, iOS, Windows, etc. That way you're looking at real font rendering, scrolling, touch and hover behavior, performance, and screen sizes, all things static mockups can only approximate. It can also pull in real content and data, so long names, missing images, and other edge cases get thought about upfront instead of being flagged by developers later. Animation timing, transitions, and loading, empty, and error states all become controls you can adjust and test.

When you're done, the values you settle on can be exported directly as code or design tokens for engineers (or more likely, coding agents) to pick up. No redlines, no "can you make it look like the Figma file?"

If you want to try one yourself, I built a playground for deciding how much of an AI agent's work (reasoning, tool use, delegation, monitoring) to show people in an app's UI. You can try it at https://intentapp.dev/agentwork.

Put simply: if you have a design question with a few variables, build a tool that lets you turn those knobs on the real thing.