Nano Banana Pro – Simple text-to-image and image editing playground

Hacker News

Share card

Nano Banana Pro – Simple text-to-image and image editing playground

Hi HN, I built a small web app around the new *Nano Banana Pro* image model: https://nanobananaproimg.com It’s a very simple, hosted playground focused on two things: - *Text to Image* – Type a prompt and get a high-quality image. - *Image to Image* – Upload an image and edit it with text instructions (change style, background, lighting, objects, etc.). No local setup, no API keys, no fine-tuning. You just sign up, buy credits, and use the model in the browser. --- ### What you can do on the site - Generate images from text prompts (up to 2000 characters). - Upload an existing image and restyle / edit it. - See cost and remaining credits next to the generator (2 credits = 1 image). - Download the result and use it for social posts, thumbnails, simple marketing visuals, etc. Right now there are three paid annual plans (Starter / Standard / Premium) with different monthly credit amounts. The goal is just to make the pricing predictable and keep the UI minimal so non-technical users can still play with the model. --- ### What this is *not* To be clear: - It’s *not* a fine-tuning / training platform. - It’s *not* a local setup tool. - It’s *not* an official product from the team behind the model. - It’s just an independent wrapper around the Nano Banana Pro image API with a credit system and a clean UI. --- ### Why I built it I’m an indie developer experimenting with small AI SaaS products. Nano Banana Pro launched with strong image capabilities, but most non-technical users don’t want to deal with API docs, SDKs, or dev environments. This project is mainly: - A way to learn how people actually use the model (what prompts, what use cases). - A testbed for pricing / credits and onboarding flows. - A minimal tool for creators who just want “type prompt → get image”. --- ### Feedback I’m looking for - Is the UI/flow clear enough for you? - Does the credit + pricing structure make sense? - What’s missing for your real workflows (e.g. batch generation, history, presets, etc.)? If you have thoughts on the UX, pricing, or landing page copy, I’d love to hear them. Thanks for taking a look!