A Necessary Addition to any Sketch-Based Product Team
- Our product team uses Abstract in conjunction with Sketch for collaboration, file management, and versioning. It's imperative for us. Our team has three user experience designers and six user interface designers. So while we have a long to-do list, we are always working in groups on a single feature set from wireframing all the way to final designs for IT handoff.
- Due to that, Abstract allows for robust versioning and file management without losing work. Before finding Abstract a few years ago, my team at the time had to carefully plan what features would be worked on and by who. Then make sure we don't have the same files open via Google Drive and clearly explain what artboards were changed and need to be addressed. It was a nightmare.
- Abstract scans each of the Sketch files and looks for differences combine work and allows all of us to be working in one file at once.
- Allows for collaboration within Sketch.
- Allows for approval of work by team leads.
Cons
- Frequent bugs between Abstract and Sketch.
- Takes a lot of processing power and battery.
- Saves time on file management
- Keeps old, archived work
- Google Drive and Egnyte