As a designer, it’s hard enough to convince yourself it’s worth both the investment of time and cost in changing to a new piece of software, incorporating systemic change to your processes seems a daunting if not overwhelming task that recalls the old adage ‘if it ain’t broke, don’t fix it.’ But to convince an entire workforce to take a bold new direction in how they run the design department, re-structure all your existing processes from initial mockups, prototyping and production handover? Well, that could arguably be considered impractical and hard to justify at the least. But as is often the case, if you take the leap, you might just land in a better place - or at the very least, a more pleasurable one.
The Adobe Creative Suite in its many guises has been the staple go-to software for designers since, well, before I became a designer way back in 2006. I’d had limited experience creating web mockups coming out of a Computer Science degree and only dabbled in print and vector artwork using Adobe Photoshop and Illustrator. Photoshop was more than enough at the time to create viable, editable website designs, but in a new role in 2006, the Creative Director wanted the team to invest some time toying with Adobe Fireworks that had become part of the Adobe family in 2005. A graphics editor combining bitmap and vector graphics seemed to offer the best of both Photoshop and Illustrator, albeit a simplified version of both, but with added features specific to prototyping, including:
At the time, it defined the very idea of rapid prototyping, a much more suitable system for web design, whilst perfectly working hand in hand with higher-end, more sophisticated Photoshop edits, or more detailed/fully editable scalable vector artwork from Illustrator that could be imported and embedded with ease. So much so that Fireworks became the core of my design process from that point on, across multiple roles and jobs right on up until 2019.
I’d moved onto brighter days in the form of Black Antelope in 2013 where they were happy to include Fireworks as part of the design and production process which at the time was still in flux. In general, the role required a focus purely on Fireworks for web prototyping, sending emails of image attachments between clients and production as the default approval process. Email chains would become convoluted, emails or important directions often overlooked, and the review period often took considerably longer than it should have. With no alternative offered, everything still… worked.
Scott had wanted to simplify the review process for some time, and had come across a new online collaborative design platform called InVision that allowed for designs to be uploaded, organized, historically backed up and commented on in the context of the designs, for ease of visibility and a much faster and more intuitive review process. InVision became a significant boon to the workflow instantly:
Initially, we found InVision to be a huge improvement to use as the mainstay of our design review phase, but we continued to use Fireworks to create the designs, and export comps as flat PNGs/JPGs to upload into InVision manually for client review. However at this point, Adobe had already switched to the newly innovative Adobe Cloud service, allowing multiple license options to use a variety of different softwares under one account. Aiming to branch out with newer solutions, one heavily criticized decision was to no longer support Fireworks by 2012 (the last version being Adobe Fireworks CS6 v12.0), with no true direct successor provided.
Despite this, and despite adopting the new review system, we still continued to use Fireworks for many years and it worked very well in tandem with InVision despite the lack of support or any new updates. Many developers and fans of Fireworks created their own free downloadable plugins for the community to add new features to the fading UI, trying desperately to keep the flickering light burning brightly.
But the lack of support slowly became all too evident, regular crashes would occur (particularly with larger project files), files would become corrupted and no longer open, and hours of work would be lost; with the lack of autosave, your work could disappear in a frustrating heartbeat because of forgetting to save in the heat of a productive design session.
However, despite clinging to Fireworks for over 6 years past the end of its support, the killing blow would come in the form of a macOS update, OS Catalina in 2020, which deprecated 32bit support, and with Adobe having no need or intention of providing a 64bit version of a software no longer in their online consciousness, a forced end was nigh (outside of running Fireworks on an older version of the OS without plans to ever update!).
Since adopting InVision, we’d been aware of their own promising design software, InVision Studio, a powerful screen design tool that could potentially take over from Fireworks. At this time, Sketch was already the design tool of choice for many web designers, but it was Mac-only, and our design team was divided between Mac and PCs. Studio supported both OS X and Windows, and looked like a worthy successor to Fireworks, so we gave it a tentative shot. Around the time we started using InVision for design feedback and review, I had attempted to create some basic design concepts in Studio, but it felt largely unintuitive and underwhelming. The pros were apparent just through preliminary investigations -
However, the cons were more glaringly obvious -
While the benefits outweighed the new challenges it presented, InVision Studio was only strong enough to be a stepping stone in the evolution of our new design process.
It wasn’t until 2019 that we took a leap of faith in adopting Sketch as a real successor to Fireworks, which also required all of us to embrace macOS for design. The industry had defined new standards for prototyping and Sketch not only seemed strong out of the gate, but was backed by regular large updates to adapt to the ever increasing demands of its users.
We decided to try it for an upcoming client project because InVision had seen the benefit of providing communication between Sketch and InVision’s online prototype platform, by providing the Sketch plugin Craft. Craft supercharged screen design by allowing any and all artboards within Sketch to be uploaded directly to a project on InVision, assigned to clients and internal teams alike for review.
Craft also syncs artboards between Sketch and InVision seamlessly, allowing you to upload only those artboards updated since the last upload, the entire suite or just specifically selected artboards to replace.
This marriage of combining the superior screen design tools, excellent collaborative features, exceptional integration with InVision, and easy exporting of bitmap and vector assets in the latest formats (JPG, PNG, SVG, WebP), was a perfect system for our design process. The benefits didn’t stop there:
While nothing is perfect, Sketch does have a few cons to consider:
Within two years, we’ve surpassed well over 50 desktop and mobile design projects combining the cohesive power of Sketch and InVision (with a little help from Photoshop and Illustrator along the way). While a single piece of software (and ideally, single price point) has yet to cater to all our needs, this rich combination has seen a rapid increase in the efficacy of our design phase and handover to production, while being a much more convenient and guiding hand for our clients when it comes to their feedback and ultimate approval of the projects. With the backing of a large community, dedicated product support, and conviction in their products, it looks unlikely that Sketch will ever have the same fate as Fireworks.
But the clear benefits of exploring new options, testing the waters for tools that are not only improved, but allow you to build and develop something far grander in scope, far richer in features and in a far more enjoyable experience - these benefits can’t be overlooked and the old days of using Fireworks and email communication seem antiquated, almost barbaric in comparison to the processes today.
Which makes us open to the idea of being receptive to more change. There are already rivals to Sketch, as there will always be competitors aiming to surpass the standard. You’ll likely not hear the word Sketch without being followed by the word Figma for example. Figma is a collaborative screen design tool, with strong symbol and shared asset management, and advanced commenting and review tools to share and approve designs outside of the organization and internally. It works as a desktop app on macOS or Windows, but also it’s fully-functional via a web interface. At first glance it doesn’t appear to be as intuitive a system as Sketch, but peers have said it’s more advanced when delivering information and design content to production during handover. Like Sketch before it, we’ll likely employ it in an upcoming project and compare the pros and cons in more detail and to see whether our process changes with the times once more.