Hi, @Carson Jones; as Lumigraphics stated, this is not the location where Adobe wants suggestions coming into. This is because THIS location is primarily focused on people asking questions about how things work (or are not working). Some Adobe engineers do monitor this space, but the primary eyes looking for things here are folks like Lumigraphics and me, who are not Adobe employees. Trust me; you do not want to depend upon Lumigraphics or myself to get your ideas into Adobe — we have no better access than you.
As far as making requests, please understand that it's not as if the Adobe engineers sit around all day wondering what to do next. They have multiple lists they draw upon to work from. These include:
- Keeping up with changes in both Mac and PC updates and changes
- Mandated changes to software based on what other companion software is doing (e.g., features in PS that Bridge needs to work with)
- Getting rid of crashes
- Getting rid of bugs
- Vital updates to the software
- Important updates to the software
- Good idea updates to the software
In all of this, the software Product Manager has to determine what can be done with the "currency" (aka engineer's time) he has to work with. It can't be greater than 100%. By this, I mean that if it's determined that solving the first three items above will take 80% of the engineers' time, that doesn't leave much time for the bottom four items.
The one way that things "can" slip in is if they do not require an exordinate amount of time to do. These are known within Adobe as JDI projects (Just Do It). These are best possible when you have a large extended group of engineers to work with. From all accounts I've heard of, the Bridge team is small, even by Adobe standards, so the option for Bridge to do any JDIs is very limited.
Lastly is patience. When Bridge first came out in 2005, I and a number of other folks were begging for there to be tabs in Bridge. 17 years later, we finally got tabs. What we actually got was not what we expected.
I took the time to write all this because this whole process is not well understood by many folks (or even known about). I've been closely involved in software development since 1985, and despite different companies, different-sized engineering teams, and different countries, the overall process and issues tend to be fairly similar. The one big big difference is the size of the company. The smaller the company, the fewer people they have to answer to, and the faster the engineers can develop. Big companies have more people to answer to, and that does slow things down. However, the issues I listed above still apply.
So, settle back; it's always a bit of a bumpy ride.
8
Replies
AdChoices