DEV Community: Leo Xm

nanobanana pro: The Etiquette and Ethics of Client Work

Leo Xm — Wed, 30 Sep 2026 22:15:57 +0000

The nanobanana pro tier has quietly become part of professional creative work — and professional work carries etiquette that hobby use never meets: the client conversations, the disclosure lines, the revision boundaries, the deliverable hygiene. This is the professional etiquette guide for pro-tier generation — the etiquette practices that keep clients confident, deliverables clean, and relationships built to last through every tool generation that follows.

The Client Conversation, Before the Work

The disclosure that protects the relationship happens before the render, not after: the workflow sentence — "my process includes AI-assisted image production; the concepts and finishing are mine" — stated in the proposal or the kickoff, so the client's consent is informed and on record. The terms that matter to state: where the tool's outputs appear in the deliverable (the drafts only? the finals?), who owns what (the platform's output terms flowing into your work-for-hire language — the rights chain the client's lawyer will eventually ask about), and the revision logic (AI-assisted revisions priced like any other revision). The conversation's payoff: the client who knows the workflow never feels surprised by it — and the surprise is the only real risk the workflow carries.

The Deliverable Hygiene

The professional deliverable's checklist for generated assets: the provenance file (the prompts, the platform, the dates — logged per asset, the records habit from our library guide elevated to client-grade); the terms snapshot (the platform's commercial-use terms as of the work's date — the screenshot-dated practice, attached to the project file); the rights confirmation (the reference images licensed or owned — the consent baseline from our ethics guide, documented); the finishing pass (the human review for the artifacts only zoom catches — the text, the hands, the edges — because the professional bar is what survives 400% zoom); and the disclosure label where the destination requires it (the platforms and jurisdictions with AI-labeling rules — the voluntary label being the cheapest insurance everywhere). Five items, an hour of discipline per project, and the deliverable stands on paperwork as solid as its pixels.

The Boundaries That Keep the Work Welcome

The etiquette lines that keep pro-tier generation professionally acceptable: the style-clone refusal (the client asking for "in the style of" a living artist's portfolio — the redirect to inspired-by-or-licensed, the ethics guide's line held under commercial pressure); the real-person consent (no generated likenesses of real people without their say-so — the campaign's "AI version of the CEO" being a consent conversation, not a prompt); the credit honesty (the awards and portfolios disclosing AI-assisted work where the venue asks — the disclosure that costs a little pride and buys a lot of standing); and the scope honesty (the AI-assisted workflow priced for its real value — the speed benefit passed to the client, the craft still billed). The pro tier's tools are new; the professional conduct is not — the etiquette above is the old contract, signed for the new tools. The workflow guides and client-facing templates: ai image editor, with the ethics framework at ai image editor.

FAQ

Do I have to tell clients I use AI generation?
The professional norm — and increasingly the contractual one — is disclosure in the proposal: the workflow sentence up front keeps every later question answerable.

What should my deliverable file include for AI-assisted work?
The provenance log, the dated terms snapshot, the rights confirmations, the finishing-pass note, and any required AI labels — the five-item hygiene that stands up to audit.

The Long Game: Reputation as the Real Deliverable

Zooming out from a single project: the etiquette above compounds into the thing a freelance creative actually sells — reputation. The client who was told about the workflow up front becomes the client who explains it to the next prospect on your behalf ("they use AI for speed, but the judgment is all them"). The deliverable that survived the 400% zoom becomes the portfolio piece that survives scrutiny anywhere. The provenance file that answered one audit becomes the template that answers every future one in minutes. And the boundaries held under pressure — the style-clone declined, the likeness consented, the label applied — become the professional identity that attracts the clients who value exactly those lines. Tools will keep changing; the reputation is the asset that persists across them. In a young industry still writing its norms, the practitioners who behave as if the norms already exist are the ones who end up having written them.

Online Image Editor Like Photoshop: What Browser Tools Can Really Do Now

Leo Xm — Wed, 30 Sep 2026 08:14:35 +0000

The search for an online image editor like Photoshop usually starts with a price tag or a laptop that fan-spins at the mere thought of opening desktop software. The honest answer today: browser editors have closed most of the gap for everyday work. This guide maps what browser tools handle beautifully, where they still trail the desktop giant, and how to pick the right one for your actual workload.

What Browser Editors Handle Beautifully

For a surprising share of real-world editing, browser tools are not the budget option; they are the rational one. Core retouching, crop, exposure, color balance, healing brushes, background removal, and layers-based composition all run smoothly in modern editors. AI features have accelerated the gap-closing: one-click object removal, sky replacement, and generative fills that once defined premium desktop suites now load in a tab. Speed matters too: no install, no update dialogs mid-project, and your file opens the same on a hotel computer as on your own. For social media graphics, product photo cleanup, real estate shots, and quick composites, a capable online editor delivers indistinguishable results in less time.

Where Desktop Still Earns Its Keep

Honesty requires the other column. Very large files, think multi-hundred-megabyte RAW files or posters sized for print at high DPI, still strain browser memory. Deep print workflows with CMYK precision, color-managed proofing, and plugin ecosystems remain desktop territory. Heavy automated batch pipelines with scripting also favor local software. If your work lives in those corners, the desktop suite justifies itself; if it lives anywhere else, the browser covers you completely, and the subscription you skip funds better coffee.

Choosing Your Editor: A Five-Point Test

Run candidates through this checklist. Layer support: real layers with blend modes separate editors from toys. Export control: resolution, format, and quality settings that you set rather than accept. AI features that work: try one object removal on a cluttered photo; sloppy edges reveal toy-grade models. Privacy posture: check whether uploads are stored or trainable on; reputable tools state this clearly. Loading and response speed on your actual file sizes: a tool that chokes on a twelve-megapixel photo is telling you something. A solid example of this class is the online image editor like Photoshop workflow, which packs layers, AI removal, and fine export controls into a tab and costs nothing to try.

Frequently Asked Questions

Are online editors safe for client work? Reputable ones are; verify the privacy policy regarding file retention and use HTTPS, and keep original masters locally.

Can browser tools open PSD files? Many import PSDs reasonably well, though exotic layer effects may flatten; test with a representative file.

Do I need a powerful computer? Less so than desktop, since heavy lifting happens server-side at many tools, though very old machines still feel the strain on large canvases.

Conclusion

The browser editor question has quietly become settled: for most people's actual editing, layers, retouching, AI cleanup, exports, an online tool now matches the desktop experience without the cost or the install. Test candidates against the five points, match the tool to your real workload, and keep desktop for the niche corners that genuinely need it. The photos will not know the difference; your budget and battery will. One last habit worth adopting: keep a shortlist of two editors rather than one, a primary for daily work and a fallback with different strengths, because every tool has outage days and feature blind spots, and a one-tab switch keeps your deadline intact while the internet argues about which platform is best.

Small Notes on Everyday Tech and Desk Setups

Leo Xm — Thu, 10 Sep 2026 04:04:39 +0000

Last month I moved my entire desk setup around and discovered that half of my daily annoyances came from how I had arranged things, not from the things themselves. The charger I thought was slow was actually buried under three other cables. The keyboard lag I blamed on software was a wobbly desk. Sometimes the fix is not an upgrade, it is a rearrangement.

I want to use this little corner of DEV to write down small observations like that one. Not tutorials, not deep dives, just honest notes from using everyday tech: a monitor arm that gave me back my desk space, a cable label system that finally stuck, and a backup routine that survived its first real accident. I work outside the software industry, but I tinker constantly, and writing things down has saved me more times than I can count.

If you stumbled onto this post, hello. I plan to publish every week or two, keeping things short and practical. The kind of notes you can read with your morning coffee and apply before lunch. Next up: why my seven-port USB hub taught me more about power delivery than any spec sheet ever did.