Designers Aren't Seeing The Potential of Figma MCP

Let's do the comments. So, the comments section is where we take a look at what you guys have had to say on some of our videos and discuss them. And this week is Figma MCP Command AI. Figma released an update to their MCP which allowed you to take the code to a coded website and dump it in a Figma file. Feels like there's an elephant in the room where everyone is fighting for their job already. your vid is a way of saying don't fire devs, fire designers. We can do design now as well as uh prompt coding. And I responded to this one, no, I don't think that's the way to look at it. Devs are not interested like this this update. Devs are not interested in this workflow of taking code into Figma. In fact, there's been a bunch of people who are like, we don't we don't need this. We don't, you know, we're not going to use this and stuff like that. We'll get into it. But I think the the bigger thing is is actually I think this is empowering designers because what was once, you know, um I don't I can't speak for Banana Man 17 here, but guys, there must be projects you've encountered where someone has developed the website first. They've used um Shad CN. They've built a prototype. They've got something working. It's a way of getting that prototype and putting it in to the design to Figma, designing it up and then bringing it back in in there, right? like this is something that's going to happen more and more especially because I'm sorry guys designers uh it's more beneficial that a a company has a working prototype that actually works and does it and shows you're going to do it from a business perspective like so they know what um what the thing's going to do and also can you build it that's one of the biggest uh you know pauses a a company will have is they they worry that you're not going to be able to do it. Funnily enough, I lost a project recently because they didn't think we could design it because we didn't provide them relevant design experience. So, it it kind of works both ways. It's a workflow that's changing and um products that focus on usable prototypes are now just easier to get up using AI and stuff like that. So, I don't I think I don't think it's saying fire designers at all. And with the two-way thing, in fact, let me just scroll down to one of the other comments. Uh, someone says, "No designer will use users because they have to rebuild everything anyway. No components, no variables, no design system." And then this guy, um, it's low 42 412 as a senior designer product engineer with 10 years in the industry doing seven years, uh, seven figures a year. I'm telling you, this is extremely useful. This is someone who's actually doing the industry. And I and I said um I said, "Thank you for this. Hate when people speak for others. That's just my pet peeve. This this MCP is a godsend to that many in the actual industry doing actual work because building a prototype is great. Um it is useful for people. Four or five months ago, I don't know, Figma released this this MCP. It was this wasn't a new tool that they released. It's just a sorry, the word tool is is difficult when you're talking about AI. This isn't a new MCP that they released. It's actually a new tool, a tool call in the MCP. The original one was taking a design and putting it into dev and I just don't think people knew that. So, the primary focus actually was I think someone actually was it on our video? But some Yeah, someone was like, oh, you know, Figma choosing devs over design. It's like no actually the the first implementation of this MCP was taking a design and putting it into and dev. Now they've just added that extra tool call to say take from code and put it into design. So you know again I I I just don't think they knew that that that was a thing that it was already doing. So I think there's a huge misunderstanding here and and it's landed badly on people. I mean, nine times out of ten, especially when it comes to design, I think designers have uh are quite fearful of of AI. They're quick to reject it. Not all, of course. You know, plenty of us, I mean, Kabaza is here. He he loves AI and stuff like that. So, there's always going to be this knee-jerk reaction of just like this is rubbish. This won't work. This is this is crap. So, there is that, but actually there there's a lot that's going on here. The good designers have always been working on strategic stuff and that's so true. But it's just one of it's it's just one of the workflows. We've now introduced a new workflow that we just now need to adjust to as designers need to adjust to and think right now we're not going to get the opportunity to do all that. Let's lean into what this is offering us. Don't um reject it. Embrace it because you're going to you're going to see this more and more. prototypes are going to come to your lap and you're going to be like, "Ah, it's already done." Like, they're already using it. How am I gonna How am I going to work on this piece of Freaking MCP. That's how you're going to work on this piece of So, anyway, um, let us know your thoughts about that. But that was just some of the stuff I've seen on our video and some other people's videos. Just a lot of like not understanding that they they think they're just going to have to rebuild it. It's like, no, you're you've got to adapt to this new workflow. And actually one of the points I made was that you you work in you work more modular, right? You bring things into your design on a modular by modular level rather than just the whole page. So as you would with any wireframe, you have let's say a project section. These are your projects, right? that that section needs to exist no matter what the design is because the wireframe slashworking prototype slashrework websites dictated that this needs a project section. Take just that section, design just that section or you know work on that section. Obviously you've established a new sort of aesthetic and things like that. Then bring it in. You might move it up or down or you might reconfigure it. But again, it's just that it's it's working on it in a more modular way. We need to adapt. We're all doing it. We're all doing it. Devs are are doing it more than anyone, right? And we're embracing it. It's just it it's just the way of the world. So anyway, yeah, let us know what you think. It's always really cool to to listen to people what they have to say and what they have to think. So yeah, let us know what you think down in the comments. This is part of a larger conversation on my show, Command AI, which we stream live every single week. We discuss the news and all things related to AI in the world of design and web. Catch us next week and join in the banter. Command AI.