New: Public Project Licenses
Hot on the heels of last week’s Public Projects announcement, we’re rolling out the ability to add a license to your work. This helps remove confusion and gives organizations explicit control over how they would like work to be used.
Open Sourced: AutoSparkle
Updating software is a pain. Troubleshooting bugs in applications still starts off with a check to see which version is causing the issue. Frameworks unnecessarily prompt users to install the latest update and restart. It frustrates users and opens them up to security vulnerabilities. It sucks. That’s why we’re releasing a small extension to the popular to Sparkle framework that allows you to silently and automatically update your application.
Introducing Public Projects
For a group of individuals who so loudly declare that design isn’t how it looks, designers really don’t know how to present their work. What we show off is the end of the process—the pretty picture posted to a portfolio website. Today we’re taking a step towards fixing that.
Introducing LayerVault Public Projects, a totally new way to share your design work with the universe.
Payment History
Point your browser at Organization Settings and you’ll see that we just added a Payment History tab. As the name suggests, you can now see the history of your payments to LayerVault.
The entire team tried unsuccessfully for several minutes to come up with puns about history and payments.
New Project Settings Pages
Last week, we released new account and organization settings pages. Today we’re releasing new project settings pages!
Now: 3 Free Observers
Observers are organization members who receive deliveries, leave feedback, and participate in the process without actually editing files. We recently started giving each organization 2 free observers.
We’re now increasing that to 3 free observers. If you’re an existing customer, you should see your next bill reflect this minor improvement.
This is Big: Billing Active Users Only
When we simplified our pricing from four tiered plans to a single per-user plan, we didn’t fully address the needs of teams who frequently work with outside clients. We’re fixing that today.
As of today, LayerVault will now only bill you for active organization members. If people in your organization aren’t in any projects, we simply won’t bill you for them.
We bill organizations for their members. Previously, customers would need to manually remove users from organizations when client-work was complete. This change our billing has two goals: Making billing simpler and fairer.
We expect that it’ll be great for customers who do client work, while also making LayerVault much more useful for customers across the board. It’s a small change but we love doing this kind of thing.
