April 4, 2017Blog
Looks like I have been penciled in to present at the upcoming Google conference in Toronto to discuss Advanced Dynamic banners. Have to try to find some presentable work I've done in that area to show. That might actually be a challenge... Most of those kinds of banners Im not allowed to show because of NDAs for some reason. Hoping I can find something.
February 22, 2017Blog,Rant
I know the argument for live fonts in banners. Easier to make client changes. Less file size. Crisp readabilty.
But unless specifically told to do so, I will never use live fonts for the following reasons:
1) Images are much faster to code. Live fonts require a while bunch of CSS to get it looking correct. Imagine a price point, with a small $, different size dollars and cents, and a few dividing lines for good measure. Not difficult CSS, but takes way longer that just saving an image in Photoshop. Just set up an action in Photoshop to turn a layer or selection into a transparent PNG, and thats your image. And as long as you keep the PSD, it's easy to make changes. The one thing I'll give live fonts in this area is its easier for a new developer to take over as you don't need to worry about passing along the PSD as well.
2) Images are much easier to QA. An image is an image in every modern browser and platform. No way can you say the same thing about live fonts. It will looks slightly different all over the place.
3) Unless you have a web font licensed, you will need to resort to Google fonts, or something else not quite what the AD wanted. And even if you do have a proper font to upload with the zip, it will never look exactly the same as the PSD. Sometimes very close, but never exact. And the AD worked hard at all those kerning and letting settings which will be tossed.
4) Custom fonts can be huge, thus offsetting the file size you saved from using fonts instead of images. Maybe even putting you over the file size limit. And you will usually have to load it from the cloud, which is still a grey area for many ad servers.
5) Using tinypng.com with retina sized PNGs is surprisingly efficient for file size and quality. Thus quality with images will not be compromised.
Overall, the thing about banners is that they are temporary venues for advertising. They will typically be handled by one dev only, and only be around for a limited time. There is no need for easy editing or ease of transfer. File size, image quality, and speed of development are the three key aspects. File size/quality is debatable depending on the design and fonts, but usually can be done with images no problem considering what banners are usually designed like. But speed of development, there is no argument at all. Images are way easier. And will always get you exactly what the AD (and client) is expecting without having to resort to "Well, it's HTML text so it will look a bit different than the PDF."
January 5, 2017Blog
Every year I seem to think I have the timing of the busy banner season hammered down, and every year it throws me off. It seems logical that November would be the busy season, with clients all preparing for the holidays. Then I would assume December would tail off as everything is already done and prepared and ready for trafficking. 2014 was like that. But this year November was the same as October which was the same as December. 2013 had a dead November, and a killer December.
I guess for freelancers it's not so much about time of year, but more on the particular clients you are working with that year, and their overflow.
August 31, 2016Blog
How is it that Tinypng.com compresses PNGs so much better than any other desktop based image compressor? Always thought ImageOptim was enough, but no. Always use TinyPNG.com as well.
August 3, 2016Blog
Since SVGs don't animate well in older browsers (Specifically zooming), I've avoided using them in banners for a while, opting instead for retina sized PNGs. But Im warming up to them. Most clients are caring less and less about IE9, and I've found a few really good tools.
The first is something with Photoshop CC that I only recently discovered. It allows you to export SVGs from text layers without having to do any extra steps (except for converting to shape layers). Just turn on File>Generate>Image Assets. Then rename each layer xxxx.svg, and without any extra steps, wherever you have saved the PSD, a new folder will appear with a file for any layer named with a .svg extension. Explained much better here: https://www.youtube.com/watch?time_continue=206&v=6TRz-gNdQFg
Also, I found a really good tool for compression SVGs. Give it a go here: https://jakearchibald.github.io/svgomg/
April 5, 2016Blog
In other words, it's going to be hand coding unless some sort of nasty animation is required. Then it's worth the fight to figure out if it can be used or not.
September 21, 2015Blog
The whole switch has not been as bad as I was expecting. Takes more work. Takes more time testing. Takes some more effort to get specs. And a few things here and there that I have to explain can't be done within the file size we have (which really is the same as Flash banners, just different things that can't be done). But overall, a banner is a banner. And Im a banner guy! Onwards!
From a banner perspective, Flash was able to hang on for 5 years after officially being declared dead for the first time back in 2010.
And for 5 years, I kept having to explain to people that Flash Banners were here to stay until HTML5 could catch up, and ad agencies could justify the extra time, cost, and increased creative restrictions.
Well, with the Firefox security block, and Chrome's supposed click-to-play banner ads that started in September (Which I have yet to actually see happen), agencies finally freaked out back in August, and switched everything over to HTML5.
It's been a crazy few months. Especially finding media companies that truly understand what is going on and can provide accurate HTML5 specs. Considering they still had trouble with AS2 specs sometimes, I think it's going to be a challenge for a while. But Flash really now is officially done. Coming from a Flash guy, that means a lot.
I will truly miss it. It was my career for 10 years.
It had it's bumps - like the IDE's tendency to like some fonts but not others, or crashing at the worst possible time. But overall, it was a joy to code with, and made things that HTML5 has difficulty doing in small files sizes, like guide layers and non-square masks, much easier.
Rest in peace my friend.
July 29, 2013Actionscript
Been working on a Banner Ad Development Guide for Project Managers and Designers for a bit, and finally completed it this morning. It is not about design - It is banner development from the Developers perspective, but not for the Developer. Feel free to comment and share!
September 15, 2012Rant
You know that new feature of the Mac OS called Versions? Its the thing that automatically saves multiple version of whatever file you are working on in TextEdit, Pages, Numbers, and other Mac Apps so you can revert back at any time to any previous state of the file. It's great for things like writing screenplays or shopping lists, when you might want to see what you previously did, or accidentally deleted something. But I've discovered that there is a possible security hole.
Whenever the operating system saves a version, it puts the data into an invisible database on your harddrive called DocumentRevisions-V100. This database is not encrypted. Which means that if you have ever made a text file that contains passwords or bank information on it, this database has a copy.
Now any smart person wouldn't make such a text file without saving it onto an encrypted DNG file or something like that. However, even if on an encrypted disk image, Versions still makes copies of it into the unencrypted database. So even though it seems secure sitting on that disk image, you actually have unencrypted versions of it hanging around.
Now this is only technically a problem if you have FileVault turned off for your hard drive. If you have FileVault turned on, it's not "really" an issue because your entire hard drive is encrypted.
But say you take your encrypted DNG file and stick it on a memory stick. Safe right? But then say you are at the library (that uses Macs) or at a friends place, and decide you need a password. You stick it in, temporarily decrypt the DNG file to get at your password file, and then close the file and eject the disk. Sounds reasonable. The file is still safely encrypted on your memory stick. But Versions has now created a copy of it on your friends computer in the database. Even if your friend has no intention of hacking you, there is still a copy of your password file sitting unencrypted out there.
People could be passing their secure documents around without knowing. Any thief who gets a hold of a computer could easily just browse the database looking for unintentional saves.
One should be able to turn Versions off on particular documents if they desire, and/or the database should be encrypted.
Hopefully Apple addresses this. If you agree, send them a suggestion, and warn your friends: https://www.apple.com/feedback/macosx.html