Plugins & Connectors

Third-party product integration

In ecosystem integration, seamless connectivity facilitates communication and interaction between third-party components.

This introductory guide aims to clarify the distinctions among the two main types of software connections: plugins and connectors (aka applications).

1. Plugins

• Plugins are software components designed to extend the functionality of a more extensive application. They allow developers to add specific features or behaviours to an existing software system without modifying its core codebase. Plugins are usually loaded dynamically at runtime, making adding or removing them easier without affecting the main application's stability.

• Plugins provide a modular approach to integration, enabling third-party developers to seamlessly integrate DAM into the host application/software. Simply use our Media Asset Widget to replace or complement the media gallery used by the third-party software/tool.

2. Connectors (Applications)

• Applications, also known as standalone connectors or adapters, are complete and self-contained entities designed to perform specific tasks or provide a range of functionalities to users. Unlike plugins and libraries, applications are intended to be independent and tightly integrated.

• Our applications have user interfaces (UI) and may interact independently with other applications or services. They will always perform a range of additional functions, such as programmatic synchronisation and similar advanced features.

In summary, plugins extend the functionality of existing applications with a more passive role, while applications/connectors facilitate interoperability and seamless synchronisation between different systems by being placed in between them and actively intervening.

A manual integration will always be possible using our Media Asset Widget, whose code/package is linked in this documentation.