We just recently started using Pixelapse a week and a half ago, so I can answer a couple of these. There is an app that runs in the menu bar of our designer Ke

We just recently started using Pixelapse a week and a half ago, so I can answer a couple of these. There is an app that runs in the menu bar of our designer Kevin's mac, which automatically uploads "revisions" of the design he's working on. It only captures changes to the file on disk, so he has to save strategically knowing that it will create a "revision". I personally don't like this, as it discourages saving often. To be fair, you can mark different revisions as "milestones", but this just seems like a bandaid for this particular problem. Before using Pixelapse, Kevin had his own workflow (similar to what you mentioned), where he'd save different versions of a design as project_homepage_option1.jpg, project_homepage_option2.jpg, etc. Pixelapse absolutely does not support this. It will upload each one as a different file and offers no way to combine them so that you can compare them for review (and there is no way in Pixelapse to compare different files, only different revisions of the same file. Also keep in mind that Pixelapse, along with every other similar app I looked at, uses the revision/history paradigm for comparing designs. But I think Pixelapse at least allows for the non-timeline-based approach a bit better than others, though it still didn't quite fit our workflow without some changes to our workflow. Edited to clarify, I wasn't trying to be too critical of Pixelapse. I actually really like it, it just required some changes to our workflow to be effective, and I think we're still trying to figure a couple things out.