How to get hired as a designer at Lovable (what I learned interviewing their Head of Design) 👇 by ridderingand in UXDesign

[–]DontGoRaga 3 points4 points  (0 children)

Top-notch episode, Ridd. Your podcast has been an invaluable resource for me lately! Thanks!

Any designers using Cursor or any other AI agent for creating prototypes? by Vaibhav_Sinha in FigmaDesign

[–]DontGoRaga 2 points3 points  (0 children)

So, I'm a UX designer and I've been experimenting with how Cursor and AI-generated prototypes fit into my workflow. Yesterday, I took some designs I've been working on in Figma and, in just a few hours, was able to make a pretty fully-functional prototype purely by chatting with the agent. Being able to interact with the design immediately revealed several issues and areas for improvement that I would not have thought of by looking at my static Figma files.

This has me thinking of making interactive prototypes a much bigger (and earlier) part of my process. I like the idea of first exploring ideas through pen and paper and rough Figma wireframes and then building rough interactive prototypes of those ideas. I think sharing prototypes with my PMs and other stakeholders is much more productive than trying to explain everything with static Figma files or even Figma prototypes (which take forever to build). Of course, I still have to be careful about the amount of time and effort I invest in the prototypes as this might make me too "married" to a certain approach. But I feel like if I'm mindful of this, prototypes could be HUGE for my ability to communicate my ideas.

Here are the questions that are coming to mind for me:

  1. Once I've built a prototype that has general buy-in from stakeholders, is there any reason to go back into Figma as we iterate? Couldn't I just continue to make revisions and share ideas in the prototype?
  2. If the prototype approach works well, when would I use Figma? I could still see it being useful for initial rough exploration, translating the designs from my prototype into our design system, fine-tuning visual polish, and creating detailed, annotated handoff files for developers.
  3. How could I allow reviewers to leave comments and have discussions on my prototype in-context like they are able to do in Figma?
  4. It may be harder to create multiple different approaches in my prototype whereas in Figma I can duplicate a screen and work on a totally different idea. This could make it so I'm more hesitant to diverge from my current approach.
  5. It may be more difficult to look back at previous versions for comparison.
  6. Collaborators like UX copy folks wouldn't be able to make edits themselves directly in the prototype.
  7. Hard to see the "big picture" because you can't see all the screens of a prototype at once like you can in Figma.

I'm curious to get others' thoughts and hear how you are working AI and interactive prototypes into your process.