A: Yes, absolutely! Right now this works best for vibe coding specially if you’re using Figma Make, or can bring your product screens into Figma. You can use our Figma plugin to get actionable feedback on your UI and user flows before you feed those learnings back into your coding workflow.

We’re also expanding our Chrome extension with vibe coders in mind. The goal is to let you get feedback directly on what you’re building in the browser, and give you a clear prompt you can take back to your coding engine to make the changes you want.

So, Figma-based workflows are the strongest fit today, but direct feedback for vibe-coded products is very much on our roadmap and coming soon.

On the models side, our architecture is designed to be multi-LLM, and we continually improve the AI powering the feedback as model capabilities evolve. Since our inputs are primarily visual—product screens and user flows—we evaluate models specifically for multimodal performance. Currently, the SOTA for Floto's use cases are predominantly Gemini models for their strong visual understanding capabilities.