Hello Patrick,

That's interesting and is also one we have on the list that users have asked for.  So will this be a single plugin that allows the user a choice or two seperate plugins?

Regards

Paul

HI Paul,

That's a question I've been asking myself.  Right now, I'm leaning toward making separate plugins.  The disadvantage to putting them together would have to do with the complexity of the program itself (more user options/selections to keep track of, separate pieces of application logic to connect to the different services, etc.).  Can you think of specific advantages of having them together in one plugin, other than simplicity of installation?

Hi Patrick,

I think the advantage is all the users, so they only have to install a single plugin to get both providers.  But if they only wanted one they may prefer seperate plugins in the first place, so it's probably six of one and half a dozen of the other.

Supporting it would probably get more complex as you say, so keeping them seperate might be better.

Regards

Paul

Hi Patrick,

I think the advantage is all the users, so they only have to install a single plugin to get both providers.  But if they only wanted one they may prefer seperate plugins in the first place, so it's probably six of one and half a dozen of the other.

Supporting it would probably get more complex as you say, so keeping them seperate might be better.

Regards

Paul

Hi there,

Great to see this one! Just to chime in from a product management perspective - I think I would also prefer the separate solution. This will also mean you can "sell" it more prominently by not having to refer to a joint plug-in and potentially muddying the waters/confusing users. So it seems to be the cleaner solution all around to have a separate plug-in.

Thanks,

Daniel

Thanks for the feedback, Daniel and Paul.