Hello, and thanks for checking out Specly!
Specly took shape over several years while I was Co-founder and ECD at Medialets (founded in 2008, acquired by WPP/GroupM in 2015). Specly came into being organically; my Creative team needed better ways to document and describe the HTML5 mobile ads we were collaborating on for our clients. Medialets’ ads were like nothing else the digital advertising industry had ever seen, partly because the mobile and tablet platforms we were building them for introduced so many new and unique use cases. The ads had to be orientation-aware, fill all the available space on varying mobile (and tablet) screen sizes, expand seamlessly across disparate environments, and they were developed in HTML5 instead of Flash. It was a bold and pioneering time for digital advertising.
We were designing and building unique, first-to-market ad experiences, but since we were doing new things in new ways, the internal and external communications about our creations became an unprecedented challenge. We often found there was no “language” that could adequately explain the modern digital artifacts we were making. And the explanatory diagrams we would invariably have to whiteboard for each other and our clients were not exactly "portable" across email chains. Inordinate amounts of time were spent on just communicating (or miscommunicating!) how ads were supposed to be designed and developed. We even held meetings to talk about how to communicate more efficiently! Ultimately, it all meant we had less time for actual design and development—the fun stuff! There simply had to be a better way...
On a mission to help explain our work to each other and to our clients, I wrote the first draft of Specly’s documentation in late 2013. Specly was born! ...at least “in the lab.” We began to use this first "beta" version of Specly as a communications tool right away, both internally and externally. The reaction from my team and from our clients and partners was unanimously and overwhelmingly positive. It was common to hear things like, “How have we not had this?” and, “What were we even doing before we had this?” As we adopted Specly into more aspects of our day-to-day workflow, we saw extraordinary results: our meetings were shorter, great ideas flowed more freely, communications between designers and developers were streamlined, costly miscommunications evaporated, better work was done in less time, and most importantly, my team and our clients were happier.
As my team grew, and as mobile steamrolled its way to dominance in our marketplace, I saw how the big agency creative teams we partnered with began to encounter the same types of design challenges my team had in prior years. It became obvious that the entire digital design industry needed a way to document and communicate design specifications without resorting to ad hoc diagrams and animations just to (hopefully) explain them—and not just for advertisements, but also for apps, websites, and anything else digital. We could all do better work more enjoyably if we had a common language that helped everyone get past the explanatory diagrams and move toward the “fun stuff” earlier in the process.
This website was launched so that everyone can learn to use Specly within their workflows, and easily share it with others. Over time Specly was expanded with new techniques that empower a growing set of design and production demands so that teams can use it for everything they create—websites, apps, ads, icon sets, and more. I encourage you to incorporate Specly into your design workflow; please let me know how it goes if you do!
If you have any questions, ideas about how to improve Specly, or if you want to support Specly by sharing it with others, please like Specly on Facebook, follow @useSpecly on Twitter, or send me an email to firstname.lastname@example.org.