<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>bradKELLETT &#187; Music</title>
	<atom:link href="http://bradkellett.com/p/tag/music/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradkellett.com</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 04:45:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Click Wheel &#8211; Not the Solution for Phones</title>
		<link>http://bradkellett.com/p/click-wheel-not-the-solution-for-phones/</link>
		<comments>http://bradkellett.com/p/click-wheel-not-the-solution-for-phones/#comments</comments>
		<pubDate>Sat, 19 Aug 2006 01:49:38 +0000</pubDate>
		<dc:creator>Brad Kellett</dc:creator>
				<category><![CDATA[Mobile Tech]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Convergence]]></category>
		<category><![CDATA[iPod]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Music]]></category>
		<category><![CDATA[Nokia]]></category>
		<category><![CDATA[Phone]]></category>
		<category><![CDATA[Samsung]]></category>

		<guid isPermaLink="false">http://www.pantsland.com/2006/08/19/click-wheel-not-the-solution-for-phones/</guid>
		<description><![CDATA[To begin, I&#8217;m not one to bad mouth convergence. While I have no real use for a music phone, I certainly don&#8217;t have a problem with manufacturers combining an audio player and a phone &#8211; it does seem like a good match. What I do have a problem with, is the fact that many are [...]]]></description>
			<content:encoded><![CDATA[<p><img width="150" height="115" style="border: thin solid ; float: right" src="http://www.pantsland.com/wp-content/uploads/2006/08/WindowsLiveWriter/ClickWheelNottheSolutionforPhones_A641/i300_launch_thumb%5B1%5D1.jpg" /> To begin, I&#8217;m not one to bad mouth convergence. While I have no real use for a music phone, I certainly don&#8217;t have a problem with manufacturers combining an audio player and a phone &#8211; it does seem like a good match. What I do have a problem with, is the fact that many are trying to take the interface of one very popular music player and make it work on a mobile handset.</p>
<p>Of course, the device I&#8217;m referring to is the iPod, and the interface is the click (or scroll) wheel. This input device is great in the audio player space, but it was not designed as, and will never work as, an input device for a phone.</p>
<p>Two recent handsets that come to mind are the Samsung i300/i310 and the LG KV2400. Both are respectable devices in their own right, especially with Samsung&#8217;s 4GB/8GB hard drives, yet both spoil functionality by using a click wheel.</p>
<p>One of the biggest problems with adding a click wheel to a phone is the space constraints. While the iPod&#8217;s wheel is very easy to use, when you reduce its size and place it with a myriad of other buttons, usability is severally compromised. Nokia, for once, have actually taken the right step on this issue &#8211; their N91 music phone still uses traditional phone navigation, and modifies the music player to accommodate this &#8211; the addition of non-click wheel music control keys is the icing on the cake.</p>
<p>I do hope that the trend I&#8217;m seeing of adding a click wheel to a phone does not continue, and that manufacturers wake up to the face that the usability of the handset should not be compromised to add a &#8216;cool factor&#8217; to the music side of things.</p>
]]></content:encoded>
			<wfw:commentRss>http://bradkellett.com/p/click-wheel-not-the-solution-for-phones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

