Bridge to no where...

Adobe Bridge wasn't upgraded with the Creative Cloud 2015 update. The last time it was updated, the main change was removing the Output module – which for many of us was the only reason to use Bridge. So obviously, either:

  1. Adobe is going to let Bridge die a quiet death.
  2. Adobe is going to replace Bridge with something more useful.

It's important to remember that Bridge was created to be a replacement for a file system. I always felt Bridge was intended to be a trojan horse – a way of providing a single file browser for Adobe customers regardless of whether they were on Macs or PCs. That customers would (hopefully) prefer the Adobe "operating system" for the native one. To entice users, they included features for server-based version control (Version Cue), a stock photo service and more. But the app was slow and unweildy. And no one that I know really used it.

Technology has changed a lot since Bridge debuted. Bridge was designed for a world where workgroups collaborated with servers, not clouds. Now, Adobe's switched to a cloud-based system. Creative Cloud is the only way to purchase most of Adobe's products and many of their new features leverage the cloud.

I assumed that Adobe was letting Bridge die. 

Lately though, I've been experimenting with the file storage features of Creative Cloud and it's reasonably powerful, simple and straightforward. Most of the file management is handled in a web interface, but as the file storage and collaboration features of Creative Cloud grow, I could see Adobe building a new "Bridge" – one that was built from the ground up in the cloud era. 

Maybe having a web app to tie it all together is enough. The web app isn't bad, but it feels detached from the software. A native app would be much more powerful and user friendly.

(Desktop development is different than mobile development, but for what it's worth, Adobe's new Creative Cloud iOS app has a handful of the features that a mobile Bridge would need.)

The nice thing about Adobe Creative Cloud distribution model is that they can update an app or introduce a new app at any time. So Adobe doesn't have to wait until Creative Cloud 2016 to update Bridge. That said, every update that doesn't include a new version of Bridge sends a very specific message: Adobe's Bridge is going no where...