Hi, I’m Joe, a Motion Designer at Together. Basically, if we did it and it moves, I’m probably the guy that’s done it.
We’re doing more and more of it these days, and so is everyone else it seems. Click on any website, walk past any city centre billboard, browse any company’s social media posts — motion is here … there … and everywhere.
And for good reason. Motion is an incredible tool, with the power to engage, educate and entertain — tacky hook, I know, but let’s not overthink it. (We’ll come back to the three E’s later, don’t worry.)
Since I first started, the field has been slowly changing. (You could even say it’s been … in motion.) It’s no longer solely about straightforward, linear animations or videos played from A to B. Motion has been quietly absorbing elements of UX/UI design, and sneaking into the domain of web development. These days, even humble utilitarian buttons are being sprinkled with the magic dust to give them more character.
Well, where am I going with this?
Why I hate love designers and developers.
As a motion professional, every day you walk a tightrope.
On one hand you’ve got pretentious, know-it-all, flat-white-drinking designers who look for the aesthetic or narrative of an animation piece, but often come up with storyboards that are too complex for developers.
On the other hand you’ve got four-eyed, basement-dwelling developers, obsessed with small file sizes that integrate easily and don’t ruin those blisteringly fast pagespeed scores they’re so proud of.
How do you reconcile the two?
What it really comes down to is which format you choose for your animations.
From Sillypun.mp4 to Dadjoke.json.
It all started with MP4, the good old fashioned Swiss Army knife of the video format world. Used extensively for some time now, it’s a video format that is heavily supported by almost all players and browsers.
MP4 has never really let us down, assuming you know its limitations. And speaking of limitations, first there’s the file size … Oh, the file size …