A bit of history on this:<p>All APNG has ever really needed to build a sustainable momentum is--like most other web features--a plurality of web browser support. These days, that usually means "supported in both Firefox and Chrome." Until that happens, nobody has any reason to create APNGs, because you can't stick them in your cutesy forum signature and expect other people using the website to see what you see.<p>Firefox already has APNG support; Chrome is the hold-out here. It's mostly because Google only want to use the "official" libpng. libpng, though, is intentionally a minimalist reference implementation! The PNG group will never accept the APNG patches into the official libpng, because that would distract from libpng's purpose in being a reference for how to encode/decode PNGs. And Google don't want to apply the APNG patches themselves, because that means, basically, supporting their own fork of libpng.<p>In other words, what's really been needed this whole time isn't "better authoring tools" (create consumption tools, and authoring tools will follow) but rather for some large organization to get behind maintaining and supporting a regular release of "current libpng with apng patches." Big enough, at least, for Google to feel as confident in their work as they do the PNG group's.<p>The easy solution, of course, would be to split out the work Mozilla is <i>already doing</i> in maintaining <i>their</i> "current libpng with apng patches" from Gecko into a separate project, and let both Mozilla and Google (and Apple and Microsoft and whoever else) be consumers for that project. If there's anything to get done, it's that.