Not surprising it can get it to parity for a casual user. One thing I find though is that a lot of the vibecloned apps miss or ignore power user features or implement edge case features incorrectly. This was very, very true of the artcraft clones - as soon as you get to the more advanced things, they start to fall apart.
For a lot of the Figma code, there are SO many gotchyas in there, that while I'd be curious to try it, I don't think agents would be able to derive the why, and thus would attempt to optimize the implementation leading to incorrect usage. I led the variables workstream at Figma, and it still is the most complex thing I've worked on in my 20 years of tech. The amount of edge cases / conditionals / exceptions in it are staggering, just to get it to a point where it seems like it's "simple" (for a power users' definition of simple).
One other thing to consider though is the value of something like Figma isn't the functionality so much as the multiplayer platform aspect. This is toats fine if you're just doing solo work, but the collab aspect means you have to fight against the social network dynamics, which also can't be vibe coded.
I think agents can absolutely write the default path correctly and it will work most of the time and seem to be feature complete. But I don't see how they will quickly handle all those dozens of edge cases.
Over time it can happen - each time a case fails, send it to an agent and have it implement the conditional case. But that will take a long time. There is a reason most solid CAD kernels are decades old - they have been battle hardened and just handle all those edge cases better than other kernels.
And yes, this will multiply the time, and the cost.
But as a user if you can identify the exact requirements you need your software to do, then it's very possible to vibe code a solution to do exactly what you're looking for. And your own offering doesn't need to be as complex, and can be tightly coupled to the other infrastructure you have.
Very curious if you try it and tell us how far it is from real figma
I wish there was a more standardized way of sharing these prompts, results and token usage.
You can try mana, curious how it compares to your previous experiences. You can sign up here if you like: https://mana.space/invite/MANA-NPNV
This is an impressive result but I think you could go a step further and really sell where the secret sauce lives in your product. Devs need a strong mental model of what they are getting and what problem is being solved - Jev did a good job at this and I think your writeup is quite good but those tasty details could go a long way.
I would rather have a standardized way of comparing these things like a list of prompts, code outputted and tokens used. I'm wasting way too much time trying to even get to a point to compare these tools.
I'm pretty sure figma clone cannot be done in 8k lines. Are you only cloned part of the logic?
Can Mana clone Mana yet?
I think it's less about the code and more about the functionality. I didn't guide the llm to add features etc. I just told it don't stop until it's feature complete. Even 2 months ago I'd have to hand hold it a lot with UX and detailed features.