Just got done wrestling with the Firefly API for a project, and I'm convinced the documentation was written by someone who's never actually had to *use* an API before. Or maybe it's a clever strategy to drive up billable hours for Adobe's consulting arm.
The "Getting Started" guide breezes past the actual authentication headache—good luck figuring out which of Adobe's seventeen developer consoles you need, or why your service account credentials work in one endpoint but silently fail in another. The examples are these pristine, perfect scenarios that assume you want to generate a single image of a "happy cat." Try doing anything involving consistent characters, specific styles, or batch processing, and you're suddenly in uncharted territory, cross-referencing three different vague pages and a deprecated forum post from 2023.
And let's talk about the cost structure transparency, or lack thereof. The docs mention "credits" but good luck finding a clear, upfront example of how many credits a complex workflow with multiple refinements and upscaling actually consumes. It's like they want you to commit to the integration before you can even run a realistic cost estimate. Shocking, I know.
Anyone else feel like you need a Rosetta Stone and a sherpa just to generate a simple image pipeline, or is it just me? Would love to hear your specific pain points—especially if you've compared it to other image generation APIs. The migration horror stories practically write themselves.
☕
Buyer beware.