DP and HTML5 – strange bedfellows

So a few days back I got my hands a bit dirty with HTML5’s CANVAS tag.  And some number of weeks ago I got into the history object and HTML5’s improvements to that.  Today I got my feet a little wet with the AUDIO tag.

It’s an interesting concept, really.  This most recent journey has been within the context of the home audio system, and I was just just just remarking to myself that development was at a virtual standstill for a number of months – and here it is that HTML5 is enabling a new coding push with real-world usability.

Well, that’s the theory.

The truth is that HTML5 and embedded media consumption are themselves strange bedfellows, and as a result, I find myself in the same position in my relationship with HTML5.

So forget about the abstracts.  My music collection is overwhelmingly encoded in the MP3 format.  And when I say overwhelmingly, I really mean completely – with the exception of perhaps 20 tracks, vs. the other 35,064 which are MP3’s.  The problem with MP3 – besides its lossy, yesteryear compression – is that it’s not in the public domain.  This doesn’t really mesh well with HTML5 – specifically, the AUDIO tag of HTML5 – which wants to work with open standards and hence is at odds with MP3.

So how does this affect me and my home audio system?  Glad you asked.

You may recall that the system consists of 2 physical zones, 4 general-purpose streaming zones and one special-purpose streaming zone.  It’s the general-purpose streaming zones that I use extensively when I’m not at home – ie, at work or in the car.  And despite advancements in the manner by which my intranet resources are made publicly “available”, the real truth is that using the streaming zones has always been a two-part affair; part one is to interact with the system using a browser, part two is to connect to the zone using a program on the client device.

Granted, quite often I can eschew part one, as the zone is loaded and good-to-go as soon as the client connects.  But one thing that really dogged me incessantly – besides security considerations that I won’t go into here – is the absence of any ability to play a single track without having to leave the web browser.

Yes, I’m talking about a desire to implement an audio client within the browser itself.

Now, Flash is capable of doing this.  And while Shelly’s phone doesn’t support Flash (argh), the truth is that Flash isn’t completely suited to the next logical step in this thought process – which is, replacing the streaming zones with a webpage and embedded player.  I mean, I could code a Flash app, but trust me when I say that that’s not going to happen.

But would could happen – and indeed, what I really, really, really want to happen – is to code an HTML5 “app” that can do this.  This would actually solve all sorts of niggling problems, like the issue of transport control that I talked about here.  The truth is that it could actually serve as a bonafied mobile music app, optimally designed for the small screen.

It could, if… MP3 and HTML5 played nicely together in all modern browsers.

And that’s the problem I’m having right now.  I’ve worked out the interaction, I’ve figured out that the current home audio system can easily support the types of XHR calls I’d need to make, I’ve got some working knowledge of JSON… heck, I’ve even got a working implementation now of an embedded player for playing single tracks.  But to make this all work I need HTML5 and it’s DOM-accessible AUDIO element, and I need cross-browser support of MP3 files via that same AUDIO element.

Desktop support is sketchy – as is mobile support.  I find it strange that Opera on Windows doesn’t support MP3 but Opera on Android does…?  And the native Android browser is supposed to support MP3 but it actually doesn’t.  <sigh>  The truth is that there’s no point burning the proverbial midnight oil on an HTML5 music player app for my audio system if support is hit-and-miss – across the devices that I actually use.

So as much as I’d love to cuddle up close to HTML5, the unfortunate truth is that it’s playing hard to get.

Leave it to Apple

I’m waiting for the first company to come along and seamlessly integrate all of your mobile and media devices. And while I still think that Apple’s living room play needs some work, I have to admit that they made big strides in the direction of data ubiquity with today’s iOS5 and iCloud announcements.

Truthfully – I have to agree with Steve’s comments about obliterating the notion of a filesystem from the average user’s lexicon. Such a thing really should be the domain of power users and server administrators.

Although… I’d prefer a standards-compliant solution rather than entrusting Apple with all of my personal data, but that’s beside the point here. Again, it’s the seamless movement and  availability of data across multiple devices that I think is kewlio.

But… yes, there’s always a but… I see one glaring problem.

While it’s great that I may have multiple devices that can all access the same data such that that data appears to be saved locally, I think that my perspective as a family man (or at least, a person in a relationship) leaves me wanting more.

One of the questions that I get asked often by the Mrs. is “why she doesn’t have the latest photos that I’ve just taken?”. Now, at first glance, it would appear that Apple has a potential solution to this problem; put us both on iPhones (sorry DSLR) and Bob’s your uncle (cloned Apple ID issues notwithstanding).

But that’s a fairly large caveat, having to exclude my DSLR… and any non-Apple product for that matter. Even more of an issue is, does Apple allow me to determine what flies into my iCloud photostream, instantly appearing on the wifey’s phone?

And even if they did, I’m then back to having to introduce some semblance of micro-managing my photos. That’s a large part of the seamless equation that just got cancelled out.

As a family man, you quickly realize that the notion of “me” takes a back seat to the notion of “us”, such that pretty much all of the memory-gathering that you do is for the benefit of the family unit and not your own personal (nefarious?) means. Even issues of music become group debates, at least with the significant other, unless you make a point of walking around your abode rocking white earbuds. In which case one has to wonder what the value is in being able to seamlessly share your iTunes library across 10 other devices, when only one of them is likely to serve as you portable music provider.

The case for Apple’s iCloud services is certainly stronger when you start talking about the stuff that falls under the traditional domain of the cloud – namely, office productivity and document management. But the media part of the puzzle is fraught with more variables and I just don’t think that Apple has solved that equation yet.

It may be that that particular equation has no solution.