Friday, August 6, 2010

Google Wave is Dead

Yesterday, Google announced that they are discontinuing Google Wave product development. Lack of the user adoption was stated as the primary reason. Here is the excerpt from the blog post -

"But despite these wins, and numerous loyal fans, Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects."

I am very sad hearing this news. I liked Google Wave a lot and always used it for team collaboration and collaborative document management. Now I am eager to see what Google has to offer to migrate this content.

I also feel that Google Wave didn't pick up because of lack of proper promotion from Google. Google is always bad in promotion and lack of promotion is killing this great product. I hope they do it better in future.

I guess, they will migrate all the content to Google Apps. Some of the innovations like "character-by-character live typing" are already part of Google Apps, so it is safe to assume that Google Wave will be used in parts in Google Apps in future.

let us wait and see.

Saturday, June 12, 2010

What are users and weekly installs on chrome extension gallery

Recently we have created a chrome extension (Chrome browser plugin) from my Online astrology software named This means that all astrological details and charts are just one click away. If you are Chrome or Chromium user, you can install plugin - MyKundali Chrome Extension.  I am sure you will love it. Don't forget to share your feedback.

Though this post is not about the the astrology extension but the stats that it shows on the extension page. After two days when I go to the extension page, I found following figure "26 users - Weekly installs: 43"

I was wondering what exactly are the "Users" and how they are calculated. Weekly Installs looks straight forward. Though chrome extension website doesn't give any official information, this is the explanation of both the terms based on my understanding -

"Weekly Installs" Count
As the name suggest this gives number of installs in the last seven days. So if I have 43 installs, it means that 43 people installed my extension in last 7 days. Remember this is not an average, so two weeks can have altogether different values.

"Users" Count
This is computed from update pings in the last week, so this gives you active users in last seven days. Remember, this is also a weekly figure and gives good indication of how many people are using your extension.

By the way, you can also use Google Analytics for more accurate analytics. So if you are a Chromium extension developer, you must use it.

Wednesday, April 21, 2010

Klinnk – The PayPal of India?

Today I come to know that TimesOfMoney, the company behind many payment and money transfer services including, has announced According to the information –

“Klinnk is a revolutionary new way to manage one’s online transactions in India. Klinnk users could either be individuals or merchants looking out for a more safe, secure and faster way of processing online transactions.

Klinnk is a bank neutral offering to the Indian customers over Internet with many features like Klinnk on Mobile, IVR, SMS and Prepaid Cards to be rolled out in future.”

Like PayPal, there is no Setup or AMC (Annual Maintenance Cost). There is only TDR (Transaction fee) of 3.5%. Transaction fee looks in line with PayPal who charges “2.9% transaction fee + $0.30 USD.” Like PayPal they also have merchant solutions.

Let us wait and see how does it fair?

Death of Old School RT and New Rules of the Twitter Game

What is ReTweet
‘Retweet’ in Twitter is somewhat equivalent to ‘Like’ in Facebook. If you liked a Tweet or want to share it with your followers, you can Retweet it. ReTweet is also referred as “RT” in Twitspace. We can define ReTweet as “To repost another user's message on Twitter with giving credit to him”

Old and New School ReTweet
Initially ReTweets (RT in short) started as an extension to “Replies”. So if I have to ReTweet your tweet, I take your tweet, embed “RT @your-twitter-usrename” in the tweet and again Tweet it. The original author of the Tweet, can see the new Tweet in his Replies/ Mentions section. Later Twitter realized that it is not the most efficient way of ReTweeting and so they introduced a new method of ReTweeting which was quicker but had lesser control. On the Web Interface, you can just click on ReTweet and Voila, you are done. You have shared the post on your Twitter and also given credit to the original author.

Disadvantages of New School RT
But not everybody enjoyed the newer method of ReTweet and these were three primary reasons –

  1. It has less control than older method of ReTweet where you could modify the Tweet before ReTweeting
  2. The ReTweeted tweet doesn’t appear in the Mentions or Replies section of the original author and original author has to check a separate section named “ReTweets => Your Tweets ReTweeted” for seeing who all have ReTweeted his content.
  3. Twitter Clients like TweetDeck, HootSuite and Seesmic were not well integrated with the new style of RT. Some clients had no direct way to see those new style of RTs.

Due to above disadvantages Old School RT was still the most popular method of RT on Twitter.

Recent Changes on 20th April 2010
Now, Twitter has changed the rules of ReTweet again. Yesterday Twitter has made some changes to the system, so that every time someone uses the “retweet” button on Twitter web interface (or new method of retweet from his Twitter client) to retweet, original tweet author can see the ReTweeted tweet in @replies section. This seems very much logical change.

New Rules of the Twitter Game
ReTweets were the way for promotion and building relationship on Twitter. The problem number 1 mentioned above is still there with the new style RT, but the problem number 2 and 3 seems to be solved with this change. So with the time we will see -

  1. Old School ReTweets are dying
  2. More and More new style RT and hence more credit to the original author.
  3.  Easier to manage – Easier to ReTweet which means more RT.

Do you see any other implication on Twitter and Twitter user if old school ReTweet method dies?

Saturday, February 20, 2010

4 Cool New Goolge Wave Features

1. Double-click to edit a wave
It is simple, just double-click on the content area where you are reading the wave. It will show two options - reply and edit. Select "edit" and you are done, it will open-up the editor. This is much faster than selecting “Edit this wave” from the menu at top-right.

2. Read-only wave
When you make a wave public, by adding, you now get an option whether you want to give read only access to the new user or full editable access.

Read-only participants can only view the wave and look at the history. But they can neither add anybody to the wave, nor can they make any modification to the wave.

3. Add Google Groups to wave
You can add a Google Group to a wave, set permissions and then view and edit waves with that group. This is a very useful feature for a person like me who uses wave for group collaboration half the times. In one of my astrology forum, I used Google Wiki for writing an ebook with my forum members and Google Wave is even better.

4. Revert to older version
Wave version control got better after introducing option for reverting to older version. You now get "Restore" option during playback (while checking the history)

Love you Google and Google Wave. Looking forward to the invitation for Google Wave on my Google Apps.

Important Note for New User:
While using Google Wave for any serious work, always keep in mind that you can not remove a user from the wave. Which means, that other user, even if accidently added to the wave, has as much control as you do. You do not own the wave created by you. So, be careful for using Wave for any official/ confidential kind of work that you do not want to share with the world.
(As on 22nd April 2010, now you can remove a user from the wave)

Related Articles:
Google Wave for Dummies