Tag Archives: google

Building for multiple mobile platforms with one codebase

Individuals may have strong opinions about the merits of Apple iPhone versus Google Android versus the struggling Palm WebOS versus the not-yet Windows Phone 7; but sit them round a table to discuss app strategy and those diverse platforms change from a debating point to a problem. Presuming a web app won’t cut it, how do you target all those devices without the unreasonable expense and complication of managing multiple projects? The native languages are all different; Objective-C for iPhone and iPad, Java for Android and RIM BlackBerry, JavaScript for WebOS, C# for Windows Phone 7.

There are three possibilities that come to mind. One is that all the platforms will eventually allow you to write in C or C++, making this the unifying language, though you still have some fancy footwork to do overcoming library differences. Android now allows this via the NDK, and Palm via the PDK. There is currently no alternative to Java for Blackberry, and Microsoft says native code won’t be possible on Windows Phone 7, but well, you never know.

The second is Adobe Flash. This is an interesting one, because Apple prohibits Flash on the iPhone, but Adobe has a Packager for iPhone that builds native iPhone apps from Flash projects. Another issue is that although Flash is available or promised for all the main non-Apple devices – Apple’s gift of a selling point to its rivals – it is not Flash alone that does what it needed, but AIR, the “desktop” or out-of-browser runtime. This has been previewed for Android and promised for other devices including Blackberry. AIR for Windows Phone 7? Maybe, though I’ve not seen it mentioned.

A third idea is a clever framework that does the necessary cross-compilation under the covers. This cannot depend on deploying a runtime, nor compiling to native code, because these approaches are blocked by some mobile platforms. Rhomobile has the Rhodes framework, where you code your app in HTML and Ruby and compile for devices including iPhone, Windows Mobile, RIM Blackberry, Symbian, and Android. Rhodes includes an MVC (Model View Controller) framework and an ORM (Object Relational Mapper) to wrap database access. There is also a RhoSync server component to enable offline data with synchronisation back to the server when reconnected; and the RhoHub hosted IDE for buildings apps with a web browser.

Rhomobile tells me that Palm WebOS support is in the works. They also promise Windows Phone 7 support, which intrigued me because Rhodes says it compiles to “true native device applications”. Has Rhomobile gotten round Microsoft’s opposition to native code? Apparently not; VP Rob McMillen eventually told me that this will mean a .NET IL (intermediate language) implementation.

The Rhomobile approach reminds me of AppForge, a company which produced the well-regarded Crossfire add-on for Visual Studio and compiled Visual Basic to a wide variety of mobile platforms. Unfortunately AppForge was acquired by Oracle, and its new owners showed callous disregard for existing customers. Not only did development cease; it also became impossible to renew existing licenses. Thanks to an activation component, that also blocked new deployment of existing applications – every developer’s nightmare.

That said, there is no activation requirement for Rhodes that I know of, and the framework is open source, so I don’t mean to suggest it will suffer a similar fate.

What about Java? On the face of it, Java should be ideal, since multi-device support is what it was designed for. It is a measure of how far Java has fallen that we hear far more about the lack of Flash on the iPhone, than the lack of Java. Microsoft says yes to Flash on Windows Phone 7, though not on first release, but nothing about Java.

Java as a mobile runtime needs a strong dose of lobbying and evangelism from its new stewards Oracle if it is not to fall by the wayside in this context. Hmm, AppForge.

Google’s privacy campaign, and three ways in which Google gets your data

Google is campaigning to reassure us that its Chrome browser is, well, no worse at recording your every move on the web than any other browser.

Using Chrome doesn’t mean sharing more information with Google than using any other browser

says a spokesman in this video, part of a series on Google Chrome & Privacy.

image

What then follows is links to four other videos describing the various ways in which Google Chrome records your web activity.

If you subtract the spin, the conclusion is that Google retrieves a large amount of data from you, especially if you stick with the default settings. Further, it is not possible as far as I know to use the browser without sending any data to your default search provider, most likely Google. The reason is the Omnibox, the combined address and search box. Here’s what Google’s Brian Rakowski says in the video on Google Chrome & Privacy – Browsers search and suggestions

For combined search and web address to work, input in the Omnibox will need to be sent to your search provider to return suggestions. If you have chosen Google as your search provider, only around 2% of the search input is logged and used to improve Google’s suggestion service. Rest assured that this data is anonymised as soon as possible within 24 hours, and you always have the option of disabling the suggest feature at any time.

However, even if you disable suggestions, what you type in the box still gets sent to your search provider if it is not a valid web address, in other words anything that is not a complete URL (though Chrome will infer the http:// prefix).

It is also worth noting that Google does not only get your data via browser features. Most web pages today are not served from a single source. They include scripts that serve data from other locations, which means that your browser requests it, which means that these other locations know your IP number, browser version and so on. Two of the most common sources for such scripts are Google AdSense (for advertising) and Google Analytics (for analysing web traffic).

Even if you contrive not to tell Google in advance where you are going, it will probably find out when you get there.

It is important to distinguish what Google can do from what it does do. Note the language in Rakowski’s explanation above. When he says input is sent to your search provider, he is describing the technology. When he says that data is anonymized as soon as possible, he is asking us to trust Google.

Note also that if you ask to send in auditors to verify that Google is successfully anonymising your data, it is likely that your request will be refused.

There are ways round all these things, but most of us have to accept that Google is getting more than enough data from us to create a detailed profile. Therefore the secondary question, of how trustworthy the company is, matters more than the first one, about how it gets the data.

Why programmers should study Microsoft’s random failure and not trust Google search

The bizarre story of the EU-mandated Windows browser choice screen took an unexpected twist recently when it was noticed that the order of the browsers was not truly random.

image

IBM’s Rob Weir was not the first to spot the problem, but did a great job in writing it up, both when initially observed and after it was fixed by Microsoft.

It was an algorithm error, a piece of code that did not return the results the programmer intended.

Unless Microsoft chooses to tell us, there is no way to tell how the error happened. However, as Weir and others observe, it may be significant that a Google search for something like Javascript random sort immediately gets you sample code that has the same error. Further, the error is not immediately obvious, making it particularly dangerous.

I am sure I am not the only person to turn to Google when confronted with some programming task that requires some research. In general, it is a great resource; and Google’s own algorithms help a little with filtering the results so that sites with better reputation or more inbound links come higher in the results.

Still, what this case illustrates – though accepting again that we do not know how the error occurred in this instance – is that pasting code from a Google search into your project without fully understanding and testing it does not always work. Subtle bugs like this one, which may go unnoticed for a long time, can have severe consequences. Randomisation is used in security code, for example.

As an aside, there also seems to be some randomness in the appearance of the browser choice screen. It turned up on my laptop, but not on my desktop, although both have IE as the default.

And who would have guessed that the EU would arrange for so many of us to get an ad for something like the GreenBrowser popping up on our desktop? Apparently it is the “best choice of flexible and powerful green web browser”, though since it is based on IE it is less radical a choice than it first seems.

image

Google Chrome usage growing fast; Apple ahead on mobile web

Looking at my browser stats for February one thing stands out: Google Chrome. The top five browsers are these:

  1. Internet Explorer 40.5%
  2. Firefox 34.1%
  3. Chrome 10.5%
  4. Safari 4.3%
  5. Opera 2.9%

Chrome usage has more than doubled in six months, on this site.

I don’t pretend this is representative of the web as a whole, though I suspect it is a good leading indicator because of the relatively technical readership. Note that although I post a lot about Microsoft, IE usage here is below that on the web as a whole. Here are the figures from NetMarketShare for February:

  1. Internet Explorer 61.58%
  2. Firefox 24.23%
  3. Chrome 5.61%
  4. Safari 4.45%
  5. Opera 2.35%

and from  statcounter:

  1. Internet Explorer 54.81%
  2. Firefox 31.29%
  3. Chrome 6.88%
  4. Safari 4.16%
  5. Opera 1.94%

There are sizeable variations (so distrust both), but similar trends: gradual decline for IE, Firefox growing slightly, Chrome growing dramatically. Safari I suspect tracks Mac usage closely, a little below because some Mac users use Firefox. Mobile is interesting too, here’s StatCounter:

  1. Opera 24.26
  2. iPhone 22.5
  3. Nokia 16.8
  4. Blackberry 11.29
  5. Android 6.27
  6. iTouch 10.87

Note that iPhone/iTouch would be top if combined. Note also the complete absence of IE: either Windows Mobile users don’t browse the web, or they use Opera to do so.

I’m most interested in how Chrome usage is gathering pace. There are implications for web applications, since Chrome has an exceptionally fast JavaScript engine. Firefox is fast too, but on my latest quick Sunspider test, Firefox 3.6 scored 998.2ms vs Chrome 4.0’s 588.4ms (lower is better). IE 8.0 is miserably slow on this of course; just for the record, 5075.2ms.

Why are people switching to Chrome? I’d suggest the following. First, it is quick and easy to install, and installs into the user’s home directory on Windows so does not require local administrative rights. Second, it starts in a blink, contributing to a positive impression. Third, Google is now promoting it vigorously – I frequently see it advertised. Finally, users just like it; it works as advertised, and generally does so quickly.

Fragmentation and the RIA wars: Flash is the least bad solution

The latest salvo in the Adobe Flash wars comes from the Free Software Foundation, in an open letter to Google:

Just think what you can achieve by releasing the VP8 codec under an irrevocable royalty-free license and pushing it out to users on YouTube? You can end the web’s dependence on patent-encumbered video formats and proprietary software (Flash) … Apple has had the mettle to ditch Flash on the iPhone and the iPad – albeit for suspect reasons and using abhorrent methods (DRM) – and this has pushed web developers to make Flash-free alternatives of their pages. You could do the same with YouTube, for better reasons, and it would be a death-blow to Flash’s dominance in web video.

Fair point; but one thing the FSF misses is that Apple’s stance has not only “pushed web developers to make Flash-free alternatives of their pages”. It has also pushed developers into making Apple-specific apps as an alternative to web pages – which to my mind is unfortunate.

The problem goes beyond web pages. If you have an application that goes beyond HTML and JavaScript, maybe for offline use or to integrate with other local applications or hardware, there is no cross-platform solution for the iPhone, iTouch or forthcoming iPad.

While I understand that non-proprietary platforms are preferable to proprietary platforms, it seems to me that a free cross-platform runtime is less evil than a vendor-controlled platform where I have to seek approval and share income with the vendor just to get my app installed.

More broadly, it is obvious that the days of Windows on the desktop, Web for everything else are over. We are seeing a proliferation of devices, each with their own SDK: alongside Apple there is Palm WebOS, Nokia/Intel Meego, Google Android, and when Windows Phone 7 comes along, Microsoft Silverlight.

The question: if you have an application and want to reach all these platforms, what do you do? A web app if possible; but otherwise?

It is the new fragmentation; and frankly, Adobe Flash is the closest thing we have to a solution, particularly with the native compilation option for iPhone that is coming in Creative Suite 5.

I don’t like the idea of a single company owning the runtime that unifies all these platforms. That’s not healthy. Still, at least Adobe is currently independent of the obvious industry giants: Google, Apple, Microsoft, IBM and so on.

Dealing a death-blow to Flash is all very well, but the end result could be something worse.

Google’s strategy unveiled: a little bit of everything you do

Google CEO Eric Schmidt gave a keynote address at the Mobile World Congress yesterday, which is worth watching if you have an interest in the future of technology or, well, human life.

image

The talk was an informative and open insight into Google’s future direction. It was centred on mobile; but since Google now regards the mobile phone as the primary device for how we interact with the world, that was no limitation. Google is putting mobile first, said Schmidt, because it is the meeting point for the three things that matter: computing, connectivity and the cloud. He believes that phones will replace credit cards, for example, as they are smarter and more secure for financial transactions.

Google’s strategy is to combine the near-unlimited power of server-side computing with its database of human behaviour, to create devices that are “like magic. All of a sudden there are things you can do that were not previously possible.”

He gave an illuminating example: Google voice search. You speak into your phone, and Google transcribes your voice and performs a search. Voice recognition is nothing new, but the difference in the Google demo is that it works. Here’s how. The problem with voice recognition is that one word sounds very like another, especially since we do not speak with precision and every voice varies. Computers cannot understand exactly what we say, but they can use dictionaries to come up with a set of possibilities for what we said, one of which is likely to be correct.

image

The next step is the brilliant one. Google takes this set of possible phrases and compares it to recent Google searches. If one of them matches a popular search, then it is likely to be what you said. Bingo. Google now does this in four languages, with German demonstrated for the first time yesterday.

It works on the assumption that humans are not very original. We tend to do similar things, and to be interested in similar things. Therefore, as Schmidt noted, if you are a tourist walking around a city with your location-aware phone, Google does not only know where you are; it also has a good idea of where you will go next.

Another cool demo is for image recognition. We saw this in two guises. In one, you hold up your phone and do an image search using the camera as input. Result: information about the building you are looking at. [Or maybe the person? Hmm.]

In another demo, you point the camera at your foreign-language menu as you ponder which incomprehensible dish might be one you could eat. Back comes the translation in your own language.

Note that these demonstrations are not really about super-powerful phones, but rather about the other two factors mentioned above, the power of cloud computing combined with a vast database of knowledge.

Schmidt’s blind spot is that he does not really see privacy as an issue. He mentions it from time to time; but he is clear that he regards the trade-off, that we give our personal data to Google in return for these cool services, as worth it. I posted a remarkable quote yesterday. Here’s another one, from late on in the address:

Google will know more about the customer because it benefits the customer if we know more about them.

What Schmidt fails to do is to extrapolate the implications for stuff other than cool services. One is what happens if that huge database is used dishonourably. Another is the huge competitive advantage it gives to Google versus everyone else; Google has this data, but rest of us do not. A third is how that data could be used in ways that disadvantage us. An example is in insurance. Insurance is about pooling risk. The more data insurance companies have about you, the more accurately they can assess the risk, which means a wider range of premiums. If by some mechanism insurance companies are able to analyse Google’s data to assess risk, they can refuse to insure, or charge high penalties, for the higher risks. We won’t necessarily enjoy that, because it means more us may find it impossible to get the insurance we want at a price we can afford.

Google’s business strategy

That’s the technical side. What are Google’s business plans? Schmidt made some interesting comments here as well, many of them in the question and answer session.

Google does not plan to become a mobile operator. Schmidt received some fairly hostile questions on this topic. Since Google positions operators as dumb pipes, stealing their talk minutes and insisting on an open web for services, who will invest in infrastructure? Schmidt denies positioning operators as dumb pipes, but does not leave them room for much other than infrastructure; he says they might have a role in financial transactions.

How do we (both Google and the rest of us) make money? Two main areas, according to Schmidt. One is advertising. He says that online advertising spend is currently one tenth of the total, and that this proportion must grow since “consumers are moving from offline to online.” In addition, mobile advertising will be huge since you can target location as well as using other data to personalise ads. “The local opportunity is much larger, and largely unexplored,” he says.

The other big opportunity is apps. The number of apps that need to be installed locally is constantly diminishing, he says, leaving great potential for new cloud-based applications and services.

As for Google, Schmidt says it wants to be part of everything you do:

We want to have a little bit of Google in every transaction on the internet

Thought-provoking stuff, and a force that will be hard to resist.

So who can compete with Google? Making equally capable phones is easy; building an equally good database of human intentions not so much, particularly since it is self-perpetuating: the more we all use Google, the better it gets.

No wonder Microsoft is piling money into Bing, with limited success so far. No wonder Apple’s Steve Jobs is concerned:

On Google: We did not enter the search business, Jobs said. They entered the phone business. Make no mistake, they want to kill the iPhone. We won’t let them, he says. Someone else asks something on a different topic, but there’s no getting Jobs off this rant. I want to go back to that other question first and say one more thing, he says. This don’t be evil mantra: "It’s bullshit." Audience roars.

Eric Schmidt: we can literally know everything

I am watching Google CEO Eric Schmidt’s keynote at the Mobile World Congress today. I am only 10 minutes in, but I was struck by these comments, as he talks about improving connectivity across the internet:

Think of it as an opportunity to instrument the world. These networks are now so pervasive that we can literally know everything if we want to. What people are doing, what people care about, information that’s monitored, we can literally know it if we want to, [pauses, lowers voice] and if people want us to know it.

A comment full of resonance. Who is “we”? You and I? or Google? The enthusiasm for knowing everything about everything, the reluctant-sounding concession to privacy at the end. The sheer bravado of it; the word “literally”, which means in actual fact, without hyperbole; and yet which is obvious hyperbole.

For another view on this, see The Onion’s piece on Google’s opt-out village.

Windows Phone 7 Series and Microsoft’s partner problem

I watched Microsoft’s Steve Ballmer, Joe Belfiore, and Andy Lees introduce Windows Phone 7 Series. It appears to be a complete departure from previous iterations of Windows Mobile, in fact borrowing more from Zune than it does from earlier Windows phones. At one point, Lees noted that it has a “new core OS” optimized in partnership with Qualcomm, though I would not rest too much speculation on that one phrase.

image

Unfortunately, the piece that I am most interested in, which is the developer platform, was not much discussed. It is to be unveiled at Mix next month in Las Vegas. Ballmer did say:

We raised the platform on which people can build … a new foundation with a rich set of development tools, built in and complete service availability that software developers can assume as a foundation.

Make of that what you will. I’d be surprised though if Silverlight is not a big part of the development story, along with revamped Windows Live services. I guess I’m expecting Microsoft to deliver with Silverlight something similar to what Adobe is doing with Flash and AIR – AIR for mobile devices has just been announced – but without the breadth of support across devices that Adobe has achieved.

We have been told that Flash will not be part of Windows Phone 7 in its first version, so it looks like it may live in its own development world to some extent.

The demo at the press launch has been well received, and it looks likely that Microsoft is creating a more usable phone than earlier generations. That’s good, though it is telling that it took Apple with iPhone and perhaps Google with Android to convince Microsoft that maybe the Start menu and a cut down Windows API wasn’t the best way to do a phone.

In the absence of technical details, what interested me most were the comments about how Microsoft relates to its partners. It is a hot topic for me. I am taking heat for talking about a poor experience on WIndows 7 that is really the fault of 3rd parties. The problem is that the partner system which worked so well for Microsoft in the early days of the PC is now working against it, and an unpleasant experience of a Windows 7 netbook is a symptom of that.

Clearly Microsoft also understands this. Ballmer noted that

We want to lead and take complete accountability for the end user experience … have more consistency in the hardware platform, more consistency in the user experience, but still enable [partner] innovation

Translation: we are being hammered by OEMs who wreck our product with poor quality hardware and add-on software.

But how will Microsoft change this aspect of Windows, whether on the desktop or a device? “There’s a bit of a conundrum here,” said Ballmer, and he is right. If Microsoft tries Apple-style lockdown, it may run into anti-trust trouble and/or drive OEMs to Linux. If Microsoft does no more than talk the talk, then the problem remains.

It is true that Microsoft is strictly specifying minimum hardware. That’s nothing new; it has done this since the earliest days of Pocket PC.

I’m inclined to think it is just talking the talk and that nothing will change. Still, here’s Lees on the same subject. He begins by restating Microsoft’s belief in the partner model:

One of the things we’ve kept constant is our belief in the partner model. There are three reasons why partners are fundamental to our business. Firstly, they add rich experience and expertise across a broad spectrum of areas, hardware, software and services. Second, is … scale. We need partners to develop, market and support Windows phones at this scale. Third, partners meet diverse needs by providing customers with choice. One size does not fit all. People want different kinds of phones.

It’s odd how Apple thrives without all that “rich experience and expertise.” But never mind. Lees adds:

We have changed how we work with them. The goal is to improve the quality and consistency.

So Microsoft says with one breath how it just loves the partner model, and with the next that it is changing it. We all know why it wants to change it. It is because it is broken, though Microsoft cannot bring itself to admit it out loud.

The question: which of these near-contradictory statements do you believe? That it is sticking with the failing partner model, or that it is changing it? My guess is the former, because I am not sure that Microsoft really has the will or even the ability to change, but I would like to be proved wrong.

Oh, and Lees says that the mobile operators:

… have tremendous value to add. They are not just dumb pipes. Our model is about enabling those innovations so that they can add software and services and benefit from our … platform.

I understand why Lees said this; but I find it hard to think of tremendous added value from the operators. Apple’s iPhone success is partly thanks to its skill in working round them.

Miserable user experience continues with Windows 7

I’ve just spent some time with a non-technical person who has just signed up for a £30 per month Vodafone internet dongle, which came with a “free” Samsung netbook running Windows 7 Starter Edition.

The user is returning it under the terms of the 14-day trial offer.

Why? Well, the requirement was for a small computer that would be connected to the Internet everywhere, within reason. The user also purchased Microsoft Office along with (for some reason I could not discern) Norton Internet Security.

The good news: the internet connection was fine when connected, something like 2.5Mb download speed on a brief test.

The bad news:

1. The little netbook was badly infested with trialware. Browsing the web was difficult because the already-small screen area was further filled by two additional toolbars, one from Google and the other from MacAfee, leaving barely half the screen for actual web pages. Google kept on prompting for permission to grab user data about location and who knows what else.

2. MacAfee was pre-installed and the task of removing it and replacing it with Norton was tricky, bearing in mind that Norton was delivered on a CD and there was no CD drive. MacAfee was constantly warning that the user was at risk.

3. Two Samsung dialogs popped up on each boot asking the user to do a backup to external storage.

4. The Vodafone connect software was bewildering. In part this was thanks to a complex UI. There also seemed to be bugs. The “usage limit” was preset at 50MB separately for 3G and GPRS; the deal allowed 3GB overall. Changing the usage limit seemed to work, but it reverted at next boot. Then it showed usage limit warnings, as 50MB had already been transferred. Once while I was there the Vodafone utility crashed completely.

5. The Vodafone dongle wobbled in the USB slot. Whenever it was attached it would come up with a dialog asking to run setup, because it included a storage area containing the utility software, even though the utility was already installed.

6. The Vodafone connection is managed through an icon in the notification area that you right-click to connect or disconnect. Windows 7 had hidden this thanks to the new default behaviour of the notification area, which is a usability disaster.

7. The Vodafone connection was set to prompt for a connection. It did sometimes display a prompt, but apparently on some kind of timeout, since it quickly closed without actually connecting. The prompt then did not reappear during that session.

The user concluded that it was too complicated to use, hence the return.

Now, for most readers of this blog I am sure none of the above would matter. We would uninstall MacAfee and Google toolbar, not buy Norton but simply install Microsoft Security Essentials, maybe use Google Chrome for a leaner browsing experience, remove any other software that was not essential (and there was other trialware that I did not have time to investigate), unset the silly option to hide notification icons, find a way of taming or replacing Vodafone’s connection utility, and all would be fine.

I am not sure of the value of the Vodafone contract; the deal is not too bad if you need to connect while out and about, though there is a heavy penalty charge of £15.00 per GB if you exceed 3GB in a month, and it is quite unsuitable if, as in this case, it is your only Internet connection and you plan to use it for things like BBC iPlayer.

That’s an aside. What I find depressing is that despite Microsoft’s efforts to improve Windows usability in 7, the real-world result can still be so poor.

In this case, most of the blame is with Vodafone for poor software, and Samsung for taking all those trialware fees. I guess it is not that bad a deal, since there is almost always someone around who is willing or enjoys solving these puzzles and getting everything working.

Still, here is a customer who wanted and was willing to pay for a no-frills, always-connected internet device, and was let down.

Here also is the market that Apple aims to satisfy with iPad, and Google with devices running Chrome OS.

I wish them every success, since it seems that the Microsoft + OEM Windows culture cannot easily meet this need.

Buzz buzz – Google profile nonsense

Google has launched a new social media service called Buzz (as if you did not know) and I’m on it – here’s my profile.

You had better follow that link too; because whenever I visit the profile when signed into Google I see this not-too-subtle banner:

image

“Your profile is not yet eligible to be featured in Google search results”. This statement with its bold yellow highlighting seems intended to make me anxious, though I’m not sure why I should care about this deliberate defect in Google’s search algorithms. Having said which, it is not actually true, as a quick search verifies:

image

Still, let’s presume that I believe it and want to fix it. I click the link to learn more. Does it tell me how to make my profile “eligible”? Not as such. Without making any promises, Google suggests that I should add more details,

For example, include details such as the name of your hometown, your job title, where you work or go to school.

It also wants a little link exchange:

Link to your profile on another website (for instance, your blog or online photo album)

and finally

Verify your name, and get a "Verified" badge on your profile.

I’ve been round the verify circus before; if you try to do it, you wander round the near-abandoned Knol for a while before discovering that it only works, some of the time, for USA residents.

Frankly, it all seems a bit desperate. My Google profile is just as I want it already, as it happens, though I could do without the big deceitful banner.

That said, this profile nonsense does nothing to allay my sense that Google has designs on me and wants more of my personal data and internet identity than I am inclined to give.

Buzz is a hard sell for me. I like Twitter, because it is single-purpose, works well – in conjunction with one of the many desktop add-ons such as Twhirl – and I never feel that it wants to take over my life.

Still, I am buzzing now, especially since I’ve linked it to Twitter so all my tweets arrive there too. We’ll see.