flysi3000

Ah, true, true... I was just curious and thought I'd ask here cuz I figure this is a pretty in-the-know crowd.

Hearing more and more about Lottie lately (plugin for exporting animation from After Effects to JSON), and as I understand it, the real obstacle to using it for banner animation is the weight of the js library. Now that support for it is coming in Adobe Animate, might we have a strong enough case to get it white-listed (like gsap, createjs, etc)?

Chiming in, just because I saw this the other day as well and had the same freakout, but then I realized that it happened when viewing our ads in a private window in Firefox. When viewing in a regular tab, I think it's okay, but it bears a little more research (which I haven't had the time to do yet).

Whoa - that page is a treasure trove of helpful stuff! Thanks!

Woo! I actually used easeInOut on the main tween, and stepped the other one - so the inverse of what you suggested. Seems slightly more noticeable, but I guess in essence it's the same thing. Thanks for the speedy reply!

Hi! I have a hypothetical question - some creative feedback I got for an animation was to make it more "stop-motion-like" but at the same time, add some easing in/out to it. My initial reaction was that this is self-contradicting feedback, but then I thought that if I were actually shooting some stop-motion animation, I could actually add easing by adding more frames at the beginning or end of the sequence. Is this something we can simulate with GSAP? I'm currently using SteppedEase, and was thinking I could take my existing tween, and tween its progress with an easeIn/Out applied to that. Is that nuts? Is there a better approach?

Thanks for the input, guys. @geedix I was looking at those specs; I think we had more than 10 external images, though - that's probably why we got the banners kicked back. I ended up solving it using a couple of gulp tasks to parse the js for image file paths and base64 encode them inline, then inline the js into the index.html file. I managed to get the files down relatively small, but I had to start with non-retina images. It was a lot of f*cking hoops, and I told our producers it seemed really excessive, but we just wanted to get these out the door, so I didn't push the issue too much.

Hey banner fam, question about a spec we received for some ads being served by Amazon. Our units are getting kicked back, because they say we need to minify scripts, and combine linked javascript and images into a single index.html file to minimize network calls. The minifying and inlining of scripts is one thing, but have you guys had to do this with images before? I'm looking up ways to use gulp to do all this automatically, but I'm spinning my wheels a little bit. Right now my approach is to try and parse the minified js file for file paths, then replace those file paths with the converted base64 data. All of this seems excessive to me. Right now, our build script spits out the following folder structure: +--build | +--my-banner | +--index.html | +--scripts.min.js | +--.jpg | .png | .svg images It would be great to be able to run a gulp process on the contents of the build folder to put the contents of each banner into a single index.html file, cuz it seems like that's what they want. Any pointers in the right direction would be awesome.

Gotcha - yeah, I was wondering about that. Cool, well it's helpful to know that's how some people manage their campaigns. Thanks!

That makes sense - thanks! Do you guys use the same workflow for bigger campaigns? We sometimes have buys that are like 64 units and more (many, many more... ?).

Nah, if there's blame, I think it can be divided between the excessive use of tracking scripts by publishers, and the scummy ad platforms that try to inflate their ad views to rake in more $$. And, yes, devs that are sloppy and get lax about best practices. (raises hand)

Hey! Are any of you guys using something like JIRA or Asana in your organizations to track your banners? Any recommendations or outlines for workflows or best-practices?

Hey! So, I went to the AMP Ads workshop at Google's NYC headquarters a couple of weeks ago. It was great to get to meet the Google team and hear the justifications for AMP, and also to voice our questions and concerns about the road ahead. There were representatives from five different agencies or production houses there (including myself), and without fail, the number one thing that each of us begged for was GSAP support. The Google engineers had apparently considered integrating animejs a while back, but balked at the 16k size of the library; GSAP is closer to ~30k, but they obviously are aware of how much we lean on the platform, so we'll see what they come up with. They're also considering implementing Canvas, which will open up some alternate avenues for us to do cool things like particles, etc. One other thing - they asked us to provide sample creative units that we had built beforehand, and at the event they showed us our regular html5 units that had been converted with an internal tool (kind of like Swiffy, back in the day!). They looked great, minus some interactivity (hover-state animation); the thought is that such a tool could get us 90% of the way to a finished unit. I don't know when/if it will become widely available. Anyway; other things to consider: - re. security, there are more and more stories like this one, of shady ad networks perpetrating ad fraud - not only is it a matter of security for users, it's also a matter of site performance, which impacts users' data and battery performance - the uptick in AMP ads served is increasing - the AMP HTML project is open-source, so you can contribute by making or improving components, etc. - GWD outputs AMP ads - as mentioned elsewhere, Adobe Animate will also output AMP. I saw a couple of sample units from the prerelease of this, and one was wack, but the other looked pretty impressive - AMP ads work anywhere, not just AMP pages That's it; hopefully, if someone from the AMP team checks out this post (which they've seen ?), they'll correct me, or fill in details!

We'll be doing some of that at the event here in NYC on the 20th, from what I gather. I'll post findings here, as I'm able, after the event.

It's not that they're not allowing JavaScript in banners, but that AMPHTML Ads only allow <amp-***> specific components, like <amp-carousel> and <amp-accordion>, and some inline css animation; you can't write your own JS, and no external assets via <script> or <link> tags as far as I understand. So no, you wouldn't be able to use GSAP in an AMPHTML Ad. Being unable to use your own JS, and the fact that everything lives on Googles servers is the reason they are touting these as more secure. I got invited to a thing at Google here in NYC later this month; hope to learn more then...