Why I Chose to Write Figma Plugins with AI

First, I know that even with AI help, writing a complex tool would still be very difficult. I might get stuck constantly, leading to great frustration and even giving up.
Writing Figma Plugins has several benefits for me:
1. I'm already using Figma, so I'm very familiar with it
I'm familiar with this tool, so I better understand what kind of Plugins can be made and which Plugins are more likely to be achievable.
2. It directly solves my problems
Using AI to code is fun, but ultimately I still hope it can help me solve problems. This has the greatest benefit for me, and I don't need to consider whether there are other target audiences or commercial value.
3. Building a chair is better than building a house
Figma is like a house. If I started using AI to code with the intention of building a Figma, it would be like building a house - difficult and impractical.
But choosing to make a Plugin is like building a chair - simpler and more feasible. I already have a house, which is great, but now I can build a chair I like to make the experience better. Isn't that better?
Moreover, the house already has many functions. Building a chair in this environment can make the overall experience better. But if I build a chair outside the house, the function is the same, but the experience won't be as good as inside the house, because we've lost the environmental advantages the house provides.
Actually, summarizing the three points above:
-
Being familiar with the product allows you to write better product requirements
-
Solving pain points makes AI coding bring real benefits
-
Environment matters - building small tools and features within mature tools or platforms might be more practical (Figma Plugin and Google Apps Script are both good examples)