What's the best design to follow for this API in this case?

Question

I'm building an API that post a given message to different platforms (Twitter, FaceBook...).

The problem is that for each platform I may change the wrapper that allow me to post the message. For example, in C# I can post a message on twitter using the yedda API or the CsharpTwitt API, for FaceBook I'll use others APIs...

Hence, I have to be able to use different wrappers to post a message for each platform.

For now, this is the design I use, but it's clear that it will be too complicated if I add more APIs with more wrappers.

I think it's a common design issue and I'm wondering

1. Am I using the best approach to have a well designed API?
2. Otherwise, what is the best design for such a situation?
3. What design pattern is applicable here?

Answer 1

I like this approach because this way you can dependency inject whatever wrapper you wish and change it with a single line of code.

For example

Bind<Yedda>().To<ITwitter>();
Bind<FBWrapper>().To<IFacebook>();

And now throughout the code ITwitter actually maps to the Yedda wrapper.

Dependency injection could be something worthwhile to look at.

Answer 2

you may use abstract factory if your create different message wrappers.

abstrcat class Abstractfactory{
       IBridge Create(int type);
}
class Platrofrm1facroty:Abstractfactory
{  
  //type m.b. for Wrapper1 to wrapperN 
  IBridge Create(int type);
}
class Twitterfacroty:Abstractfactory
{  
  //type m.b. for Yedda or CshartTwitt
  IBridge Create(int type);
}