But that's just it, I have to find a use for it. It isn't immediately obvious to me. I'm not the typical designer as I don't have clients and my job isn't 100% design but I have been designing everything from packaging, to print advertisements, to websites for ten years. I don't know why I would use this. If I need alternate versions of files I just save them with version numbers. The poor man's version control. But I don't need anything more than that - do other designers?
The power of Github I believe is that it allows programmers to share their work with their colleagues, learn from others, and work together with others.
I like Dribbble because it allows designers to do what they want to do with their colleagues. Show off their work and get inspiration from other designers. To me, Dribbble is the closest thing to a Github for designers.
What's missing from Dribbble is the collaborative part. Coders working with coders, designers with designers. But that's the problem. Coders have to work with other coders all the time it's the nature of the beast. Designers do not in the same way. In my experience.
So if it's not designers with designers then it's designers with coders. And a place for those who (like me) both design and code to both showcase our work and to work together with others. If you could turn this into a Dribbble + Github I think that would be interesting.
As a designer/programmer, I completely agree.
As a programmer, the idea of saving multiple copies of a file with different versions numbers just sounds awful.
But when designing in photoshop, theres rarely a need for a full version control system since I usually only have 5-6 PSDs of each iteration per design (or logos/sites/etc) and at that scale its easily manageable.
If version control was built into photoshop, it would be nice but the important thing is its not a need I have and I wouldn't necessarily seek this type of product out.
I feel like the word "version" means completely separate things to a programmer talking about (d)vcs and to a designer talking about mockups. To a programmer, version control is more likely to mean revisions of the same file as it evolves and is changed. To a designer, a version is a distinct mockup that represents a new look.
(Sure, a programmer may rewrite something, and a designer will tweak something. But, even then. Different words are used to describe what took place.)
I think you hit the nail on the head with regard to what designers need from version control. We bill ourselves as Dribbble + Github for creative teams exactly for the reasons you describe.
I would really like to find out what revisu does and how it works without signing up. An intro video would be ideal, or at least a much more detailed feature list and screenshot walk-through.
Thanks for your feedback! We've talked to a few designers and it seems like everyone has a slightly different workflow. There are definitely people who manually save different files as you do and some more hardcore designer/developers who use git to manage versioning. We think there's a middle ground in between where you don't have to think about versioning and it just happens in the background.
We've hidden it in the demo but we've baked in collaboration as well. You can create a group for your team or even show it off publicly, a bit like Dribbble. The benefit of using Pixelapse is that you can learn how a design was created from start to finish. Like you said, not all designers necessarily work with other designers, but there's definitely collaboration and conversations with managers or developers or other stakeholders who may not be design/tech savvy. We want to save you from the cycle of exporting the psd, emailing the copy to a bunch of people, getting feedback and having to repeat as you incorporate the feedback. We're still thinking about different ways to expand and move forward and doing a Dribbble + Github may well be where we ultimately end up. :)
Sounds like you're aiming at teams and small ad agencies? Is that correct? I do like the idea of being able to share the versions as it progresses with other stakeholders. That is valuable. I didn't grep that from the demo. Admittedly I didn't poke around too much, I spent a few minutes on the site.
Is this for web design teams or mostly traditional media teams (Packaging, branding, print)? If the former, how do the developers work with it? If the latter, I like the functionality you've described.
I apologize if these questions and my critiques are too early in your dev cycle, I realize that you just released this (And it does look well polished!). I really just have an interest in this space and would like to see something work for my needs.