There is a gap between Figma and the App Store that nobody has successfully closed. Every designer who has ever shipped a prototype knows exactly what I mean. You spend hours getting it right. The colors, the spacing, every transition mapped out frame by frame. You hand it to someone and they tap on it and... nothing. It doesn't bounce. It doesn't feel like anything, because it isn't. It's a picture of an app. And somewhere between that picture and the real thing, the entire experience you were trying to communicate just disappears.

Play was built to close that gap.

The Gap Nobody Was Closing

The premise was almost offensively simple. What if you could design an app that actually felt like an app, without writing a single line of code? Not a simulation. Not a click-through prototype with hotspots. An actual thing you could hand to someone and they'd hold it and swipe it and not be able to tell the difference.

The key insight was native. Not "native-looking," which is what every design tool was chasing. Actually native. Spring physics that matched UIKit exactly. Haptics that fired when they were supposed to. Scroll behavior that felt like iOS because it was iOS. The bar Play was aiming at wasn't "good enough for a demo." It was "indistinguishable from the real thing."

That's a very different problem than what Figma is solving. Figma is a communication tool. It helps you show people what a thing could look like. Play was trying to make you feel what a thing could feel like. Which sounds like a small distinction until you actually experience the difference, and then it's the only thing that matters.

I joined the team because this felt like the most important unsolved problem in the design tools space. Not the flashiest, not the most talked about, but the one that quietly sits behind every single design review where someone says "it'll feel better when it's built." I was tired of saying that sentence. I wanted to build the tool that made it unnecessary.

Your Users Will Notice Everything

Designing a tool for designers is the scariest thing I've done professionally. I don't say that lightly.

Most of the time when you're designing a product, your users are forgiving in ways you don't even realize. They fill in the gaps. They learn the patterns. They adjust. A slightly off transition, a modal that appears a fraction too slowly, an animation curve that's a tiny bit wrong, most people don't consciously notice any of it. They might feel something is off, but they can't name it, and they move on.

Designers can name it. Every single time. They will clock your easing curve from across the room. They will notice the pixel that's not on the grid. They will feel the scroll inertia and have an opinion about it. Your users, in this case, are the exact people who spend their days thinking about the things you are trying to get right. There is nowhere to hide. Every decision is legible to everyone using the product.

That's terrifying, but it's also clarifying. You can't get away with "good enough." You can't ship something that works and figure out the feel later. The feel IS the product. If a design tool doesn't feel considered, the implicit message is that you don't know what considered feels like, and that's the one thing you absolutely cannot communicate to this audience, lol.

So every interaction we shipped had to pass a different bar than I'd applied anywhere else. Not "does this work?" Not even "does this feel good?" The question was: "would I be embarrassed if a senior designer at a top studio noticed this?" And that question, applied consistently, will absolutely slow you down. But it also forces a level of craft that I think was a big part of why people loved the product the way they did.

What We Got Right

The thing Play got most right was restraint. This is hard to pull off with a design tool, because the instinct is always to add more. More features, more power, more customization. Every user request is a feature request. Every edge case wants a setting. The natural trajectory of any tool is toward complexity.

We pushed against that constantly. The bet was that designers would rather have a smaller set of things that worked beautifully than a large set of things that worked adequately. And that bet paid off every time someone picked up the app and just... started making something. No tutorial. No onboarding friction. The thing just made sense, and what they made felt real.

The canvas was opinionated in ways that some people found limiting and others found freeing. You couldn't do everything. But what you could do, you could do faster than anywhere else, and it felt better when you were done. That's the tradeoff we made, consciously, again and again.

Getting onboarding right was something I thought about a lot. When your product is a design tool and your users are designers, the first impression has to be exceptional in a way that goes beyond standard onboarding logic. It's not just "help the user understand the product." It's "demonstrate, immediately, that the people who built this tool have taste." The first thing someone does in Play has to feel good enough that they trust everything else. You don't get a second chance to make that first impression with this audience.

I think we got there. Not perfectly, nothing ever is, but well enough that people talked about it. And in design tool circles, word of mouth is basically everything.

Then Apple Called

I wasn't part of the team anymore when it happened. Apple acquired Play in early 2026, and I found out the same way most people did. It didn't feel like a surprise when I heard it, though. Not because I saw it coming, but because the fit was so obvious in retrospect.

Apple has spent years trying to lower the barrier to building for their platforms. Swift Playgrounds, the various tutorials, the effort they put into making Xcode marginally less intimidating with every release. The goal has always been the same: more people making things for Apple devices. Play was the most native-feeling solution anyone had shipped to that problem. Not because the team was trying to appeal to Apple, but because they were trying to solve the same problem Apple was, just from the designer's side of the table instead of the developer's.

When a product is already speaking the language of the platform at that level of fidelity, and the platform's owner decides they want to speak that language more clearly, the conversation is going to happen eventually. It was just a matter of time.

The product is offline now. That's a strange thing to sit with. Something you put a lot of yourself into, that people genuinely loved, just gone from the internet one day. No fanfare. A quiet sunset. The design community noticed, and there were a lot of kind words from people who'd built real things with it, which meant more than I expected.

What I Think Happens Next

Here's my honest read, for what it's worth.

Apple is not buying design tools as a hobby. They acquired Play because they want what Play represented: a path from design intent to native feel that doesn't require a developer. The gap I described at the start of this, the one between Figma and the App Store, Apple wants to close it from their end. They want designers to be able to go all the way to something that feels real, without leaving the Apple ecosystem to do it.

The obvious home for this is somewhere in the Xcode or Swift Playgrounds ecosystem, but I'd argue the more interesting version would be a standalone tool that sits between design and development as its own category. Not a prototyping plugin. Not a developer tool with a nicer UI. Something genuinely new that treats the designer as the primary user and lets them get to native-quality output directly.

The bones of that thing exist. They're sitting somewhere in Cupertino right now. Whether Apple ships it as a product or absorbs the technology into something else entirely, I genuinely don't know. But I'd bet money the work that team did shows up somewhere. Things that good tend to find their way back into the world.

And in the meantime, I still think the problem is unsolved. The gap is still there. Someone is going to close it, and whoever does is going to matter a lot. That's maybe the most interesting thing about working on Play: even after the acquisition, after the sunset, after all of it, the original question is still open. What does it look like when design and native feel are the same thing?

I don't know yet. But I'm still thinking about it.