It is difficult to manage plugins and dependencies within Mautic
Currently there is no easy way to manage plugins within Mautic, or their dependencies. This makes it quite difficult for the end-user to install new plugins, and is also restricting the growth of our ecosystem as the process is so complex.
Changes to plugins are coupled to Mautic releases
We are restricted in making changes or updates to plugins which are shipped with Mautic because they have to fit within the release cycle of Mautic itself. An issue might only affect a very small subset of Mautic users who actually use that plugin, but we have to ship the fix to every user of Mautic rather than every user of the plugin.
Mautic Core is bloated by plugins that are not widely used
Mautic itself is quite bloated and complex due to the number of plugins that we ship with the core product, whereas if we had the architecture to support a decoupled approach to plugins we could streamline the product significantly. This would also mean that we could easily empower smaller teams (e.g. Tiger Teams) to support specific plugins and make updates much more quickly.
Read more in John Linhart’s proposal about the Mautic Marketplace here.