What do you like best about Miro?
Here’s the rewrite:
I only just got to explore Miro Canvas 26 today, so this is very much a first-impressions take, but honestly it’s been a fun few hours.
The thing that struck me right away: the AI features don’t feel bolted on. That’s rarer than it should be. A lot of tools right now are dropping AI into existing workflows and calling it a day, but here it actually feels like the AI was considered from the start. How people brainstorm, how they make sense of messy ideas, how collaboration actually works when you’re in a room (or a board) together.
I come at this from a UX research and product background, so I’m probably more attuned than most to when something feels designed versus just shipped. And these flows feel designed.
The boards themselves are just… engaging? Even in a review or feedback setting, which can get heavy fast, the structure and interactions make the whole thing feel lighter. That matters more than people give it credit for. Keeping teams genuinely present and involved over long sessions is hard, and good interaction design quietly does a lot of that work.
What I didn’t expect: I kept thinking about personal uses. Career mapping, long-term planning, just getting thoughts out of my head and into something that makes sense. There’s an approachability to it that makes you want to keep going.
Tomas’s keynote was a big part of what got me thinking differently about this. Something about the way he framed where Miro is heading just clicked, and now I want to actually test it. Going forward I’m planning to prototype as much as possible directly in Miro and start building out more autonomous workflows using these tools. Less bouncing between apps, more thinking and building in one place.
Very early days, but I’m genuinely curious to see where this goes with regular use. Review collected by and hosted on G2.com.
What do you dislike about Miro?
Here’s a natural, balanced version that fits the tone of the rest:
Where it gets harder for me to make the switch fully is UI work. For building out full UI workflows and going directly from design to build, Figma is still where I live. There’s something about being able to stay in one place from wireframe to handoff that I haven’t found a reason to move away from. The fewer platforms in that particular process, the better.
So for UX specifically, Figma is still the stronger tool in my opinion. The depth of the UI workflow, the way it handles components and prototyping, the direct path to actually building, it’s hard to compete with that. Miro doesn’t need to be that though, and I don’t think it’s trying to be.
The way I’m starting to think about it is less either/or and more about what each tool is actually good for. Miro for thinking, synthesizing, collaborating and now increasingly for prototyping ideas and building autonomous workflows. Figma for UI design and anything that needs to go somewhere buildable. They serve different moments in the process, and forcing one to do the other’s job usually just creates friction. Review collected by and hosted on G2.com.