Tuesday 3 June 2014, 10:56
There have been lots of comments from you and responses from Dan and the BBC iPlayer team. Comments can be a little hard to find so I though it would be useful to gather some of the key points together.
"Averaged across all of these criteria, 5% of respondents said they felt the new BBC iPlayer was worse than the old BBC iPlayer, 58% felt it was better, 33% felt it was the same and 5% said they didn't know."A word cloud of feedback on the new iPlayer from the independent user research
"The data we used for making this decision was entirely usage based. We have been monitoring the number of plays for radio on demand content on a monthly basis for the last 6 months. In terms of figures, taking the month of April 2014, we saw that radio usage on TVs made up 1% of the total radio usage across devices. Similarly, when compared to all audio and video usage on TVs, that figure drops below 1%. I understand this does not give any comfort but this decision was not taken lightly..."
Andrew Scott (General Manager, BBC iPlayer Radio) also commented:
"...we are currently evaluating how best to bring Radio to connected TV devices in a way that will be more widely used, probably as a combination of an application on the TV itself (which is a fairly expensive business when you take into account the testing across different TV manufacturers and models) and devices like Google Chromecast integrated with the iPlayer Radio mobile application in a similar way to how we integrated support for Apple Airplay.
We've read all of your comments here and I'd be really interested to hear more of your thoughts on this – please email email@example.com..."
"We are currently in the process of consolidating the number of separate iPlayer codebases we develop and maintain in order to provide the best value for money from our fixed funding. For example, prior to the launch of the new iPlayer, we were maintaining 3 separate codebases for computer browsers, tablet browsers and mobile browsers – we now have a single responsive codebase that serves all browsers. Similarly, in the TV domain, we are consolidating around a single HTML codebase. In the mobile apps domain, we have 2 codebases – one for Android devices, one for iOS devices. The market share of Windows Phone 8 doesn’t yet justify the cost of a developing and maintaining a full native app (as @DBOne mentions this isn’t just about current share of handset sales). We have however, been able to update the previous Windows Phone 8 wrapper app..."
Nick Reynolds is Editor, BBC Internet blog
Join the discussion...
Monday 2 June 2014, 10:04
Wednesday 4 June 2014, 08:48