Has anyone else seen the rumors about Figma building their own app creation platform? From what I’ve heard, it’s supposed to let you design responsive layouts, use ready-made components, add interactions, and publish everything with one click.
Apparently it’s going to be AI-powered and can take text descriptions, existing Figma designs, or images as starting points. The AI part runs on Claude through Supabase.
I’m curious what everyone thinks about this direction. It seems like a pretty aggressive move since they’re going head-to-head with tools like Webflow and Framer that already let you import Figma files.
A few things I’m wondering about:
Will we be able to export our projects or are we stuck hosting on Figma?
Is this going to cost extra on top of current subscriptions?
Are they trying to do too much at once?
Part of me thinks this makes sense because lots of people are already jumping straight to Framer instead of prototyping in Figma first. But I also wonder if they should focus on fixing their existing prototype features instead of building something completely new.
What do you all think? Is this the natural next step or are they losing focus on what made them good in the first place?
I’ve dealt with this workflow nightmare at enterprise scale. The issue isn’t Figma building another website builder - everyone’s trying to solve this with platforms that lock you in.
Here’s what nobody mentions about AI code generation: it works great for demos but breaks when you need real integrations. Your client wants Salesforce sync, custom analytics, payment processing, or multi-language support. Now you’re stuck with AI-generated code you can’t modify.
I solved this completely different. Instead of waiting for Figma to maybe build something decent, I automated the entire pipeline with Latenode. Pull designs from Figma API, extract components and specs, generate clean code templates, push to any platform I want.
The killer advantage? I control every step. Need custom business logic? Add it. Client wants specific hosting? No problem. Design changes? Everything updates automatically without breaking custom code.
I built workflows that handle the full cycle - design updates trigger code generation, run tests, deploy to staging, notify the team. Works with any stack, any hosting, any CMS. No vendor lock-in.
Why bet on Figma building the perfect solution when you can automate exactly what you need today?
I’ve worked with enterprise teams for years, and this could actually fix a huge problem nobody talks about. It’s not just the design handoff - it’s version control and collaboration. We design in Figma, build in Webflow or Framer, and lose our single source of truth. Designers keep tweaking Figma while devs build elsewhere. Everything goes out of sync. I’ve seen final products that look nothing like the original design because of this mess. If Figma can keep design and development connected throughout, that’s genuinely valuable. The AI stuff is flashy, but the real win is keeping everything tied together. That said, I’m skeptical about execution. Publishing websites isn’t just pretty interfaces - you need SEO, performance optimization, custom domains, integrations. These are complex backend challenges Figma’s never touched. They could easily build something that works for simple landing pages but breaks on anything serious.
Not surprised at all - this was bound to happen given how design workflows are changing. I’ve used Figma for years and there’s always been this annoying gap between making beautiful designs and actually getting them live. Right now I’m stuck exporting assets, handing off specs to devs, or dealing with third-party plugins that barely work.
The timing’s smart too. Adobe’s acquisition spooked everyone, and competitors like Framer are crushing it with that seamless design-to-web flow. Figma’s got a huge user base and tons of existing design files - if they can create a truly integrated experience, they’ll own this space.
My worry isn’t whether they should do it, but whether they can pull it off technically. Building a solid web publishing platform is completely different from design tools. They’ll need performance, SEO, and hosting that matches Webflow, which has been perfecting this stuff for years.
If they rush out something half-baked with crappy output or limited customization, they’ll piss off both designers and developers. That’s a risk they can’t afford.
Makes total business sense for Figma, but I’m worried about the timeline. I’ve been through tons of design-to-dev cycles, and the real problem isn’t just handoff - it’s that most designers don’t get web constraints. Figma crushed it because they solved one thing really well. Now they’re jumping into hosting, CDN management, databases, and responsive behavior. That’s completely different territory. Webflow spent years getting their generated code production-ready. The AI part sounds cool but also sketchy. I’ve tried various AI code tools and they all spit out bloated mess that looks decent at first but becomes impossible to maintain or customize. If Figma locks you into their ecosystem with crappy code you can’t export, designers will hit walls the moment clients want anything beyond basic stuff. I bet they’ll demo something flashy that can’t handle real projects. Success depends on whether they give you proper code access and exports from launch.
figma’s getting way too greedy. they already own the design tool space - why are they trying to take over everyone else’s territory? webflow and framer have spent years building their platforms, and now figma thinks they can just show up with some ai and compete? they should focus on making figma better instead of spreading themselves this thin.
This feels like reinventing the wheel when better solutions already exist.
I’ve hit this exact problem multiple times. You design something beautiful in Figma, then spend weeks making it work in reality. The handoff process sucks, and even tools like Framer still require tons of manual work.
After dealing with this headache for years, here’s what I learned: stop waiting for Figma to maybe solve this someday. I started automating everything with Latenode. You can build triggers that grab your Figma designs through their API, process the data, and push it straight to your hosting platform or CMS.
Best part? You’re not locked into anyone’s ecosystem. Your designs can go anywhere - Webflow, WordPress, custom apps, whatever. You can add your own business logic, connect databases, send team notifications when designs are ready.
I built one workflow that takes Figma updates and automatically generates responsive code, optimizes images, and deploys to staging. Took a weekend to build and saves hours every week.
Why wait for Figma to build something that might not fit your needs? You can solve this today with proper automation.