Since last week’s launch, more people have started collaborating across organizations. Until now, we simply dumped both organizations’ projects on the All Projects page.
We just rolled out an update that cleans up the All Projects page if you’re part of multiple organizations. Enjoy!
A week ago we released forking and free accounts. A little less than a month ago we released public projects. Tons of designers have since created public projects, watched others’ work, and forked projects. We wanted to pause for a moment to look back at some of the great stuff created over the last few weeks.
We just pushed Project History live for all projects.
Project History allows you to go back through files you may have deleted and restore them. To access the Project History, just click on the “History” button located at the top of any Project Page. From this page, you can undo any erroneous deletion.
It’s just one more way we’re making design frustration a thing of the past.
Yesterday, we rolled out free accounts to LayerVault along with the concept of forking. The release had been several months in the making. But unlike most big launches, the pieces of this release were exposed over time. If anything, it wasn’t so much the big launch but one of the last launches in this thread of thought. After building LayerVault for nearly two years, we have realized that the best way to build a product is to release things piecemeal and to avoid the Big Launch.
For the past two years, LayerVault has been a paid-only service. It’s allowed us to stay focused on building a business that will be around awhile. Today, LayerVault is taking a leap towards becoming more accessible in three different ways: free accounts, forking, and lower prices.
Last year, we released LayerVault 2. This Tuesday, June 4, we’ll be making a big announcement. Mark your calendars.
We’re growing quickly at LayerVault and looking for a few good engineers to join us. We’re the most interested in Full-Stack engineers with a Rails focus or Cocoa developers.
Our mothership is in NYC, but you can be anywhere.
If you’re interested, please email email@example.com. Include your GitHub profile and a quick hello. We’ll take it from there.
Alternatively if you’re a technical recruiter looking to lend us your services, please email firstname.lastname@example.org immediately.