Products can be beautiful and delightful, but I'm not sure it's meaningful when you call your own product beautiful and delightful.
Meaningful, maybe not. Having a desirable marketing effect? Probably.
Show HN: Sync Done Beautifully
11–20 of 27 posts
Re: Show HN: Sync Done Beautifully
#12Is the icon supposed to have a psb extension? It looks like a typo.
It's for files over 2GB. So referencing 500mb files confused me a bit, too.
Re: Show HN: Sync Done Beautifully
#13Earlier quoted context omitted.
Hey, one of the founders of Pixelapse here. For context, our target demographic is graphic designers. We initially started out with tiered pricing based on storage. However, based on usage, we actually found that people rarely hit their storage caps. A better barometer for us is the number of people working together, which we approximate with projects. In that regard, our pricing plans are similar to Github's. Public…
What products would you say are comparable to yours? Perforce comes to mind, though that's more of a "check out, check in" model, where this appears to be more of a dropbox model? I'm not understanding how a version is identified, though. Is a version stored on the server every time the file is saved? I don't see anything about locking. How do you prevent two people from working on the same unmergeable file at the sa…
I'd say the model is most comparable to Dropbox in that it passively syncs your work in the background. The check-in, check-out approach works for developers but we found it to be too confusing for our target audience of designers. It's a bit of cognitive overhead to remember to constantly check-in, especially when using Photoshop, which crashes quite frequently.
Every save forms a new version online, but you can go back and retroactively mark certain versions as major milestones. Milestones are roughly equivalent to commits in Git.
Since we're primarily focused on graphic design formats, we don't attempt to do any merging of files since it's unclear that the end product would make much sense. We don't lock files either. If two users simultaneously edit the same file, one of them "loses" and shows up as a Conflicted copy that you can visually resolve in the Comparison view online.
Re: Show HN: Sync Done Beautifully
#14Earlier quoted context omitted.
Hey, one of the founders of Pixelapse here. For context, our target demographic is graphic designers. We initially started out with tiered pricing based on storage. However, based on usage, we actually found that people rarely hit their storage caps. A better barometer for us is the number of people working together, which we approximate with projects. In that regard, our pricing plans are similar to Github's. Public…
What products would you say are comparable to yours? Perforce comes to mind, though that's more of a "check out, check in" model, where this appears to be more of a dropbox model? I'm not understanding how a version is identified, though. Is a version stored on the server every time the file is saved? I don't see anything about locking. How do you prevent two people from working on the same unmergeable file at the sa…
[deleted]
Re: Show HN: Sync Done Beautifully
#15Earlier quoted context omitted.
What products would you say are comparable to yours? Perforce comes to mind, though that's more of a "check out, check in" model, where this appears to be more of a dropbox model? I'm not understanding how a version is identified, though. Is a version stored on the server every time the file is saved? I don't see anything about locking. How do you prevent two people from working on the same unmergeable file at the sa…
I'd say the model is most comparable to Dropbox in that it passively syncs your work in the background. The check-in, check-out approach works for developers but we found it to be too confusing for our target audience of designers. It's a bit of cognitive overhead to remember to constantly check-in, especially when using Photoshop, which crashes quite frequently. Every save forms a new version online, but you can go…
If two users simultaneously edit the same file, one of them "loses" and shows up as a Conflicted copy.
From my perspective, that seems like a good feature to consider adding. Groups of artists are used to self-organizing so they don't end up conflicting in this way, but I think that's only because they haven't had tools to solve the problem for them. We're rolling Perforce out enterprise-wide, and trying to convince artists to start storing their working files in it (PSDs, etc) -- one of the big selling points is that you can easily see that someone else is working on this file before you jump in.
Re: Show HN: Sync Done Beautifully
#16[deleted]
Re: Show HN: Sync Done Beautifully
#17Products can be beautiful and delightful, but I'm not sure it's meaningful when you call your own product beautiful and delightful.
Meaningful, maybe not. Having a desirable marketing effect? Probably.
I don't know about that. It's certainly becoming a trite way to describe your product.
Re: Show HN: Sync Done Beautifully
#18The landing page loads a whopping 6 MB of assets, the culprits particularly being two images at 3.2 and 1.8 MB. It was definitely not a fun experience on my lowly mobile network connection.
Re: Show HN: Sync Done Beautifully
#19Earlier quoted context omitted.
Nop, it's a reference to Photoshop's Large Document Format. [1] [1]: http://helpx.adobe.com/photoshop/using/file-formats.html#lar...
Cool. It's been a while since I've used Photoshop on a regular basis, so I'm out of the loop. It just seemed odd given that psd is used directly underneath the icon.
Since I've know about it, I've liked the extension because in .PSB, the B is for big.
Re: Show HN: Sync Done Beautifully
#20Products can be beautiful and delightful, but I'm not sure it's meaningful when you call your own product beautiful and delightful.
Agreed. Even if "beautiful" is a foundation of a company's strategy, I like it when they show me what I can do, and let me notice how beautiful they've made it.