Tim Anderson's ITWriting » bbc

What next for the BBC and its world-beating website?

tim — Wed, 03 Mar 2010 10:55:50 +0000

The UK’s public broadcasting company the BBC is in the spotlight, thanks to a new strategy review and ensuing discussion. I have only just read it, because of other work, but I think it is significant. The BBC’s Director-General Mark Thompson says:

Clearly the BBC needs the space to evolve as audiences and technologies develop, but it must be far more explicit than it has been in the past about what it will not do. Its commercial activity should help fund and actively support the BBC’s public mission, and never distort or supplant that mission.
Where actual or potential market impact outweighs public value, the BBC should leave space clear for others. The BBC should not attempt to do everything. It must listen to legitimate concerns from commercial media players more carefully than it has in the past and act sooner to meet them. It needs the confidence and clarity to stop as well as to start doing things.

Why such negativity? The essence of the problem is that the BBC has been too successful for some. Commercial broadcasters and web sites have to compete with an organisation that is publically funded, and complain that it is unfair competition. The BBC demonstrates the effectiveness of the subscription model, especially when that subscription is all-but compulsory. In the UK, you have to pay the licence fee if you have equipment capable of receiving its TV broadcasts.

My main interest is in the BBC website. It is one I use constantly, and I do not think there is anything like it in the world. It offers comprehensive news, features and comment, on a site that is fast and resilient, and without the irritation of advertising. For example, if I want to know the latest state of play in financial markets, I head straight to the BBC’s Market Data page.

The absence of advertising has several benefits. First, it increases confidence in the neutrality of the site. Second, it improves performance – I’m aware that my own blog is slowed down by ad scripts, for example, and I’m not happy about it; but I’m also trying to make business sense out of running the site. Third, it improves usability in other ways, with less distraction and increased space for content. Note though that the BBC site does carry advertising when viewed from non-UK locations.

The BBC web site is an enormous success, the 44th most visited in the world according to Alexa, and the top news site (cnn.com is next at 61) unless you count Yahoo, which is something different to my mind.

So what do you do with a world leader? Cut it, apparently. The report talks about “focusing” the BBC web site by:

Halving the number of sections on the site and improving its quality by closing lower-performing sites and consolidating the rest
Spending 25% less on the site per year by 2013
Turning the site into a window on the web by providing at least one external link on every page and doubling monthly ‘click-throughs’ to external sites

This is made more explicit later in the report:

To help ensure that this refocusing takes place, the BBC will spend 25% less on BBC Online by 2013, with a corresponding reduction in staffing levels
The number of sections on the site (its ‘top-level directories’, in the form bbc.co.uk/sitename) will be halved by 2012, with many sites closed and others consolidated
New investment will be in pursuit of the five content priorities only, and there will be far fewer bespoke programme websites
BBC Online will be transformed into a window on the web with, by 2012, an external link on every page and at least double the current rate of ‘click-throughs’ to external sites.

There is an even more explicit section on BBC Online further down (pages 36-37) – the report seems to say the same thing several times with more detail on each iteration – but I won’t quote it all here. I will note that the sections identified for removal are not ones that matter to me, with the possible exception of local news:

Restricting local sites in England to news, sport, weather, travel and local knowledge (where ‘local knowledge’ means supporting BBC initiatives such as Coast and A History of the World in 100 Objects where there is local relevance, but not general feature content)

I do understand the problem here. Consider, for example, UK newspaper sites like the excellent guardian.co.uk – disclaimer – there are a few of my own contributions there. Such sites do not really make money, because they depend on synergy with print media that is in decline, not least because of advertisers turning to the web. There is a big debate in the media industry about whether to charge subscriptions for sites like these, as the New York Times has done, and will do again. However, the existence and quality of the BBC’s free site significantly impairs the prospects for subscriptions to UK newspaper sites.

This, I presume, is why the BBC intends to increase the number of external links; a small compensation for its unfair advantage.

Nevertheless, I think the BBC is mad to consider reducing its online investment. It is against the trend; the web is rising in importance, and traditional broadcasting decreasing. It is bad for the UK, for which the BBC is excellent PR and a genuine service to the world. It is bad for subscribers such as myself, enforced or not, who want the online service to get better, not worse.

Rather than cutting back on the BBC’s most strategic services, I’d favour looking again at the way the BBC is funded and what happens to the licence fee, which is an anomaly. I don’t see any reason in principle why it should not be shared with other organisations that are serving the public interest in news and media.

Why I don’t want to view bbc.co.uk through an app

tim — Wed, 17 Feb 2010 15:02:48 +0000

The BBC has announced mobile apps for BBC content, the first being for the iPhone. There is a demo posted by David Madden here:

Our aim is to develop core public service apps that bring some of the BBC’s most popular and distinctive content to mobile in a genuinely user-friendly and accessible way.

In another post Erik Huggers explains our mobile future.

I have reservations about this approach, and wonder if the BBC has been unduly influenced by Apple’s iPhone marketing – “there’s an app for that.” The iPlayer desktop application makes perfect sense for downloading and viewing video offline; but why make an app to view a web site? I can think of several objections:

1. It introduces inequality between devices. So iPhone is first. Blackberry and Android are mentioned. What about Palm WebOS? What about Windows Phone 7? Maybe Flash can help with that as a common runtime; but Flash won’t be on Windows Phone in its first release. Older devices will be left behind, even where they have decent web browsers.

2. It breaks the web. Well, one app does not break the web. But if every major web site decides it has to deliver its content through an app, what happens to hyperlinks? You can go from app to Web, I imagine, but if the target site also delivers its best mobile content through an app, what then? Imagine what the web would be like if, instead of browsing, you were constantly app-switching.

3. It moves mobile to a separate world. The truth is, there isn’t a hard and fast distinction between a mobile device and a desktop device. A laptop is mobile, but more like a desktop in terms of web browsing. What about the iPad? What about all the new form factors coming down the line? There isn’t any more reason to have apps for mobile devices than there is for desktop devices.

4. It distracts investment away from what the BBC should be doing: optimising its web site for mobile, and degrading gracefully for less powerful web browsers.

Are there cases where a BBC app might make sense? Maybe a special for the 2012 olympics, that delivers the latest results, for example? Quite possibly; but what concerns me is the idea that apps become the main way to view BBC content on a phone, rather than the web browser. It is a bad precedent, and one that I hope is not imitated by others.

Going Mobile

tim — Tue, 12 Jan 2010 15:27:18 +0000

In the back of my mind I knew that this blog looked terrible on a mobile, but I did nothing about it until @monkchips complained that it was unreadable on his HTC Magic, which runs Google Android 1.6.

I don’t have an Android device, but I grabbed the SDK, ran up the emulator, and had a look. The page took ages to load, and did not work properly even when fully loaded.

I figured “there’s a plugin for that”, and there is – several in fact. I settled on the WordPress Mobile Pack. Installed, configured, and a short time later was up and running.

I had a few hassles, mainly because most of my wordpress installation is not writeable by the web server, and this plugin needs to write themes on installation and temporary images after that, so I had to loosen permissions slightly. I then set the themes directory back to read-only, and configured the cache so that Apache will only serve images.

I still only get a score of Fair (2 fails) from the MobiReady report. Still, progress. I am ahead of bbc.co.uk which gets Bad (10 fails); but behind microsoft.com which rates Good (0 fails).

The plugin also tells me that 5% of the traffic to this site is from mobile users. More than I had expected.

Beep beep.

BBC trying out HTML 5, video element

tim — Tue, 18 Aug 2009 07:02:05 +0000

The BBC has an HTML 5 demonstration using the video element. The video itself is encoded in both Ogg and H.264. In the screenshot below I have just clicked on a navigation image to jump to a specific place in the video. The demonstration is meant to work in Firefox, Safari and Chrome, though for me it only ran in Firefox (3.5).

There is a detailed comment from the BBC’s Sam Dutton on why the proof of concept was put together here. There is an interesting remark on why the BBC is interested in this approach, which does not require a plugin like Adobe Flash or Microsoft Silverlight:

Flash and other Rich Internet Applications (RIAs) provide something like this already via timeline scripting, but RIAs are ‘black boxes’, using compilers and obfuscators to hide code and data: great if you want to protect intellectual property, whereas we needed to provide a mechanism whereby data and the code acting on it were open and accessible. HTML 5 and the jQuery JavaScript framework gave us the tools we needed without requiring extra plugins or proprietary software.

From a technical perspective, Dutton remarks that the HTML 5 solution is more efficient if you want to synchronize other elements with the playing video:

The HTML 5 audio and video elements remove the need for player plugins, work like any other HTML element in terms of styling and positioning, and standardise the programming interface for playback control. Less well known is that these elements emit a timeupdate event (at a frequency adjusted to fit available processing and memory) which removes the need to poll a player for the current time position. This makes media scripting far more efficient, since there is no need to run a loop or use setTimeout. In tests run on several machines we found that timeupdate events are emitted regularly and frequently (particularly in Firefox), whereas polling a media player for current video time is unreliable.

Dutton adds:

… it’s early days for us on this and there are a number of serious challenges before this becomes anything near mainstream – if ever.

The BBC is an influential site and its experiments will attract keen interest from those watching the evolution of web video.

Technorati Tags: adobe,microsoft,flash,bbc,video,firefox,chrome,safari

BBC seeks web response from unconnected users

tim — Wed, 10 Jun 2009 10:19:29 +0000

This really needs a cartoonist. I thought I should grab it before it gets changed.

“The BBC was surprised by the lack of response to its latest Internet survey”

The serious point: now you have another reason not to trust web surveys.

Update: The BBC’s form is not completely daft: it says “at home” and you might be on the Internet at work or in a café. Still, that’s going to be unrepresentative of the 30% – it is exactly the sub-set which is already proven to be Internet users, whereas we most want to hear from those who are not and need to be “persuaded to go online”. Thanks to @rupertg and @putsimply on Twitter for the correction.

Technorati Tags: bbc,internet,statistics

Is Silverlight the problem with ITV Player? Microsoft, you have a problem.

tim — Sat, 18 Apr 2009 06:49:17 +0000

I sat down last night to watch a programme on ITV’s catch-up service, using the Silverlight-based ITV Player. It was watchable, but not too good. Now and again the stream would pause for buffering, and I saw the Silverlight busy icon for a while. Quality is also an issue. Sometimes it is great; sometimes it is horribly pixelated.

I took a look at the ITV forums. It seems to be a common problem. The Best of ITV section is dominated by complaints. Some are from an aggrieved minority running Linux or PowerPC Macs; but there are plenty of others. My experience is relatively good; other issues include broadcasts that only play the ads; or codec issues; or streams failing completely half way through a programme. Here’s a sample:

Believe me guys even if you had Windows OS the player still wouldn’t work its completely rubbish; 6 times i’ve tried to watch Britains Got Talent and it either vanishes, or skips etc.
Rubbish, rubbish, rubbish! BBC iPlayer is excellent compared to this, i’m quite disappointed!

Readers of this blog will know that I have nothing against Silverlight, though my interest is more in the application development side than video streaming. Still, the impact of one on the other should not be discounted. You can guess what the pundits in the ITV forum are calling for. It’s Adobe Flash, because they have seen it working well for the BBC and elsewhere.

Now transition to the development team as they put forward the question of whether to use Flash or Silverlight for their upcoming RIA (Rich Internet Application) project. If the exec responsible struggled to watch ITV player the night before, thanks as far as she can tell to the Silverlight plug-in, that becomes a factor in the outcome.

I understand why people blame Silverlight for these problems; but I realise that this may be wrong, cross-platform issues aside. Maybe ITV has inadequate servers; or there is some other technical issue, and Silverlight is innocent.

If you know the answer to this, please let me know or comment below.

Microsoft must realise, though, that this is the most visible use of Silverlight for many UK folk. Some may also remember how BBC iPlayer transformed its reputation when it moved from using primarily Microsoft technology – though not Silverlight, and made worse by poor peer-to-peer client software – to Adobe’s Flash platform. I suggest that Redmond’s finest give it some attention; though who knows, it may be too late.

Technorati Tags: silverlight,flash,adobe,microsoft,itv player,bbc iplayer

BBC adopting Adobe AIR for platform-neutral iPlayer downloads

tim — Tue, 14 Oct 2008 16:29:55 +0000

Just noticed that the BBC is adopting Adobe AIR to create a platform-neutral download client for iPlayer. Erik Huggers says:

Today, we are announcing that in partnership with Adobe we are building a platform-neutral download client.

Using Adobe Integrated Runtime (AIR), we intend to make BBC iPlayer download functionality available on Mac, Linux and Windows for the first time later this year. Whatever platform you use, you’ll now be able to download TV programmes from the BBC to watch later.

This follows much criticism of the BBC for its original Windows-only iPlayer.

Looks like Adobe has the BBC in its grip, technology wise, having ousted Microsoft from iPlayer completely – though I believe it is still experimenting with Silverlight’s Deep Zoom.

Technorati tags: adobe, microsoft, bbc, air, iplayer

BBC iPlayer supporting H.264 in Flash – what’s the point of downloading now?

tim — Wed, 13 Aug 2008 19:31:25 +0000

The BBC’s streamed catch-up broadcasting, iPlayer, is about to be upgraded to the high-definition H.264 standard, according to this post, from the BBC’s Head of Digital Media Anthony Rose.

He says that the “Play high quality” option will be available “from this week”, though I couldn’t see any sign of it on a brief sampling of available content.

The question: where does this leave the download service, based on peer-to-peer file sharing? This is the thing that caused me considerable hassle this time last year, and which also drew criticism because it is Windows-only.

By contrast, the Flash-based embedded video seems to have performed as smoothly as Flash usually does.

When Flash streaming was introduced, the BBC said that the download option would remain for higher-quality viewing, but with H.264 Flash that argument has little force. It is still comforting to have a downloaded file, in case your Net connection fails or becomes congested, but other than that there is little advantage. My guess is that it will wither. Supporting both must be expensive.

It is unfortunate for Microsoft, whose technology is losing out to Adobe’s at the BBC, particularly since Silverlight would probably have worked nicely in this context. Unfortunately the old iPlayer is not Silverlight, but based on Windows Media Player, known to be hassle-prone as well as being single platform.

Technorati tags: bbc, iplayer, flash, silverlight, h.264

BBC iPlayer beta firewall issues

tim — Thu, 03 Jul 2008 09:39:53 +0000

I was disappointed when my first efforts to use the BBC’s streaming iPlayer beta failed. Whatever content I chose, I got the message: This content isn’t available at the moment.

Right-clicking the player lets you copy a further error message, which says:

Title: akamai:AkamaiServiceError.AKAMAI_API
Description: Connection attempt failed
Code: 18

At first I blamed beta unreliability; then when it continued I wondered if it could be a firewall issue. I use Microsoft’s ISA Server. I looked at the log, and noticed that traffic on port 1935 was being blocked. I added a new protocol which I called iPlayer, for outbound TCP traffic on port 1935. I added this to the web access rule in ISA Server. Now it works.

It’s a great service. The quality is fine. For some reason I care deeply about audio quality when listening to music, but when it comes to most video content, I mind much less.

Note: I don’t know if this is the only firewall issue with iPlayer, or if the port may change in future. Others have fixed similar issues just by clearing cookies or their browser cache. All I can say is that this fixed the problem for me.

I also think that the BBC’s player could display a more helpful error message; and I’d like to see technical information on what the requirements are. I couldn’t find anything useful here.

Technorati tags: iplayer, isa server, firewall, bbc, akamai

The BBC’s Global Visual Language

tim — Thu, 03 Jul 2008 09:04:35 +0000

Not a pictorial version of Esperanto; rather, a set of design guidelines for bbc.co.uk:

The global visual language is a set of guidelines which aim to bring more consistency to the site by introducing an underlying design grid and consistent design patterns, icons, buttons, image sizes and a pan-BBC audio/video player.

according to BBC interaction designer and blogger Ben Hanbury. His main focus is the revised iPlayer site, which has the last seven days of the BBC’s TV and radio output available on-demand via a media player based on Flash – Adobe must be delighted.

That said, the new iPlayer site is one of the few examples I’ve known where Flash content does not play reliably. On my normal PC I get the useless and inaccurate message, “This content isn’t available at the moment.” Seems to be a firewall issue. I’ll post again if I can work out exactly what the problem is.

Technorati tags: bbc, iplayer, adobe, flash