Plant v.s. Abstract v.s. Folio
All trying to do what LayerVault (The reason Designer News exists) failed to do in their own way, it's quite interesting seeing these things all evolve and compete.
Also Kactus :) https://kactus.io/
Haha yeah at first I thought "Oh did Kactus rebrand into Plant?"
HA! I'm glad I'm not the only one :)
My same thought. Personally, I've not experience a need for design version control. But I've never worked on a large team before.
The guy who is head of Design's name is Art: https://plantapp.io/#about So random, but I like it
I thought this was some sort of version control for plants and I cared for a hot second.
This super neat! I only wish something like this existed for Creative Cloud apps.
Aurooba, thank you! Support for adobe apps is definitely on our roadmap
The whole concept of version control for Sketch files seems odd to me. Personally, I can't think of what problem it's really solving.
Is it just trying to solve the fact that you use one file for experimenting on ideas?
Is there some teamwork thing where you'd create sections of the app in Sketch, and then other teams could branch and make changes?
Is it trying to create another source of truth?
have you ever had a design, then changed it and wish you could revert back to an earlier version? also branching is something that comes to mind with sketch version control, allowing you to explore a few options without duplicating etc.
Not really. I just create new artboards and experiment. Then delete or move them to an archive page. I can't think of any time in the past few years I wish I could revert it back to a previous version.
I just create new artboards and experiment. Then delete or move them to an archive page.
This just sounds like you're manually doing some sort of version control tbh. Not saying that you necessarily need it, just that VCS automates some of that as well as making more long-term experimentation easier.
i agree, but if that works...
EDIT (11 months later): This is such an important tool for a team. Being able to work on the same file and merge changes is the piece that I was missing in my earlier comment.
For me too. I've found if you're using Dropbox, this isn't needed. Just jump on version history in Dropbox and revert.
Am I the only one that thinks the product and brand look a lot like Abstract?
Also, for those of you wondering about the need for version control for design files, yes, it's absolutely needed to scale design teams, collaborate on projects, and work with remote team members.
I implemented Abstract with my team earlier this year and it's made marked improvements in our scalability and process for creating design systems for clients.
Can SF font be self-hosted on a server?
i would love to use this (i am trying it out right now) but it doesn't support libraries at the moment so none of my artboards are working, searching your site for a workaround at the moment.
Hi Jeff, actually Plant fully supports Sketch libraries. Symbols from Sketch Libraries file can be shared across all your project, and in case you don't want to share your Sketch Libraries file with other contributors, but you have projects which use symbols from Sketch Libraries file, Plant is smart enough to version it and contributors won't lose the latest version of those symbols.
If you have any issues please contact us at firstname.lastname@example.org
interesting, that wasn't my experience. i will try again!
I'm a somewhat satisfied paying user of Abstract (somewhat = it does what I need but I also have big expectations for groundbreaking features in the future).
Can anyone who's experienced both product speak about the pros and cons of each?
Specifically, I think Abstract's branch support and "immutable" master branch is a great feature. Plant doesn't seem to have this. Is that true?
I'm confused on why this application keeps asking permission for 'stored information in my keychain' application, and if I deny it, it kicks me out of the app. I think you need to better explain what this access is being created for, and why.
Hi Joe, Art here, co-founder at Plant. When the user logs in using the Plant Mac app, then the app writes their keys to the keychain and in order for some other application to access them, it must request access to the keychain. In our case it is Sketch inside which the plugin is located (from the OS point of view the plugin and Sketch are the same). The same is the reverse - when we login through the Sketch (plugin), it writes the keys to the keychain, and the App should ask for permission to access.
We are working on an alternative approach, so that we do not have to ask the user at all, but so far this is how it works.