Dom's First Architecture Diagram

So what if not everyone wants to visit a Retailer’s, Reseller’s, or, Referrer’s web site to fill out some widget? What if not everyone wants to communicate via email?  What if some people out there prefer other channels, like Twitter, text messaging (SMS), Facebook and of course mobile applications?

We (can) do that

In its infancy, AnotherSocialEconomy – called Twetailer, actually only worked with Twitter. The problem we had, was that some people found the short messages to be cryptic – like a programming language. So we decided to go multi-channel – which simply means, our users can choose their own method of communicating with us.

So while, we’re currently emphasizing the Widget as our Consumers’ starting point, a web console for the Retailers and email as our communication method, we can support other channels. Channels like Twitter, which provides us with free text messaging. A Jabber chat channel – like Google Talk and Apple’s iChat. Sort of like a command-line interface.

We also have open source client applications,  like an Android mobile app, Adobe AIR desktop app, a Widget and a Bookmarklet hat can be used as starting points for Consumer & Retailers.

So what’s the (Can) for? AnotherSocialEconomy provides an public REST application programming interface (API) which means that the developer community can create their own channel – like maybe Facebook. It also means they can create their own social economy powered by our engine.

For more technical information, please free to contact Dom.