Uploaded January 2025 | Updated September 2026, 2 weeks ago
When it comes to delivering a complete software product, there are many steps in the process that have nothing to do with the code of the plugin itself, but are just as crucial.
One of these is building installers and notarizing them so downloading your plugin is frictionless for the customer. The process for doing this is different between Windows and Mac, and you’ll need different build machines to create the installers, as they’re mutually incompatible.
Working through this whole process can seem a bit tedious—especially for those newer to the industry—but there is a way to streamline it, called a CI (continuous integration) pipeline. This automates the process of building installers and code-signing, among other useful benefits.
To learn about more about the challenges of building a successful audio plugin, check out our discussion of it on YouTube here:
youtu.be/ovEAHXUFP7U
When it comes to delivering a complete software product, there are many steps in the process that have nothing to do with the code of the plugin itself, but are just as crucial.
One of these is building installers and notarizing them so downloading your plugin is frictionless for the customer. The process for doing this is different between Windows and Mac, and you’ll need different build machines to create the installers, as they’re mutually incompatible.
Working through this whole process can seem a bit tedious—especially for those newer to the industry—but there is a way to streamline it, called a CI (continuous integration) pipeline. This automates the process of building installers and code-signing, among other useful benefits.
To learn about more about the challenges of building a successful audio plugin, check out our discussion of it on YouTube here:
youtu.be/ovEAHXUFP7U
