<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Designing a touch-screen TV remote control on a smartphone</title>
	<atom:link href="http://notube.tv/2010/05/05/designing-a-touch-screen-tv-remote-control-on-a-smartphone/feed/" rel="self" type="application/rss+xml" />
	<link>http://notube.tv/2010/05/05/designing-a-touch-screen-tv-remote-control-on-a-smartphone/</link>
	<description>NoTube is a European research project exploring Semantic Web and TV</description>
	<lastBuildDate>Fri, 20 Jan 2012 15:07:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: TimS</title>
		<link>http://notube.tv/2010/05/05/designing-a-touch-screen-tv-remote-control-on-a-smartphone/#comment-534</link>
		<dc:creator><![CDATA[TimS]]></dc:creator>
		<pubDate>Fri, 01 Jul 2011 11:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.notu.be/?p=244#comment-534</guid>
		<description><![CDATA[Big advantage of gestures: you can do them without looking at your device&#039;s screen. Tap to play/pause would be a good start.

Perhaps you&#039;d consider some novel EPG designs. Navigating TV EPGs seems very clumsy, by comparison to, say, browsing content on an iPod. That&#039;s partly because iPods make excellent use of scrolling (and have done for the best part of a decade, now), and respond instantly, and maybe partly because you have a better idea what music is on your iPod than what programmes are on an EPG.

An iPad would be a really good form factor for an EPG. (An iPhone-sized smartphone is probably a little small).

A brief discussion just now suggested browsing by length (&quot;I want a 30 minute programme to watch over dinner&quot; vs. &quot;I want a feature film&quot;).]]></description>
		<content:encoded><![CDATA[<p>Big advantage of gestures: you can do them without looking at your device&#8217;s screen. Tap to play/pause would be a good start.</p>
<p>Perhaps you&#8217;d consider some novel EPG designs. Navigating TV EPGs seems very clumsy, by comparison to, say, browsing content on an iPod. That&#8217;s partly because iPods make excellent use of scrolling (and have done for the best part of a decade, now), and respond instantly, and maybe partly because you have a better idea what music is on your iPod than what programmes are on an EPG.</p>
<p>An iPad would be a really good form factor for an EPG. (An iPhone-sized smartphone is probably a little small).</p>
<p>A brief discussion just now suggested browsing by length (&#8220;I want a 30 minute programme to watch over dinner&#8221; vs. &#8220;I want a feature film&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Second screen usability &#171; NoTube blog</title>
		<link>http://notube.tv/2010/05/05/designing-a-touch-screen-tv-remote-control-on-a-smartphone/#comment-51</link>
		<dc:creator><![CDATA[Second screen usability &#171; NoTube blog]]></dc:creator>
		<pubDate>Mon, 13 Dec 2010 12:57:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.notu.be/?p=244#comment-51</guid>
		<description><![CDATA[[...] in early May we blogged about some usability issues associated with using a smartphone app as a TV remote control and ‘companion dev... in one of the NoTube prototypes developed by the BBC. Since then &#8216;second screen&#8217; apps [...]]]></description>
		<content:encoded><![CDATA[<p>[...] in early May we blogged about some usability issues associated with using a smartphone app as a TV remote control and ‘companion dev&#8230; in one of the NoTube prototypes developed by the BBC. Since then &#8216;second screen&#8217; apps [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vickybuser</title>
		<link>http://notube.tv/2010/05/05/designing-a-touch-screen-tv-remote-control-on-a-smartphone/#comment-43</link>
		<dc:creator><![CDATA[vickybuser]]></dc:creator>
		<pubDate>Tue, 11 May 2010 12:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.notu.be/?p=244#comment-43</guid>
		<description><![CDATA[Thank you both for your comments.

Karl - the settings have now been changed in Wordpress and http://blog.notu.be/feed/ now carries full posts.

Vicky]]></description>
		<content:encoded><![CDATA[<p>Thank you both for your comments.</p>
<p>Karl &#8211; the settings have now been changed in WordPress and <a href="http://blog.notu.be/feed/" rel="nofollow">http://blog.notu.be/feed/</a> now carries full posts.</p>
<p>Vicky</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://notube.tv/2010/05/05/designing-a-touch-screen-tv-remote-control-on-a-smartphone/#comment-42</link>
		<dc:creator><![CDATA[Karl]]></dc:creator>
		<pubDate>Sat, 08 May 2010 14:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.notu.be/?p=244#comment-42</guid>
		<description><![CDATA[Hello.

1)&#039;Tilt and shakes&#039; as well as voice commands are nice but there are some inherent costs within (the phone is not normally used as a remote so there is an extra learning curve for the user)

2)Could you enable the &quot;full content&quot; RSS feed, please?
Partial feeds tend to get overlooked.


Karl]]></description>
		<content:encoded><![CDATA[<p>Hello.</p>
<p>1)&#8217;Tilt and shakes&#8217; as well as voice commands are nice but there are some inherent costs within (the phone is not normally used as a remote so there is an extra learning curve for the user)</p>
<p>2)Could you enable the &#8220;full content&#8221; RSS feed, please?<br />
Partial feeds tend to get overlooked.</p>
<p>Karl</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Atherton</title>
		<link>http://notube.tv/2010/05/05/designing-a-touch-screen-tv-remote-control-on-a-smartphone/#comment-41</link>
		<dc:creator><![CDATA[Mike Atherton]]></dc:creator>
		<pubDate>Thu, 06 May 2010 12:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.notu.be/?p=244#comment-41</guid>
		<description><![CDATA[Hi Vicky - good post. My experience of various touch-screen remotes (including the Harmon Kardon Take Control and the Logitech Harmony) is that they&#039;re unfortunately mostly crap. While the idea of an adaptive remote is interesting, in practice devices have failed because:

- they&#039;ve used resistive touch screens, which aren&#039;t nearly sensitive enough. Perhaps the iphone&#039;s capacitative screen will aid this issue

- in order to be usable, the button sizes have to be far larger than on a physical remote. This leads to real-estate issues.

- and as you mention, the lack of haptic feedback make them impossible to use without looking at the screen constantly. I imagine this would be worse on a non-dedicated device (like the iphone) where it would be all too easy to quit the remote app.


And as you mention in your other point, web-enhanced TV certainly doesn&#039;t have to mean web on a TV screen. In the bad old days of OpenTV/Liberate apps (hmm - are we still there?) it was briefly popular in the US to create somewhat synchronised websites that extended a programme-brand and offered in-programme interactivity (such as answering quiz questions) in a way that overcame the backchannel limitations of the time. Reference point here: http://en.wikipedia.org/wiki/Two-Screen_Solutions

Personally I&#039;d love to see some kind of synchronised smart programme extension on my iphone - real-time tweets, IMDB trivia, Test The Nation style interactivity - far more than I&#039;d want to use the phone to control the TV itself.]]></description>
		<content:encoded><![CDATA[<p>Hi Vicky &#8211; good post. My experience of various touch-screen remotes (including the Harmon Kardon Take Control and the Logitech Harmony) is that they&#8217;re unfortunately mostly crap. While the idea of an adaptive remote is interesting, in practice devices have failed because:</p>
<p>- they&#8217;ve used resistive touch screens, which aren&#8217;t nearly sensitive enough. Perhaps the iphone&#8217;s capacitative screen will aid this issue</p>
<p>- in order to be usable, the button sizes have to be far larger than on a physical remote. This leads to real-estate issues.</p>
<p>- and as you mention, the lack of haptic feedback make them impossible to use without looking at the screen constantly. I imagine this would be worse on a non-dedicated device (like the iphone) where it would be all too easy to quit the remote app.</p>
<p>And as you mention in your other point, web-enhanced TV certainly doesn&#8217;t have to mean web on a TV screen. In the bad old days of OpenTV/Liberate apps (hmm &#8211; are we still there?) it was briefly popular in the US to create somewhat synchronised websites that extended a programme-brand and offered in-programme interactivity (such as answering quiz questions) in a way that overcame the backchannel limitations of the time. Reference point here: <a href="http://en.wikipedia.org/wiki/Two-Screen_Solutions" rel="nofollow">http://en.wikipedia.org/wiki/Two-Screen_Solutions</a></p>
<p>Personally I&#8217;d love to see some kind of synchronised smart programme extension on my iphone &#8211; real-time tweets, IMDB trivia, Test The Nation style interactivity &#8211; far more than I&#8217;d want to use the phone to control the TV itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

