If you use the word “integration” or “compatibility” with a seasoned plugin developer, chances are you might make them flinch. You can’t blame them. More often than not, these terms bring to mind an inbox laden with emails asking for compatibility with one plugin or another, day in and day out.
But what’s the big deal?- you ask. You, the proud developer of a newly released plugin, would kill to have an inbox full of customers. You would gladly trade places.
Well, the fact of the matter is that the prospect of an integration can be daunting. It means a plugin developer may have to become familiarized with a codebase that falls far short of their own standards (we all know what open-source, at its worst, can lead to). After that, resolving the compatibility issue in question ranges from cakewalk to descent into the underworld. Usually, it’s somewhere in between. The last step, of course, is to get back to the customer in question. Imagine the battle-tested plugin developer’s remorse when, on occasion, they never hear so much as a peep from that customer again. Sure, the resolution to this issue may pay dividends in the long-run, but as the veteran developer knows full-well, there is no guarantee of that.
In a word, ensuring your plugin plays well with others is no joke. That’s why you don’t hear many old-timers advising folks to make integrations and compatibility a focus, or at least that’s my hypothesis. But regardless of whether my suspicion is true or not, the fact that this is a neglected growth lever is beyond dispute. You don’t need to take my word for it either. Just ask Chris Lema, who recently stated as much in one of his blogposts (which I briefly covered in WooWeekly).
The message is simple: it pays well to ensure your plugin plays well with others. Even if that sounds like bad poetry to you, it’s true.
Continue reading WordPress: Growing Your Plugin (Part 2: Integrations)

