Why Social Networks Are Monopolistic By Nature?

Social networking has been the hottest area after the dot.com burst. User base is still a critical factor and far more sticky than before. It’s the connections among these users that differentiate social networking from other types of Internet services.

A connection is formed from one user to another. They cannot be on two different web sites, even though theoretically they can. Technically we can define protocols to link users, even groups, together from different sites. But it is not efficient and may not be fast enough to sync up states and discover new connections. Even more issues on business side, not to mention privacy policies.

So the reality is that once a site gets critical mass, there is no chance for others. Think about the competition between Facebook and MySpace. Intend it or not, monopoly is a natural result.

But it doesn’t mean there is no more chance. You got to think differently.

Unlike enterprise customers who prefer one vendor to take care of everything, individual users would like to divide their lives into different aspects and go with one site for each aspect. After all, no one wants one site to know everything.

With one aspect, however, you don’t like to deal with an extra site as long as the one in use is good enough. So there is no chance for latecomers unless the monopoly site makes a big mistake itself. Such a mistake could happen from time to time. That is why Google invests in its Google+, hoping one day Facebook will make a mistake and it will then take lead.

Now, I think it’s clear that new entrepreneurs who are interested in social networking business should look for new aspects, not compete with incumbents.

Update: Sam Johnston (@samj) sent me a link to his article Infographic: Diffusion of Social Networks — Facebook, Twitter, LinkedIn and Google+. Nice reading!

This entry was posted in Others and tagged , , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

  • NEED HELP?


    My consulting helps clients with virtualization and cloud computing, including VMware infrastructure automation and orchestration, vSphere management APIs, and deep product integration with hypervisors. Current training offerings include vSphere APIs training, vCenter Orchestrator training, and etc. Should you, or someone you know, need these consulting services or training, please feel free to contact me: steve __AT__ doublecloud.org.

    Me: Steve Jin, VMware vExpert who authored the VMware VI and vSphere SDK by Prentice Hall, and created the de factor open source vSphere Java API while working at VMware engineering. Companies like Cisco, EMC, NetApp, HP, Dell, VMware, are among the users of the API and other tools I developed for their products, internal IT orchestration, and test automation.