Adobe Bridge is a creative digital asset manager that lets you preview, organize, edit, and publish multiple creative assets (including Adobe Photoshop, InDesign, Illustrator, After Effects, and Dimension files) with thumbnails and rich previews.
Edit metadata. Add keywords, labels, and ratings to assets. Organize assets using collections, and find assets using powerful filters and advanced metadata search features. Collaborate with Libraries and publish to Adobe Stock from Bridge.
N/A
Adobe Experience Manager
Score 8.4 out of 10
N/A
Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
Adobe Bridge is a useful tool within the CC environment but doesn't have much standalone value that I use it for outside of organization of assets and the preliminary asset selection process.
Okay so I've actually tried to use Lightroom. Photoshop is its own beast and doesn't have the catalog that Bridge of Lightroom has. Lightroom is not as powerful with being able to check between images, finding files, etc. I wanted to love it, but Bridge won hands down with all …
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with …
Adobe Experience Manager is what I use most frequently. While the other tools I listed above are important, they are ultimately a secondary tool utilized on a need by need basis where as AEM is what we use daily for content creation, content updates, content optimization, etc.
AEM is comparable to Sitecore and less agile than Bynder, but Adobe products were already being used across the org and adding AEM allowed us to link it all together.
I love to use it when I need to rename a group of photos from one of my photographers because they named the files incorrectly. My team seems happy to use it from now and then in combination with InDesign and Photoshop
I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
It took me a while to figure out how to get Bridge to work faster. Apparently, you need it to cache your entire library and once that library is cached then it can refer to those files quickly.
It takes up more space on your computer and you should consider buying a computer with plenty of space and a great graphics card to help this program work at its best.
I wish it would recognize that firewall software and virus protection software isn't its enemy and work with them running all the time. This error doesn't always occur for me, but when it does, I am annoyed.
easier way to make universal changes for multiple websites at a time (ie pushing out a new experience fragment to all as opposed to having to individually add to each site)
easier way to get site images to look and be sized exactly as I want directly from the site page editor
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
Adobe Bridge is useful as a jumping off point for file organization within the CC environment. It is a little slow and clunky at times but is useful for preliminary photography selection development including contact sheets, file renaming, and the overall selection process.
Sure there are a few quirks in the interface, but once you learn them, building and editing pages is fast and efficient. Once you have the content and the planned design decided (how the pages will look and which components you will use), page builds and publishing are quick. I was able to build a 10-page specialized site with cards built using the list component in an afternoon
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
Okay so I've actually tried to use Lightroom. Photoshop is its own beast and doesn't have the catalog that Bridge of Lightroom has. Lightroom is not as powerful with being able to check between images, finding files, etc. I wanted to love it, but Bridge won hands down with all the time it has saved me so I can get back to my children instead of complaining that it takes me so much time to narrow down images
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
