Bynder vs. Perforce P4

We have numerous renderings for some of our properties that are constantly being updated. It was hard to keep track of the most current rendering since it lived in multiple locations with various employees. Creating a central location where we can regularly update the renderings without having to add a new file and re-upload solved the issue of questioning whether the rendering you were looking at was correct.

Incentivized

While Perforce Helix is the best version control software out there, it can also be used to track your documentation, training videos and materials, and requirements. If you have strict compliance requirements, it can be used to ensure that those requirements are satisfied. Perforce Helix is incredibly flexible and can meet the needs of individual users as well as companies with thousands of users.

Incentivized

• Extracting content is where Bynder shines. My previous EverNote account reminded me of the last scene in Raiders of the Lost Ark -- warehouse full of stuff where clearly everything was lost once it was put in there. Bynder makes it easy to find and extract information especially because of the thumbnail views aided by the categorization tools. Since you can use these in combination everything is basically a complex Boolean search without needing to know how to write a complex Boolean Search.
• Easy I/O. Getting information into and out of Bynder is really easy -- follows the "don't make me think" rule. visual cues and clear buttons, etc. In fact, since I use multiple systems, I find it easiest to actually do file transfer TO MYSELF via Bynder rather than download or email files between my PC and Mac for example. That's how easy it is.
• Categories, tagging, last-used, most-frequent, hide/show -- there's a lot of flexibility in organizing your content. Technically, this kind of thing exists in every tool I've ever used... but it's the implementation that matters. UI design is vital to making this a valuable tool as opposed to a dreary step of "file retrieval".

Incentivized

• The branching mechanisms in Perforce allow for an enormous codebase to be duplicated into release versions weekly with little impact upon things such as the speed of queries against the version control.
• Action triggers permit such things as automated builds of software versions, dynamic messaging when issues are identified either within or prior to a build process, and much more.
• Locking provides the ability to prevent modifications of stable, tested versions in order to ensure validity when they are released.

Incentivized

• Link Sharing: One thing I wish Bynder had was quick link sharing for images or collections of images to share outside of Bynder. Currently you have to create a collection and send it via email to the person you want to view it. Otherwise you can make it public and share a link but then that collection technically can be viewed or downloaded by anyone. Since I'm used to the functionality of Dropbox, this is one thing that I feel is lacking.
• Public Media Center: Along the lines of the last comment about link sharing; one thing that would be helpful is a public media center. If we were able to tag what photos we would want to include there, along with downloadable logos, guidelines, PR, etc. There are workarounds but the functionality doesn't quite exist.
• Automatic Translations: We opted to keep all of our metadata and tagging in English, as most of our International partners do speak some English; however, it would have been nice to have an option to automatically translate any metadata/tagging for certain languages. We did have the option of automatically translating the main menu buttons but that wasn't much help. If we wanted metadata/tagging in other languages we'd have to input it manually for thousands of assets.

Incentivized

• Perforce tends to feel backwards in how it approaches certain tasks, like branching and integrating - even once you figure out how it wants you to perform these tasks, you will likely forget when it comes around to the next time you need to do them again.
• Perforce has a higher price tag, comparatively.
• Perforce make some tasks very easy, and yet other tasks very difficult - it doesn't always seem to have found its target user's proficiency.

Incentivized

We are fully committed to our use of Perforce. It works well within our organization and our desire to share our code base with our customers. Their support staff are responsive, inquisitive, and eager to improve their software. I feel like we have a direct line to their design/feature team as they often solicit our feedback.

Incentivized

I give it the rating because the filtering system is an efficient way to search and it seems like everyone regardless of age would be able to understand this function of how to locate assets. For average users they will mostly just use it to search and download assets so they don't need to learn everything about it but as long as the designers know the usability better it should not be an issue.

Incentivized

With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!

Incentivized

In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.

Incentivized

When we were getting ready to switch vendors, WebDAM wasn't very responsive to my questions or my needs. They also sent me all the files on an external drive that was formatted for Mac and didn't even think to verify whether I had a PC (which I did) so the external drive was useless and I had to wait another week to get the updated external drive that was formatted for a PC that I could then use.

Incentivized

I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.

Incentivized

This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.

Incentivized

My team chose Bynder as it is not my role to decide these things, but it was chosen so that we would be able to send large files and packages to outside organizations like vendors. It was also a matter of storage limitations with OneDrive as we were bound to run out of space as the organization grows. Bynder allowed us to not need to worry about storage.

Incentivized

Git is great, I love Git. But it's not great for dealing with binary assets, even when using Git LFS. Locking is not as simple as on perforce. Git presents some problems on using for non-tech people it can get overwhelming and tech people have to come by and help.

Incentivized

• More polished and compelling national marketing pieces due to greater and better use of photos.
• More polished and compelling regional marketing pieces due to regional staff members ability to access assets directly and select from full bank.
• Greater efficiency when designing pieces (easy to share assets with external designers).
• Increased use of marketing assets across regions due to sharability.

Incentivized

• Decreased our implementation costs by allowing versioning and back out of customizations made in the field.
• saves developers time through automation of changes between branches - they think less of the plumbing and have more time to write code.
• Downside is training/managing expectations of new developers who come in assuming they will use Git.

Incentivized