{"id":16713,"date":"2010-12-02T09:35:36","date_gmt":"2010-12-02T16:35:36","guid":{"rendered":"http:\/\/blogs.adobe.com\/jnack\/?p=3307"},"modified":"2010-12-02T09:35:36","modified_gmt":"2010-12-02T16:35:36","slug":"what-if-dropbox-offered-time-tracking-versioning-more","status":"publish","type":"post","link":"http:\/\/jnack.com\/blog\/2010\/12\/02\/what-if-dropbox-offered-time-tracking-versioning-more\/","title":{"rendered":"What if Dropbox offered time tracking, versioning, & more?"},"content":{"rendered":"

Answer: You’d have something like the just-released GridIron Flow 2.0<\/a>. \u00a0It can save your butt, for free. Why would you not start using it immediately?<\/p>\n

The company has radically redefined what was already a unique & very powerful piece of software, enabling file sync & collaboration on top of automatic versioning. \u00a0Oh, and instead of costing a couple of hundred bucks per seat, it’s now free (!), with paid upgrades if you need more capabilities. \u00a0Read on for details.<\/p>\n

I praised Flow 1.0<\/a> as being like an airbag, staying out of your way until it saves your bacon–by automatically versioning your files (think realtime Time Machine, with beautiful Adobe integration). \u00a0Trouble is, because the app is so unique, it’s sometimes hard for people to wrap their heads around & pay for up front.<\/p>\n

The barrier to entry, however, is now zero.<\/p>\n

The free product, Flow Essentials<\/strong>, tracks all files in a creative project and displays them in a visual map<\/a>. You can now define projects and identify teams of people that will be part of the workflow. Flow 2 Essentials enables realtime collaboration, enabling users to add notes<\/a> to nodes on the map, and to send emails (linking recipient to the node on that map) to the team or a subset of the group. The map allows you to see who worked on each asset, the size of the asset, and any attached notes.<\/p>\n

This is all provided, along with 4GB of online Overflow storage (the Dropbox-style part), for free. \u00a0Unlike Dropbox (of which I’m a fan, by the way), Flow doesn’t require moving assets into specific folders; you can move and rename them while staying synced.<\/p>\n

They also offer three premium services, each for $10\/month per user, or $20\/mo.\/user for all three (no contract required):<\/p>\n

    \n
  1. Time Manager<\/strong> allows you to review the time you have invested on each asset, and provides a control feature to allow amortizing total time across multiple projects. It also displays percentage of time spent in each creative application and offers a manual entry mechanism that allows you to include time that is not file based (e.g. design & client meetings, phone calls, etc.).<\/li>\n
  2. Versioning<\/strong> enables automatic file versioning & allows you to lock, delete, branch or drill down on any specific version. Versions are saved locally by default.<\/li>\n
  3. Overflow<\/strong> shares not only the asset but versions of that asset as well. The premium service adds 50GB to the 4GB of storage provided for in Essentials.<\/li>\n<\/ol>\n

    Why am I promoting this app? \u00a0Do I or Adobe get some kind of kickback for sales? Nope. It’s just that having been a Web designer in a big agency, I know the pain of lost\/overwritten files & the drag of filling out timesheet. \u00a0What’s it worth to help fix those problems? \u00a0More than the cost of a few coffees a month, I’m guessing.<\/p>\n

    If you take Flow for a spin, please share your impressions via the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Answer: You’d have something like the just-released GridIron Flow 2.0. \u00a0It can save your butt, for free. Why would you not start using it immediately? The company has radically redefined what was already a unique & very powerful piece of software, enabling file sync & collaboration on top of automatic versioning. \u00a0Oh, and instead of […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/16713"}],"collection":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/comments?post=16713"}],"version-history":[{"count":0,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/16713\/revisions"}],"wp:attachment":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/media?parent=16713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/categories?post=16713"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/tags?post=16713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}