G.E. Handheld UltraSound: from US$250,000 to US$7,000 in 5 months!

Last week I noticed the Beeb had a story on G.E.’s new hand-held ultrasound (story).

Developer GE Healthcare says the portable device, priced at about £5,000 in the UK, is not designed to replace existing machines.

I did a search around and found that it was actually released back in October 2009 (story).

GE has just unveiled this device at the Web 2.0 summit, and they estimate that its cost will be about $250,000.

So between 10th October 2009 and mid February 2010, some 19 weeks, the price has dropped by some US$240,000. That’s a drop of US$12,000 a week, US$1,800 a day, or $75 an hour. Imaging trying to put a purchase order together for one – you just can’t nail down a price. I would guess this isn’t a linear price drop, because in about 10 days from now (Feb 2010) they they would be free!
What will be interesting is when you can rent one for a few months for home use. Wow; wonder what interesting things people would ultrasound? Pets? Tracing the wiring in walls? Injuries? Perhaps they’ll be used by pro-sports players on the field to assess injury?

Google Nexus One: first impressions

This blog post is being done by voice from my new phone. Yes I finally caved in and bought a Google phone.

Well, the first part was voice captured, analysed, and shipped back in 95% accurate transcoding within a few seconds. This part is being written on my old laptop.

My recent trip to SF saw me meet up with an old friend (Mikolaj) who works at the so-called Mountain View Chocolate Factory that has become a part of all our on-line lives. And I was impressed; nice big bright screen, good integration with various on-line services (many Google run, but still ones I already used, like Calendar). And the reviews showed it to be good, with a “fast” processor, etc, etc. It looked like a slightly smaller iPhone, which seemed nice.

And then Linus spoke to the masses, and yeah, he professed he was pleased. While the rest of the community complained about forks and support, I found my 5 year old Nokia, with 1″ blurry screen, half-day standby time, 5 minute talk-time was a bit long in the tooth. So I caved. I got a Google phone; the Nexus One.

I ordered it around noon on Monday. By Wednesday night, a little over 56 hours later, it was in my hands in London, England. Nicely engraved with my name, in its small white box.

The open box experience was similar to what opening Apple products was like; a nice box, smoothly opening to reveal the well mounted product, sheathed in a cardboard mount to ensure it is… displayed… as the box is opened.

The ray of sunshine came down, and all was good.

So, a few second later an the device was free of its transport. It comes wrapped in a cellophane sleeve that tries to explain how to open the case. Accompanying it is a warranty paper, and a single sheet of numbered instructions, 1 to 5, indicating that you need to put the battery in, give it a full charge, and then turn it on. Back on the cellophane, how did it come off. Was there a release button, a catch, a lever, a… hang on… no, slide and it pops open – wow, that was easier than I expected!

Charge charge charge. Tap tap tap. Green LED! Go!

The set up was smooth and straight forward. Since I didn’t have a SIM in phone to start with (it was in the aforementioned Nokia device), it asked me to set up WiFi. Then my Googlemail account, and woosh… my calendar, contacts, and Gmail all came down.

And then.. it advised a new firmware, would I like to install it? Yes. And woosh, it did what it should, and it was all good. Pinch to zoom on maps works (multitouch).

A few seconds later and my rcpt.to email IMAPS and SMTP/STARTTLS was up and running.

Later, a browse the “Marketplace”, the Android App store, And it advised of an updated Maps application.  Then add in the compass, and Snake.

So,w hat are my favourite things:

Google Goggles: scans pictures for things (bar codes, objects, logos) and then displays information on it.

Voice search: someone (Eric) mentioned a book title today but couldn’t remember the author, so I whispered the title to my phone and it showed me the cover, summary, author, etc.

Maps: well, as ever. I have had this on my Blackberry Bold, but the Nexus One has a screen twice the size, and a magnetic compass.

The only downside was the battery life with the GPS turned on today. Admittedly, I did play with it a fair bit. And to its credit, it showed me what was responsible for the power use: the display – it breaks down the consumption of power to the various components of the phone, which is neat. I’ve turned off the GPS for tomorrow trail!

I’ve fired up Facebook and all my contacts from Facebook have (at my choice) been sucked into my phone contact lists (with all their pictures). So I think my contacts are now not stored in my phone, nor on the SIM, but in the cloud.

I’ve had the phone for 24 hours now. I like it. It’s light, and does everything. It was cheaper than an iPhone, and is more open.  What’s not to like thus far.

Dreamscreen update: same problems

Yesterday (Feb 7th) my HP Dreamscreen advised on-screen that there was a firmware update (1.6.0.0, 2/1/2010). “Hurrah!” I thought. They’ve seen the issue with the Snapfish app being unable to load images and crashing to the “home” screen.

Sadly, not. It still fails to load most thumbnails in both the list of all albums, and when browsing a single album. Aghhh!

And there’s still no SDK. No way for me to write my own app to make it work like I want it to. There’s such a potential for this as a platform, but HP isn’t allowing this to be realised. *sigh*

HP DreamScreen: recent developments

The DreamScreen is unwell. It’s Snapfish application is dying. Repeatedly. And it’s not showing the Snapfish albums when it does run….

I thought it was a weak Wifi signal, but after re-positioning the router to within 2 metres of the DreamScreen, I think its safe to say it’s not.

When starting the Snapfish application (why can’t it automatically “sleep” to this app?) it tried to download the list of albums. It seems to know how many albums I have, but fails to get the thumbnails, and the album titles. Trying to browse an album seems to again know how many items there are, but again the thumbnails fail. Trying to show a high res crashes the app, and the main menu screen is shown again.

Tut tut, HP:

  1. Your Snapfish app (HP’s stack on the dream screen hardware) doesn’t seem to be resilient enough to handle data returned to it and crashes. Bad.
  2. HP runs Snapfish – if that’s returning new/different data, then that’s Snapfish’s fault for modifying a “stable” API. Which is HP.  Bad.
  3. There is no diagnosis that I can access to see what the error is. Bad.
  4. There is no way for me to write an app onto this platform, still. Bad.

There was talk of an open SDK at one stage, but I’ve not seen any sign of it. Hum….

If HP doesn’t resolve this issue, or free the platform to let people develop more useful apps, then it will circle the plughole and die! An opportunity for a great product missed.