Over the past many years I lead software development teams that produced commercial-ready software. In order to track revisions we always used source control tools like MKS, Git, and SVN. Without it, chaos would erupt when a prior version couldn’t be rebuilt for testing or customer support.
Versioning has served as a “safe haven” historical record of all of the intellectual property associated with software builds. (Not to mention that version control was typically mandated in customer agreements.)
For software developers, using these tools to manage software source code and other artifacts took some learning once you memorized the commands:
Not exactly intuitive!
Although we had an idea of what the perfect versioning app would need to do, I decided to write my fifth book called Version Control for Creative Professionals that attempted to simplify how non-programmers could use Git (a very popular shareware versioning tool):
After writing and illustrating over 50 pages I simply stopped. Attempting to simplify the complexity of Git was more difficult than I thought. Great for software engineers, not so great for creative professionals. Rather than design outward with a host of features hoping customers would like it, I took the opposite approach.
So, that's dandy. What's the catch? There's only one. It is the customer's responsibility to make sure that all of a project's assets (files, directories, ...) reside under one project folder. That's it. (By the way, Git and SVN require the same thing.)
Being a programmer, I designed the app in late 2012 while on an extended trip back in Asheville, North Carolina. The initial working edition was completed in Seattle, Washington.
So why hasn’t it been released? We’ve been doing testing, testing, and even more testing. (A versioning app that safeguards your digital stuff must be completely reliable.)
* Separate Spresso iVersionIt licenses are required for macOS and Windows
CONTACT US ABOUT