<?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/"
		>
<channel>
	<title>Comments on: Symbian, Nokia and Java</title>
	<atom:link href="http://aniszczyk.org/2009/11/02/symbian-nokia-and-java/feed/" rel="self" type="application/rss+xml" />
	<link>http://aniszczyk.org/2009/11/02/symbian-nokia-and-java/</link>
	<description>work. life. open source. diatribes.</description>
	<lastBuildDate>Thu, 29 Jul 2010 04:49:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Dave</title>
		<link>http://aniszczyk.org/2009/11/02/symbian-nokia-and-java/comment-page-1/#comment-1403</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 05 Nov 2009 03:42:32 +0000</pubDate>
		<guid isPermaLink="false">http://aniszczyk.org/?p=1375#comment-1403</guid>
		<description>&quot;On a side note, this is one area I think Apple is brilliant in. Have you noticed that their mobile phones have had the same LCD size for a few generations?&quot;

But they managed to achieve that only by choosing an impressive resolution at the time they launched two and a half years ago. What happens when that fixed resolution starts making their phone look primitive? Droid already has almost twice the resolution, so it probably won&#039;t be too long now. Will they ever be able to bump it up, or are they held captive by their 100,000 applications that have all been designed down to the pixel?

Sometimes avoiding a problem is a good strategy, but it can also make things much more difficult when you finally have no choice but to solve it.</description>
		<content:encoded><![CDATA[<p>&#8220;On a side note, this is one area I think Apple is brilliant in. Have you noticed that their mobile phones have had the same LCD size for a few generations?&#8221;</p>
<p>But they managed to achieve that only by choosing an impressive resolution at the time they launched two and a half years ago. What happens when that fixed resolution starts making their phone look primitive? Droid already has almost twice the resolution, so it probably won&#8217;t be too long now. Will they ever be able to bump it up, or are they held captive by their 100,000 applications that have all been designed down to the pixel?</p>
<p>Sometimes avoiding a problem is a good strategy, but it can also make things much more difficult when you finally have no choice but to solve it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Aniszczyk</title>
		<link>http://aniszczyk.org/2009/11/02/symbian-nokia-and-java/comment-page-1/#comment-1394</link>
		<dc:creator>Chris Aniszczyk</dc:creator>
		<pubDate>Tue, 03 Nov 2009 14:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://aniszczyk.org/?p=1375#comment-1394</guid>
		<description>I didn&#039;t mean to directly compare Apple and Nokia mobile application development, I was more stating the problem of developing user interfaces for mobile devices, whether they are phones or not. In the past, I had to target Windows Mobile devices, Nokia Communicators, Motorola and portable devices. One problem was UI layout but that wasn&#039;t the only problem. There was the &quot;clam-shell dual ui&quot; issue like I mentioned, the other was something I&#039;ll call device normalization. Some devices have different input mechanisms... from a pointer, a touch screen to smart buttons. Should you display your user interface differently based on the input? Buttons may be OK if the device has a touch screen, but not if there&#039;s just smart buttons. That&#039;s part of the challenge.

Thanks for responding by the way.</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t mean to directly compare Apple and Nokia mobile application development, I was more stating the problem of developing user interfaces for mobile devices, whether they are phones or not. In the past, I had to target Windows Mobile devices, Nokia Communicators, Motorola and portable devices. One problem was UI layout but that wasn&#8217;t the only problem. There was the &#8220;clam-shell dual ui&#8221; issue like I mentioned, the other was something I&#8217;ll call device normalization. Some devices have different input mechanisms&#8230; from a pointer, a touch screen to smart buttons. Should you display your user interface differently based on the input? Buttons may be OK if the device has a touch screen, but not if there&#8217;s just smart buttons. That&#8217;s part of the challenge.</p>
<p>Thanks for responding by the way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: a_car_lover</title>
		<link>http://aniszczyk.org/2009/11/02/symbian-nokia-and-java/comment-page-1/#comment-1392</link>
		<dc:creator>a_car_lover</dc:creator>
		<pubDate>Tue, 03 Nov 2009 13:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://aniszczyk.org/?p=1375#comment-1392</guid>
		<description>I don&#039;t want to start a debate on Nokia vs Apple, but the blog is comparing apples to oranges (no pun intended) and even there, the orange is described as a lemon.

First of all, Nokia has a few dozen smart phones in the market compared to essentially one product (and its three variants) by Apple. The business model and markets addressed by either company is different and hence, the strategy with respect to different screen sizes cannot be compared directly. 

Secondly, even though there are different screen sizes for Nokia&#039;s smart phones, over the last 3 years or so, they have been coming in the same resolution - QVGA (320x240 pixels) in either landscape or portrait modes. The recent touch screens (S60 5th edition) are 640x360 pixels and again, the resolution is consistent, though the screen size differs according to the target demography. So as a developer, UI layout is not as difficult as the blog makes it out to be.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t want to start a debate on Nokia vs Apple, but the blog is comparing apples to oranges (no pun intended) and even there, the orange is described as a lemon.</p>
<p>First of all, Nokia has a few dozen smart phones in the market compared to essentially one product (and its three variants) by Apple. The business model and markets addressed by either company is different and hence, the strategy with respect to different screen sizes cannot be compared directly. </p>
<p>Secondly, even though there are different screen sizes for Nokia&#8217;s smart phones, over the last 3 years or so, they have been coming in the same resolution &#8211; QVGA (320&#215;240 pixels) in either landscape or portrait modes. The recent touch screens (S60 5th edition) are 640&#215;360 pixels and again, the resolution is consistent, though the screen size differs according to the target demography. So as a developer, UI layout is not as difficult as the blog makes it out to be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zviki</title>
		<link>http://aniszczyk.org/2009/11/02/symbian-nokia-and-java/comment-page-1/#comment-1391</link>
		<dc:creator>Zviki</dc:creator>
		<pubDate>Tue, 03 Nov 2009 13:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://aniszczyk.org/?p=1375#comment-1391</guid>
		<description>I&#039;ve been (and still) using Symbian S60 since the very first phone Nokia came up with, the 7650. I love it and its&#039; market share is impressive. Yet, it never did fulfill its&#039; promise to bring a plethora of applications. Possibly because it failed to attract developers. It seems that Nokia will shift to Maemo eventually.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been (and still) using Symbian S60 since the very first phone Nokia came up with, the 7650. I love it and its&#8217; market share is impressive. Yet, it never did fulfill its&#8217; promise to bring a plethora of applications. Possibly because it failed to attract developers. It seems that Nokia will shift to Maemo eventually.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
