Banana Image Editor: What workflows and features do you want next?

I’m building Banana Image Editor (Banana Editor), a Gemini 3.0 Pro (Nano Banana Pro) powered photo editor focused on granular inpainting and prompt-driven control. I’d love to learn how you’d use it in real projects and what would make it a daily tool for you.

Questions for you:

• What’s your main use case: ecommerce product shots, portraits, interiors, marketing creatives, or storyboards?

• Which edit types matter most: background swap, wardrobe/prop swap, relighting, identity lock, or scene extension?

• How important is “permanent links / cloud history” for generated images versus quick temporary previews?

• Do you prefer “generate first, then save” (faster) or “save before showing results” (more reliable)?

• What output formats do you need most (PNG/JPG/WebP), and do you need original + edited comparisons exported together?

• What would be a fair credit/pricing model for you (e.g., per edit, per batch, team usage)?

• Any integrations you’d want (e.g., API, Zapier, Figma, Shopify, Google Drive)?

If you share a sample workflow (inputs, constraints, and what “success” looks like), I can prioritize and ship improvements quickly.