Gmail on you mobile

Nokia N80

First, if you don’t use gmail you should really consider starting. It’s the best web based mail this planet has seen so far. On my computer at home I don’t use anything else. I didn’t even bother to install Outlook or anything similar the last time I cleaned up the box.

If you need an invite send me an email to eirikso at gmail dot com. The 50 first will get one. Or, simply google “gmail invite”…

So, you’re using gmail and you have a Symbian phone. Like the Nokia N80 or N73 one of the 300 supported java enabeled phones. And you want a nice interface for your gmail account. Then simply point the browser in your phone to “” and install.

A very nice application to read your gmail on the phone. Only one (big) disappointment so far: you can’t attach anything when you send mails from this client. This is something that Google needs to fix!

A quick note: the phone in the picture is a Nokia N80. The picture itself is taken with my Nokia N73. Click the image to see the high resolution version.

Gmail on you mobile

The death of beta

After writing about my first experience with the new Yahoo GO TV people keep reminding me about the fact that this is beta software. At some point back in time a “beta version” of a software package was a complete version, but with possibilities for bugs and maybe some minor functions missing.

Flickr Beta Gmail Beta

This whole Web 2.0 thing has destroyed the “beta” state completely. “Beta” means nothing as long as the world’s most successful photo sharing site – Flickr is still in “beta” after years of existence and the world’s best web based mail – Gmail is also in “beta”.

So what should the team behind Yahoo Go TV do when they want to show people something before it is completed? Call it “a public preview” or something. If you absolutely want to call it a “beta” because that is so cool and Web 2.0 like then please emphasise what’s the reason for the “beta” state.

For Yahoo Go TV the situation is a bit special since they bought a complete product with a large user base and lots of functions and then release this complete product as a “beta”. This is my suggestion:

1. Analyze what’s the most important functions for the passionate and long time users:
– The configuration tool and flexibility
– The plugins

2. Understand that it is these long time users that will write about your product at once and like it or not, they will compare it with the existing one that they love.

3. Keep those existing functions when releasing the first “beta”

4. If keeping these advanced functions is impossible make it completely clear that they will appear again in a future release. Do that by implementing some extra screens in the installation wizard.

A screen that says “Open the advanced configuration tool” with a greyed out “OK” button and a message that says “This is a preview version, the configuration utility will be back in the next release“. Do the same thing with the plugins and the other functions that you find important. “Add plugins” – Message: we will keep supporting plugins but they are disabled in this preview version. And so on.

Doing so would avoid the negative parts of discussions like this and this. Now, the fact that you follow the forums and the blogs and actually post comments and take part in the discussion is great. Keep up the good work!

Looking forward to the next “beta” or “public preview” or “release candidate” or … of Yahoo Go for TV!


Writely Logo
I forgot to mention another solution. The extremely cool BetaMeter that writely use:
Beta Meter

It’s now on 64%. At least I can see an end to Writely’s beta status.

The death of beta