Tim Anderson’s ITWriting

If you have any interest in the future of the music industry, I recommend taking a look at the following video:

There are a couple of reasons why this demo of streaming music to a Google Android mobile is interesting. First, if Spotify delivers the kind of performance and quality it has on the desktop, this will be a great facility for music fans. Second, it is interesting to see how it handles the offline problem, such as when you are in London and descend into the London Underground train network. Simple: just mark a track for offline use, and it downloads to local storage. I’m presuming this is encrypted in some way in order to prevent you from converting it to a standard MP3; but if it is always available anyway, who cares?

Will this be free, or a premium service? I’m guessing the latter but don’t yet have any more details.

Of course everyone is asking for an iPhone version. See for example this post:

It’s interesting that Spotify has chosen Android as the mobile debut, rather than iPhone – although it’s safe to assume the company is working on Apple’s handset too, among others.

Hmmm, I wonder what chance this would have of getting past Apple’s iPhone app censorship? It seems to me that what we are seeing is the beginning of the end for the iTunes download model.

I’ve been researching open source .NET and noticed that SharpDevelop, the free IDE for .NET on Windows, completed version 3.0 earlier this month. Congratulations to the team. Along with Windows Forms and ASP.NET applications in C# or Visual Basic, you get extras like support for F#, Boo and Python. Another welcome feature is built-in support for Subversion version control. There’s even an ASCII table in the IDE, which brings back memories: 15 years ago every programming manual had one at the back.

SharpDevelop has two major challenges. One is keeping up with Microsoft; right now there are discussions about improving WPF support, for example. The other is that Microsoft offers free Express versions of Visual Studio, which leaves SharpDevelop with those niche users for whom the Express products are unsuitable, but who do not want to pay for a full version, or who are wedded to some exclusive SharpDevelop feature.

In favour of SharpDevelop, it installs more easily and loads more quickly than Microsoft’s effort, and certainly proves the point that native C# applications do not have to be slow.

A more interesting though less complete product is the forked MonoDevelop, which is cross platform and targets Mono, the open source implementation of .NET. Mono now looks good on Linux; but the idea of WORA (Write Once Run Anywhere) has never really caught on in the .NET world. How many significant Mono applications for Windows have you seen? My guess is that if it happens at all, it will be in the form of Silverlight/Moonlight running in the browser.

I’m sure it can really lose your data as well, but in this case “seem” is the appropriate word. I’ve been messing around with Hyper-V and one of my test machines is a SharePoint server. I started this up and found I could not access it over the network. On further investigation, it turned out to be a broken trust relationship with the Domain Controller. In other words, on attempting to log on with domain credentials I got the message:

The trust relationship between this workstation and the primary domain failed

The official advice when confronted with this problem is to remove and re-join it to the domain, creating a new computer account. I did so. Logged on, and was disappointed to discover that SharePoint was now empty. Worse still, even checking out the SQL Server databases did not uncover them. All my documents had vanished.

It turned out that I had done the wrong thing. What had really happened is that Hyper-V had been saving my changes on that virtual hard drive to a “differencing disk”, a file with an .avhd extension. This is part of the Hyper-V snapshot system. Somehow, Hyper-V had forgotten the differencing disk, and started up my SharePoint VM using the last fully merged copy of the drive, which was over a month old. My drive had gone back in time, so the data had gone.

The solution was to restore the old parent .vhd from backup, and then manually merge it with the differencing file. Step by step instructions are here. Since I had deleted the original computer account, I then had to remove and rejoin the machine to the domain a second time. All was well and my data reappeared.

The bug here is how Hyper-V managed to start with an old version of the virtual hard drive in the first place. I can imagine this causing panic if it occurs in production – and once you start writing new, important data to the old version you are really in trouble. I was lucky that the discrepancy was severe enough that Active Directory complained.

Virtualization may be wonderful; but it also introduces new problems of its own.

The other lesson is that those .vhd files in C:\Users\Public\Public Documents\Hyper-V\Virtual Hard Disks do not necessarily contain your latest data. You also need to consider the .avhd files stored handily at C:\Program Data\Microsoft\Windows\Hyper-V\Snapshots.

One OS – one device – one AppStore – easy over-the-air purchase for end users. Apple’s development and deployment model delivers results, despite mutters about lock-in and Apple helping itself to a generous slice of the revenue.

Here at Adobe MAX Europe we’ve been hearing about the future of Flash on mobile devices and even seen a demo of what many would like to be able to do: simple over-the-air download of both the Flash runtime and Flash applications. Flash is a great runtime for a mobile device. A while back I reviewed the LG Viewty phone, which has a Flash UI, and despite some imperfections it convinced me of the potential of Flash for mobile devices.

Even so, it will be difficult for Adobe to create an application platform that works as well as Apple’s AppStore. Here are some of the problems.

• Device-specific APIs. I spoke to the folk on the Sony Ericsson stand here at MAX. If you want your Flash application to do things like talking to the GPS, or integrating with the PIM (Personal Information Manager) on the phone, then you have to write a device-specific version of your Flash application. This adds to the development effort and creates friction in the deployment process. Will Adobe wrap device functions in Flash APIs? I asked about this at the press briefing today. The answer from Senior Principal Scientist Mark Anders was yes … maybe. He mentioned that API bloat became a negative for Java. It really is a difficult thing to get right.
• Operator interference. Apple has bullied the operators it works with into doing things its way, and gets away with it because the device is so desirable. The operators though are reluctant to be no more than data carriers. They lock down devices, run their own application stores or music services, and make it difficult to mount a convincing challenge to Apple’s single store.
• Diversity of devices. Diversity is good, sure. It’s tough for developers though. Maybe there’s a keyboard, maybe there is a touch screen, maybe there is a joypad, maybe the screen is big or small. Your app has to work well in every scenario, or else limit the number of devices it supports. Much easier with Apple, just one device to target. That will change somewhat as Apple bring out new iPhone variants, but there will always be more consistency from a single vendor.

It was similar factors that caused Microsoft to abandon its third-party vendors and create Zune, in an effort to compete with the iPod. Microsoft was too late. I am sure we will see increasing use of Flash and Flash-based applications on mobile devices; but it will be hard to displace Apple’s iPhone as the foremost mobile platform for downloaded applications.

Flash in the mobile browser is another matter, of course. If Apple continues to exclude Adobe’s runtime – which I guess it does to protect its application business – then it makes a nice selling point for competitors which do support Flash.

VMWare has announced its Mobile Virtualization Platform for Mobile Phones. The idea is that you run apps within a virtual machine on your device:

Because VMware MVP virtualizes the hardware, handset vendors can develop a software stack with an operating system and a set of applications not tied to the underlying hardware allowing them to deploy the same software stack on a wide variety of phones without worrying about the underlying hardware differences. At the same time, by isolating the device drivers from the operating system, handset vendors can further reduce porting costs by using the same drivers irrespective of the operating system deployed on the phone.

One of the benefits claimed is the ability to switch VMs, for example between home and work versions, and the ability to migrate to a new device by copying the VM from one to another.

VMWare says the Mobile Virtual Platform (MVP) supports:

… a wide range of real-time and rich operating systems including Windows CE 5.0 and 6.0, Linux 2.6.x, Symbian 9.x, eCos, µITRON NORTi and µC/OS-II.

No mention of Apple or iPhone, of course.

Update: I got a little more info from VMWare about this. This is a bare metal VM, so there is no host OS as such. The implication is that you cannot run both the VM and another OS, as on a PC; the VM in effect replaces the OS. This isn’t a product you will be able to buy for your mobile; it will come pre-installed, presuming VMWare is successful in marketing it to mobile phone manufacturers and telecom providers.

The technology comes from a company called Trango which VMWare has acquired. There is a bit more information about the product on Trango’s site.

According to a release today from Moneysupermarket.com, promoting its recycling service, two-thirds of us (in the UK) don’t recycle old handsets. The worrying aspect of this is that handsets include some nasty chemicals (mostly in batteries) which should be disposed of safely. Many people either don’t know or don’t care about the regulations and throw old phones in the bin, whereupon they end up in landfill. Of course you could say the same about laptops, iPods, shavers, and no end of other electronic devices with rechargeable batteries. Moneysupermarket.com made a model out of old phones to make the point (that’s London’s Post Office Tower in the background):

I am not sure about the recycling service – you might do better on eBay, except for worthless old devices. Still, I do think this is a problem that should be addressed. I hate the casual manner in which we chuck poison into landfill, risking it finding its way into the foodchain. A good start would be to regulate against the business model of the major telecom providers, which subsidises the hardware thus encouraging users to change their devices long before they are really worn out.

• Reasonable price hardware without having to purchase a contract (it can’t qualify as an open platform without this).
• Excellent web browser (should be a given, coming from Google).
• Client for Exchange – or could just be secure IMAP, since Exchange supports this quite well.
• Google maps – this is one thing I know is on there.
• Ability to stream music over wifi. I have lots of music on a server at home, and would like to be able to play it easily on the mobile device.
• A keyboard – one of the things that puts me off Apple’s iPhone. I know this is on the T-Mobile G1, which is the HTC Dream.
• Respect for privacy. For example, the geolocation stuff is great, but the idea of broadcasting my presence to Google or others spooks me a bit too. I want full control.
• Ability to code and install my own apps. Should also be a given, as this is meant to be an open platform.
• Instant messaging with choice of service – not just Google Talk.
• Voice over IP when I am on wifi. Carriers dislike this of course.
• Up-to-date Flash runtime. Silverlight would be nice too; wonder if Microsoft/Mono is smart enough to pursue that with any vigour?
• View common document formats – the usual scenario is when these arrive as email attachments. I guess .doc and .pdf matter most. I occasionally get sent a .docx; I have never been sent an .odt.
• A bonus would be the ability to play divx movies.
• Excellent battery life. This matters.

I may have missed a few things. I’ll check out the press conference later and see what the score is.

During the keynote at Google Developer Day London, Android evangelist Mike Jennings gave us what he says is the first showing of an actual device – prototype, of course – in Europe. I took a few blurry pics.

Perhaps inevitably, it seems reminiscent of Apple’s iPhone. It even has an accelerometer so you can code it to respond to tilts and turns.

The web browser is based on WebKit, of course.

We were shown a spinning cube created in Java using an OpenGL library. The Android SDK is based on JDK 1.5.

Another thing that was mentions is Gears for Mobile. Now that Gears has a geolocation API it will be particularly useful in this context.

The LG Viewty (KU990) is a decent camera phone which came out last year in the wake of the first iPhone; yes it is me-too product but it has a few advantages over Apple’s product, like an 5 MP camera.

The trouble is, there are niggles, some minor, some major – like video recordings losing sound. A little over six months on, and users are posting messages like this:

I have to admit that I hate this phone. I have had mine six months now and I have regretted it for some time. It’s unresponsive, the camera is poor most of the time, it’s really awkward to use. It’s very slow at taking photos. It can’t hold a signal. The battery life is getting poor. It won’t handle many music file types very well. It feels like a Beta phone. The support from LG is non existent. I’m so disappointed. I look at apple, and yes, people did have to fork out for their phones, but look at the level of support and development they’re getting – new stuff is being added all of the time. It almost feels like they built this phone as a test for some of the features to go into other products.
The best thing about this phone is the video, and I love that part of it. I have some real magic moments captured and I’m grateful. But that is it.
I speak for myself, but I will never get another LG phone, period. As soon as I can get bought out of my contract the better.

It is a big change in mood from when the Viewty was released. This huge thread on the What Mobile forum has the story. Early adopters loved it – except for a few niggles which they hoped and expected would be fixed by a firmware update.

There has been no firmware update. Presumably all the software folk at LG have moved on to the next shiny device. Viewty users feel abandoned.

This seems like a good case study about not getting Web 2.0. Ironically LG made an effort to exploit social networking when the Viewty was launched. LG contacted bloggers and and offered phones for review; I reviewed it here. There is an official LG UK Blog – which sadly is pure marketing fluff and has done nothing to engage with the community over the issues which have been raised. There is an official Viewty website that has lots of Flash multimedia but little substance.

Yesterday I wrote about purchase decisions that begin with a Google search. Mobile phones are a good example. Anyone who does their Web homework will be put off the Viewty; and indeed deterred from newer LG models because the same thing will likely happen again. Network effects work both ways; even those who do not live on the Web will be influenced by opinion-formers who do.

It seems to me that a relatively small investment in communication and post-release software update and support would yield significant improvement in sales.