Live data from Hacker News

Pixelapse (YC W12): GitHub-Style Sharing and Version Control For Design Projects

techcrunch.com

1–10 of 21 posts

Re: Pixelapse (YC W12): GitHub-Style Sharing and Version Control For Design Projects

#5

How does this compare to Layervault?

LayerVault just has one plan: $24/user/month with unlimited storage and projects. Pixelapse seems more flexible with a free plan (1GB storage) and pay plans starting from $19/month (20GB) up to $149/month (100GB).

Not sure how they comparefeature or quality wise but Pixellapse's pricing plans might be serious trouble for LayerVault.

Re: Pixelapse (YC W12): GitHub-Style Sharing and Version Control For Design Projects

#6

Why not just link directly to the Pixelapse website? Does TechCrunch deserve to be a middle man for every startup?

Why not indeed: https://www.pixelapse.com/ - especially since TechCrunch have a broken link, and pixelapse haven't thought to redirect it.

Re: Pixelapse (YC W12): GitHub-Style Sharing and Version Control For Design Projects

#7
The largest plan has 9 collaborators, which seems rather prohibitive.

As a dev I often had to tweak my designer's assets. For example, fixing the 9-patching for Android or removing bad whitespace. Could I offer these changes in a pull request?

Re: Pixelapse (YC W12): GitHub-Style Sharing and Version Control For Design Projects

#8
post #6

Why not just link directly to the Pixelapse website? Does TechCrunch deserve to be a middle man for every startup?

Why not indeed: https://www.pixelapse.com/ - especially since TechCrunch have a broken link, and pixelapse haven't thought to redirect it.

Just caught that - it should redirect now.

Re: Pixelapse (YC W12): GitHub-Style Sharing and Version Control For Design Projects

#9
I'm curious to see how the whole 'forking/cloning' concept is replicated here, especially if Pixelapse is seeking to become the Github for design. I'm fairly certain that the restrictions for use of graphic content in a public format is a lot more prohibitive as opposed to software (there's not really such a thing as 'open-source graphics' besides measly clip art galleries).

The true social value of Github is in its community-oriented approach where any developer anywhere can fork code and contribute changes. That doesn't seem as possible with imagery, and my impression is that designers are more concerned with protecting their work (nothing wrong with that - just an observation).

Re: Pixelapse (YC W12): GitHub-Style Sharing and Version Control For Design Projects

#10

The largest plan has 9 collaborators, which seems rather prohibitive. As a dev I often had to tweak my designer's assets. For example, fixing the 9-patching for Android or removing bad whitespace. Could I offer these changes in a pull request?

Hi hannah, We'll work with you if you have larger needs. Please get in touch: hello@pixelapse.com

With regards to changes made to assets, they sync automatically between your machine and your designer's.

Post reply on HN