Update issues and the need for better support for creators

Hi ​@youcef khettra — welcome to Figma Forum, and thank you for taking the time to share your experience. I’ve moved your post to our Feedback section so we can better track it and share with the right teams.

I’m sorry for the disruption with your project — that kind of setback is tough. Since your original post was in a reply regarding Figma Make, could you clarify if you were using only Make or other products as well, and whether anything is still blocked? Accessibility and the designer experience are our top priorities, and I’m happy to surface any specific issues with our product team.

Hi ​@Tom Reem , thanks for the reply.

But let me be clear — as someone who’s been programming for 10+ years, I know my code, I know my environments, I know how things are supposed to run. And when I export my code from Figma Make? I see it relies on specific nodes, specific environment variables, specific configuration files — none of which are documented. So the only option is reverse-engineering. That’s not a feature, that’s punishment.

Most people won’t even know how to do that. So why even offer “export your code” if the whole thing is locked to your platform? Is that freedom, or is it exploitation to keep us inside Figma’s hosting?

And let’s not ignore the gaps:

• No GitHub integration (the industry standard).

• Libraries like React Flow don’t even work properly, even outside “pro” features.

• No clear way to split files/containers, which means you end up with monstrous 3k, 4k, even 6k-line files — that’s where the login bugs start.

For me, sure, I can clean up infrastructure, rebuild configs, make it work after export. But most people can’t. And it feels intentionally set up this way.

Please, fix these fundamentals before you talk about raising prices. Otherwise it’s going to be a disaster for the exact people who are putting their hopes into this tool. I’ve spoken with many devs in the community — this isn’t just my frustration. It’s a shared concern. Authentication, third-party integrations, even basic stability… the issues keep repeating.

I want this tool to succeed. We all do. But not if it comes at the expense of the creators who trusted you with their projects.

Thank you for taking the time to lay this out so clearly, ​@youcef khettra. I can hear how much experience you’re bringing to this. Feedback like this — especially around documentation gaps, integration pain points, and code export challenges — is helpful for our product teams as they evaluate priorities. I’ll make sure your perspective gets shared with the right folks on our end.

While I can’t speak to specific roadmap timelines, improvements in areas you mentioned are top of mind. Any product updates will be announced in our release notes: Figma product news & release notes, and our Designer Advocate team will keep sharing resources to help teams get the most out of prompt-to-code — like these tips for using Figma Make: 8 essential tips for using Figma Make.

Thanks again for raising these concerns — your voice (and that of the broader dev community) is critical in helping us shape where the product goes next.