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.
I think the only thing that you lose here is access to an actual "diff", but visually, you get most of it.
Grats on a fantastic achievement.
Someone was working on a .js PSD file parser, which may be of interest down the line but it was in early stages.
Great product, I love the idea. Well done.
Version controlling for design is great but if you want to differentiate from layervault or pixelnovel.com then you should try and see if designers would collaborate in an opensource fashion, ala github. (I am really curious about this, as that's the real reason people use github AFAICT)
So I would go and add some social aspect for it, make it a bit more like dribbble, behance, flickr (portfolios, inspiration) as these are the sites that designers use.
Also adding stockphoto/illustration selling and job board features would probably make for the best designer platform ever. (not mentioning the business options...)
And after this feature suggesting madness, I would like to point out that if you want to keep this simple and stupid, then still please get a designer and work on the ux.
Keep up the good work!
When a designer is working in photoshop they are not actually part of the development process yet. They are still in design mode, they are for the lack of a better word sketching.
Not until they start to actually output assets for developers do the github concept start to make sense.
Designers often have different versions of the same design inside the document in the layers and groups and smart objects.
They will for instance have a couple of version of a header or some styling on their elements, perhaps different layout for main content.
So for this to be useful it would need to create a kind of master psd that save the state of which layers and groups are turned off and on.
This way you can sketch away and not have to worry about creating a billion different versions inside the documents that just make them bigger.
But that is a different problem.
When we first came up with this idea, we really needed a good way to comment & annotate and keep all that feedback inline instead of it spilling over into email. The second is that we provide an easy way to diff revisions side by side or overlay them to see what has actually changed. Behind the scenes, we actually work quite differently from LayerVault, particularly on large files. I'd love to talk to you more to see how we can help you. Please email me firstname.lastname@example.org.
The functionality and usefulness of this service is fantastic, but I wonder how hard it would be for github itself to compete; they've shown that they can do simpler binary versioning and comparison with PNG/JPEG images, so all they'd have to do is add support for previewing PSD files as well. Whether that's a simple thing to support is not something I'm qualified to answer though :)
Another issue that might be how integrated the version control system could be into the graphics app. Github will never aim to integrate itself deeply into Photoshop, so designers would be forced to visit a browser to see changes.
Something like OS X Lion's file versioning system might actually be perfect for this.
I did find a small bug:
in the X/Y view, your scrollbars are draggable, so if you scroll the image, then release the mouse button the view panel gets stuck to your mouse.
Are the full files for each revision saved? Or have you developed a way to store only the differences?
With large PSD files, the former could get expensive quickly, which makes me wonder the same thing as ARolek asked, what will pricing be based on?
When playing around with the |X|Y| functionality
BUG - Dragging the slider on a compare window beyond the container and releasing the mouse causes the window to follow your mouse around. Your drag and drop "sorting" functionality seems to kick in.
BUG 2 - Adding multiple versions to the compare frame works well, however it was initially hard to tell how to remove a given frame. Some ability from the frame would be nice, but that wasn't the bug. When you add multiple versions to compare you see them highlighted below. Then when you go to another view (i.e. the single revision view) and back to the |X|Y| compare view the frames you were last comparing are still there, however they are no longer highlighted.
Again, this looks great, just keep going! :)
This is something I have thought about doing for a while, but to be honest, I never had the technical chops to do it at the time.
Sure, parts of this still needs polishing - got some quirky JS issues with the comparison of the two images side by side in Chrome on Windows.
But you guys have done and awesome, awesome job!
Edit: Btw, this is the quirky issue I encountered - http://i.imgur.com/MOY9c.png To replicate this, in Chrome on Windows 7, click on the 'X Y' side by side icon and then just try scrolling the images up and down, or side to side, and then moving the mouse. It moves the entire DOM element.
Congrats on the launch.
Try and chose a 2 syllable or a less tongue twisting name.
Rather, my point is simply: it's worth it.
So for me, downloading a client that syncs, while useful, is not the _answer_.
The answer is for designers to embrace git and also for developers to make git easier to use. Whether that requires a better UI, better documentation, better tutorials, etc.
Git has the power to do all this and more, there just needs to be an intuitive wrapper for the workflow maybe?
The big problem with that is that its extremely buggy. It seems to choke on merge conflicts most of the time and it can get into some really weird states. I've had it undo changes on completely different files than what I told it to and lose hours of work.
Just ideas that popped into my head looking at this. It's pretty awesome, great job!
I wonder if it would be possible to turn design files into something textual to leverage git's builtin merge capabilities?
Also, really neat concept overall. Can't wait to try it!
Granted, Creative Cloud isn't fully released yet, but it will be soon and it is basically this plus Dropbox plus full native integration into all the Adobe apps.
I see this as a case of applying a successful model from one field to another without consideration around whether this is actually a problem in the first place.
When I click for an invitation, I get an Application Error (An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details.)
Re: the app error. We underestimated the load on the site. :) We just scaled up so if you refresh and try again, you should be able to sign up.
Congrats on a sharp looking launch, Pixelapse!
My favorite is the side by side view. Speaking of which there is a bug in latest chrome on win where the side by side panels get dragged when using the scrollbar.
Fuck it, I'd fund this.