The pros far outweigh the cons for your team to be using Abstract. Get started with it and we doubt you’ll go back to managing files through Google Drive or Dropbox.
Avoid chaos and have a singular source of truth.
Typically, our workflow would be to create multiple working files segmented by what each user is working on or by feature, but this often gets messy as you work on larger projects and more files are riddled through your folders. You almost need a board to manage what is contained in which files and what versions are the most current.
We received an invitation to test drive the platform and have been using it in our workflow for about 3-4 months.
You have a master branch that everything is merged up into, and you create child branches that are for working files. As you check files out and commit changes, you can get approval from whoever is monitoring and controlling what makes it into master, and making sure your additions to your design system or interface are consistent with the rest of your product.
If your team is using sketch for design and you need to manage versions and allow multiple designers to collaborate, you should definitely bring Abstract into your workflow.
If you’re interested in learning more about the product and team at Abstract, stay tuned for a new episode of Seaworthy releasing later this week featuring Tim Van Damme, Abstract’s Head of Design.
See all the ways we can help you grow through design, development, marketing, and more.
A podcast about building successful software. We provide actionable advice around product validation, execution, and promotion.
Receive the latest articles, resources, events, and more!