Output module should be integral to Bridge CC

  • 4
  • Idea
  • Updated 3 years ago
Having to download and install the output module every time there's an update to Bridge is a burden on your customer. Why isn't it part of the Bridge software like it used to be?
Photo of Brant Louck

Brant Louck

  • 2 Posts
  • 1 Reply Like
  • I feel like Adobe doesn't like me

Posted 3 years ago

  • 4
Photo of aaron dougherty

aaron dougherty

  • 38 Posts
  • 7 Reply Likes
Agreed.  Why is this a problem?
Photo of Brant Louck

Brant Louck

  • 2 Posts
  • 1 Reply Like
It's strange to have one of the fundamental functions of a piece of software be available only as a plugin, when it used to be integral. Imagine if Adobe suddenly decided to remove photoshop's ability to save a psd as a jpg. But offered that functionality as a plugin you could download.
Photo of Peter Moloney

Peter Moloney

  • 103 Posts
  • 34 Reply Likes
I couldn't agree more!
Not only is this a real time consuming pain to do each time, but it isn't even simple.
I'm old enough to remember installing individual plug-in components but few are familiar with this sort of thing nowadays.
I assume (perhaps someone in Adobe can actually enlighten us) the problem is that Bridge is incredibly old code and needs a total rewrite - and on the other hand it isn't used by many, and therefore Adobe can't see a way to make money out of it, and therefore it's on the "back burner"
This is only how I see it - I would love someone at Adobe to map out the future of Bridge.
For me and MY work Bridge is the hub of everything I do "all day every day".
Please Adobe move Bridge forward!