Skip to main content

The Missing Link in Social media




In India there is a famous saying, 'Not all fingers on your hands are of the same size.'  It simply suggests that no two human beings are same. We all think differently, we all have different aspirations. When it comes to social media sites, the world is roughly classified as the battle between Facebook, twitter and Google plus.

I have repeated this since beginning, Social media is not new, people were social like this before. If human being is nothing but only social. We used to gather around bonfire, gather near water cooler, people used to bond together in the rock concerts, they bonded in favorite bars. They did talk about brands and advertise there too. With the advent of computers, people have started channeling their energy on the computer. They do things online, why? For one, you can bond with freakishly high number of people that you can physically meet.

Every day some start-up does a special feature in some online tech magazine about what these social network are missing. Everyday someone writes what the current social network lacks and how it can be fixed. But I believe we all are making one big mistake, we are putting twitter, facebook on the same page, which infact is misleading.

A rough analysis of social activities indicates the following traits in social users.

1. People who use twitter are creators, active agents who like to broadcast things irrespective if someone reads them or no. They are not so keen on knowing what their friends are up-to and prefer living in the moment. The twitter crowd accepts everyone. At the same time, it does not stop for anyone.

2. People on Facebook are closed, they tend to form small comfort zone and prefer to stay in them.

There are different types of social users and they haunt different places in different social network. Bringing them all together can be fatal and disastrous. The point is not to hunt for flaws in the social network and go on and build one for yourself. Google tried that, I wonder how many people actually like it?

The creator won't like it because its too heavy to understand, to channel creativity there should be freedom from expression, this can be evident for the fact that many twitter users still are fine with old twitter with no fancy animated graphics and stuff.

The normal facebook users have already build their comfort zone and won't be comfortable for moving out until and unless their comfort zone moves out.

Instead of creating more and more social networks we should try understand each other. There is no point in creating a separate social networks for communities. You cannot make people from twitter join facebook unless of course you threaten to kill a puppy if they don't. You cannot make people from facebook use twitter, their twitter account will lie dormant even if they create.

The strategy you design for both these networks should not be same, while on twitter, updating a status once in a day may not be as effective on facebook regular updates can amount as spamming. Again, customers on facebook would want freebies and stuff but people on twitter would like to engage in conversations. You cannot stereotype people on twitter as your customers and use it as a advertising medium. You have to fold up your sleeve and get in the mud if you really wish to connect.

It is very impolite to intrude in the personal space of a person, before doing it, always and I repeat, always LISTEN to them first. Then you may make your move.

What do you think?

Toon Courtesy: www.theholycow.co.in

Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…