Jayesh W.
JW
Software Engineer II
Computer Software
Enterprise (> 1000 emp.)
"Turning Product Requirements into Usable UI Flows with Galileo AI"
4/5
What do you like best about Galileo AI?

I found it strongest during the early UI exploration stage, where a written product requirement could quickly become something concrete enough to evaluate. For a rider-support mobile concept, I started with the overall support journey and generated screens for trip overview, issue reporting, request review, and request status.

What stood out was the iteration workflow. Instead of rebuilding screens whenever the direction changed, I could ask for focused changes to hierarchy, actions, spacing, or consistency and review the updated flow visually. That made it practical for exploring how a multi-step experience should work before spending time implementing the interface. Review collected by and hosted on G2.com.

What do you dislike about Galileo AI?

Detailed screens still need careful review after generation. In a support flow with status cards, forms, maps, navigation, and several actions, some generated elements contained more information than the screen really needed or gave secondary details too much visual weight.

More precise prompts improved the result, but I would still treat the generated interface as a strong design starting point rather than something ready to move directly into implementation. Review collected by and hosted on G2.com.

See what 45 reviewers think of Galileo AI

4.3 out of 5 · Verified reviews from real users

Read all reviews