If Nano Banana Pro actually got thrown into our product dev pipeline, I think the time saved wouldn’t be the few minutes spent drawing—it’d be the back-and-forth rounds between design and product. Back in the day, you’d wait half a day just for a rough prototype sketch. Now, you describe the functional requirements clearly, and within minutes you get three or four different UI concepts.
The team just argues over the images, and efficiency actually goes up. But there’s a catch: what it spits out is concept art, not deliverable assets. Spacing, grids, real copy—none of it lines up properly.
If you try to use it as a high-fidelity prototype, you’ll mess up. It’s best for quickly putting vague ideas on the table so everyone has something to point at and talk about. What’s the bottleneck in your team’s prototyping phase right now—is it the slow drawing, or not knowing what you want?