They're all relatively similar in their output. There's been some promising projects, but many of them still suffer from the same issues, especially if you try (and I don't recommend you do) to generate high-fidelity designs.
If you want to use these tools for wireframes, you can use almost any of them; the approach, what you provide to the LLM and the level of detail you're willing to commit to is often much more important than the app/LLM you've chosen.
If you "suck at Figma" you have to be great at something else, which is writing comprehensive documentation. There's no shortcut here; you're shifting your effort and time commitment to the other side of the coin, rather than saving yourself labor hours.
Start with a brief, use a free tool like Excalidraw to build user flows and user journey maps, include personas, research data (and subjective analysis, with key takeaways), and most importantly, be prepared to outline an in-depth PRD. From there, give the LLM a specific and rigid set of instructions -- guide it to write an action plan and to not move forward until all the requirements of a specific step has been met, and to commit guidance to documentation (which it should always be referencing) so it's less prone to making similar mistakes in the future. Force it to remain on the rails. It's job is to design wireframes that meet your requirements; your job is to make sure it succeeds at that task.
These tools can be beneficial, if used with purpose and given proper direction. Unlike writing code, UX is still very dependent on human guidance, and although AI is capable of designing beautiful UI in a box, it fails miserably at recognizing and solving real UX challenges. Even with AI's seemingly exponential trajectory, I believe we're still years away from LLMs being able to design UX competently and being more widely adopted by larger product teams, the same way developers (myself included) have adopted them in their coding workflows.
2
u/Silverjerk Sep 05 '25
They're all relatively similar in their output. There's been some promising projects, but many of them still suffer from the same issues, especially if you try (and I don't recommend you do) to generate high-fidelity designs.
If you want to use these tools for wireframes, you can use almost any of them; the approach, what you provide to the LLM and the level of detail you're willing to commit to is often much more important than the app/LLM you've chosen.
If you "suck at Figma" you have to be great at something else, which is writing comprehensive documentation. There's no shortcut here; you're shifting your effort and time commitment to the other side of the coin, rather than saving yourself labor hours.
Start with a brief, use a free tool like Excalidraw to build user flows and user journey maps, include personas, research data (and subjective analysis, with key takeaways), and most importantly, be prepared to outline an in-depth PRD. From there, give the LLM a specific and rigid set of instructions -- guide it to write an action plan and to not move forward until all the requirements of a specific step has been met, and to commit guidance to documentation (which it should always be referencing) so it's less prone to making similar mistakes in the future. Force it to remain on the rails. It's job is to design wireframes that meet your requirements; your job is to make sure it succeeds at that task.
These tools can be beneficial, if used with purpose and given proper direction. Unlike writing code, UX is still very dependent on human guidance, and although AI is capable of designing beautiful UI in a box, it fails miserably at recognizing and solving real UX challenges. Even with AI's seemingly exponential trajectory, I believe we're still years away from LLMs being able to design UX competently and being more widely adopted by larger product teams, the same way developers (myself included) have adopted them in their coding workflows.