<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="http://blogs.forum.nokia.com/styles/rss.css" type="text/css"?>
<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns="http://purl.org/rss/1.0/"
>
 <channel rdf:about="http://blogs.forum.nokia.com/rss.php?blogId=43602&amp;profile=rss10">
  <title>Gabor Torok&#039;s Forum Nokia Blog</title>
  <link>http://blogs.forum.nokia.com/blog/gabor-toroks-forum-nokia-blog</link>
  <description>&lt;p&gt;Software architect working in Symbian/S60 area since 2000 and still being enthusiastic about mobility. Please visit my introduction page on Forum Nokia Champions web page.&lt;/p&gt;
</description>
    <dc:creator>tote_b5</dc:creator>
  <dc:date>2009-11-23T21:38:16Z</dc:date>
  <admin:generatorAgent rdf:resource="http://www.lifetype.net" />
  <items>
   <rdf:Seq>
       <rdf:li rdf:resource="http://blogs.forum.nokia.com/blog/gabor-toroks-forum-nokia-blog/2008/07/18/static-vs-active-application-icons" />
       <rdf:li rdf:resource="http://blogs.forum.nokia.com/blog/gabor-toroks-forum-nokia-blog/2008/01/13/touch-less-ui-accelerometer" />
      </rdf:Seq>
  </items> 
 </channel>
  <item rdf:about="http://blogs.forum.nokia.com/blog/gabor-toroks-forum-nokia-blog/2008/07/18/static-vs-active-application-icons">
  <title>Static vs active application icons</title>
  <link>http://blogs.forum.nokia.com/blog/gabor-toroks-forum-nokia-blog/2008/07/18/static-vs-active-application-icons</link>
  <dc:description>&lt;p&gt;
I found an interesting blog about mobile interaction design at &lt;a href=&quot;http://sender11.typepad.com/sender11/2008/06/dead-icons-must.html&quot;&gt;Sender 11&lt;/a&gt;
(whatever that name means). The point of the article is that in order
to make application icons more attractive and provide a better
user-experience, the icons should refresh their content from time to
time and show &amp;quot;relevant&amp;quot; information to the user instead of being
passive and showing only static information.&lt;br /&gt;
&lt;br /&gt;
I like the idea. As one of the &lt;a href=&quot;http://sender11.typepad.com/sender11/2008/06/dead-icons-must.html#comment-119547678&quot;&gt;comments&lt;/a&gt; says &lt;span style=&quot;font-style: italic&quot;&gt;with Nokia S60s you can now build interfaces wiht live icons like these in web-run-time and create a whole menu as a widget.&lt;/span&gt;
Well, I don&#039;t know much about widgets, but I can imagine that it would
work. For example, the whole Application Shell could make use of Web
run-time and show application entry points (i.e. icons) as widgets with
their always-changing behavior. Even more, the idea of Active Idle
could be replaced by an active Application Shell, too. Some pixels
could also be saved from precious screen real-estate (e.g. unread
messages) by letting the application icons show information.&lt;br /&gt;
&lt;br /&gt;
What could different applications show to the user? Here&#039;s a by far incomplete list out of my mind:
&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Calendar: indication about events nearby&lt;/li&gt;
	&lt;li&gt;Messaging: unread messages (sms, e-mail, etc.)&lt;/li&gt;
	&lt;li&gt;Bluetooth connectivity: enabled vs disabled, transfer in progress&lt;/li&gt;
	&lt;li&gt;WLAN connectivity: enabled vs disabled, number of hotspots nearby&lt;/li&gt;
	&lt;li&gt;Maps: known (i.e. pre-recorded) locations nearby&lt;/li&gt;
	&lt;li&gt;Clock: time&lt;/li&gt;
	&lt;li&gt;Music Player: some information about tune being played (with scrolling, for example)&lt;/li&gt;
	&lt;li&gt;RSS reader: new, unread items&lt;/li&gt;
	&lt;li&gt;etc.&lt;/li&gt;
&lt;/ul&gt;
Could you add more?&lt;br /&gt;
&lt;br /&gt;
Tote&lt;br /&gt;
&lt;a href=&quot;http://mobile-thoughts.blogspot.com/2008/07/static-vs-active-application-icons.html&quot;&gt;mobile-thoughts.blogspot.com&lt;/a&gt;&lt;br /&gt;</dc:description>
      
    <dc:subject>S60</dc:subject>
      
    <dc:subject>UI</dc:subject>
      
    <dc:subject>Symbian</dc:subject>
      
    <dc:subject>Development</dc:subject>
     
    
  <dc:date>2008-07-18T12:16:48Z</dc:date>
    <dc:creator>tote_b5</dc:creator>
 </item>
  <item rdf:about="http://blogs.forum.nokia.com/blog/gabor-toroks-forum-nokia-blog/2008/01/13/touch-less-ui-accelerometer">
  <title>Touch(less) UI + Accelerometer</title>
  <link>http://blogs.forum.nokia.com/blog/gabor-toroks-forum-nokia-blog/2008/01/13/touch-less-ui-accelerometer</link>
  <dc:description>&lt;p&gt;We all know &lt;a href=&quot;http://www.apple.com/iphone/&quot;&gt;iPhone&lt;/a&gt;. Even though it&amp;#39;s not available in Hungary as of yet, I&amp;#39;ve already had the chance to hold it in my hands and play with it. &lt;span style=&quot;font-weight: bold&quot;&gt;It&amp;#39;s simply great&lt;/span&gt;.
People say that it&amp;#39;s because of the touch UI, but I don&amp;#39;t believe that.
It&amp;#39;s not that simple. Lots of other manufacturers have already made
phones with touch support, but for some reason the success of their
products is not even comparable with iPhone&amp;#39;s. I think it&amp;#39;s because of
Apple&amp;#39;s approach to user interface, &lt;span style=&quot;font-weight: bold&quot;&gt;more importantly to user experience&lt;/span&gt;. They made it as simple as possible and it will be very hard for phone vendors to compete with it.&lt;br /&gt;&lt;br /&gt;Motorola announced their &lt;a href=&quot;http://www.phonemag.com/ces-2008-motorola-rokr-e8-music-cellphone-01151.php&quot;&gt;ROKR E8&lt;/a&gt; phone at &lt;a href=&quot;http://www.cesweb.org/default.asp&quot;&gt;CES 2008&lt;/a&gt;. It&amp;#39;s a touch-driven phone, needless to say. The coolest feature that I found is that it &lt;span style=&quot;font-weight: bold&quot;&gt;doesn&amp;#39;t have a physical keyboard&lt;/span&gt;, but it &lt;span style=&quot;font-weight: bold&quot;&gt;dynamically shows always the relevant keys&lt;/span&gt; based on what feature/program is being used at the moment. I remember of a patent that I have read about over at &lt;a href=&quot;http://www.intomobile.com/2007/11/23/another-day-another-nokia-patent-dual-screens.html&quot;&gt;IntoMobile&lt;/a&gt;:
Nokia had patented their invention of a dual-screen phone with touch
support. My first reaction to seeing the drawing from the patent that
the keyboard layout could be displayed on one of the screens and it
could be dynamic: sometimes &lt;a href=&quot;http://en.wikipedia.org/wiki/QWERTY&quot;&gt;QWERTY&lt;/a&gt;, sometimes &lt;a href=&quot;http://upload.wikimedia.org/wikipedia/commons/thumb/f/f9/Phone_Numberblock_ITU-T_E.161.svg/222px-Phone_Numberblock_ITU-T_E.161.svg.png&quot;&gt;ITU-T&lt;/a&gt;, sometimes something else, something relevant. I&amp;#39;m very happy to see it to come true.&lt;br /&gt;&lt;br /&gt;You might have already heard about that Nokia was planning to add &lt;a href=&quot;http://www.mobiletechnews.com/info/2007/07/02/125315.html&quot;&gt;tactile feedback&lt;/a&gt;
support to their future phones, which means a little buzz when user
presses one area of the (touch)screen. Very interestingly very similar
to what Motorola has just come up with. You know, one of the biggest
constraints of using a mobile phone instead of e.g. a laptop is screen
size. And the size of the screen has so far been limited 1: by the &lt;span style=&quot;font-style: italic&quot;&gt;device size&lt;/span&gt; (it must fit into one&amp;#39;s pocket), 2: it had to &lt;span style=&quot;font-style: italic&quot;&gt;have a keyboard&lt;/span&gt;. It seems that the &lt;span style=&quot;font-weight: bold&quot;&gt;trend for 2008 is that there will be no keyboard&lt;/span&gt; on smartphones at all. Ehm, I mean no real, physical keyboard - as opposed to virtual.&lt;br /&gt;&lt;br /&gt;Have you heard that Nokia recently submitted another patent application for &lt;span style=&quot;font-weight: bold&quot;&gt;touch&lt;u&gt;less&lt;/u&gt; UI&lt;/span&gt;? See &lt;a href=&quot;http://www.unwiredview.com/2008/01/08/first-glimpse-inside-nokia-s60-touch-going-beyond-multi-touch/&quot;&gt;Unwired View&lt;/a&gt; for more details. The basic idea described in the patent is that there would be&lt;span style=&quot;font-weight: bold&quot;&gt; sensors arrayed around the perimeter of the device&lt;/span&gt; capable of sensing finger movements in 3-D space. The user could use her fingers similarly to a touch phone, but actually &lt;span style=&quot;font-weight: bold&quot;&gt;without having to touch the screen&lt;/span&gt;.
That&amp;#39;s cool, isn&amp;#39;t it? I think the idea is not only great, because user
input will not be limited to 2-D anymore, but that I can use my thick,
dirty, bandaged, etc. fingers as well (as opposed to &amp;quot;plain&amp;quot; touch UI).
I&amp;#39;m a bit sceptic, though, how accurate it can be, whether the software
will have &lt;a href=&quot;http://en.wikipedia.org/wiki/Artificial_intelligence&quot;&gt;AI&lt;/a&gt; or the user will have to learn how to move her fingers. We&amp;#39;ll see hopefully very soon!&lt;br /&gt;&lt;br /&gt;Finally, there is one more thing I&amp;#39;d like to mention here. It&amp;#39;s the &lt;span style=&quot;font-weight: bold&quot;&gt;built-in accelerometer&lt;/span&gt;.
I&amp;#39;m pretty sure that most readers have already heard of that the newest
Nokia smartphones have built-in accelerometer. It&amp;#39;s sort of a motion
sensor that actually hasn&amp;#39;t got so much publicity so far. I was always
wondering &lt;span style=&quot;font-weight: bold&quot;&gt;why Nokia has not announced, advertised&lt;/span&gt;, etc. this piece of gadget. I mean at all. I can&amp;#39;t remember if I have ever read any articles, blogs, etc. &lt;span style=&quot;font-weight: bold&quot;&gt;from Nokia&lt;/span&gt;
about that they have put this extra hardware in their phone. You know,
an accelerometer in a mobile phone is unusal. Not only to me, but to
other people as well.&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-weight: bold&quot;&gt;Why did Nokia not advertise this?&lt;/span&gt;
If it&amp;#39;s expensive, it doesn&amp;#39;t make any sense not to advertise it. If
it&amp;#39;s cheap (I bet it is), then it doesn&amp;#39;t have to be advertised, but
then why add it to the phone at all? &lt;span style=&quot;font-style: italic&quot;&gt;Just to see what the (developer) community thinks&lt;/span&gt; about it? What kind of applications can they make out of it? Although it&amp;#39;s a good idea, &lt;span style=&quot;font-style: italic&quot;&gt;I don&amp;#39;t think it&amp;#39;s a valid business reason.&lt;/span&gt; And you know, it was also unusual that Nokia published an API for developers to use this feature - but it was &lt;span style=&quot;font-weight: bold&quot;&gt;an R&amp;amp;D API&lt;/span&gt;! Knowing Nokia and using their SDKs for ages, I would say it&amp;#39;s, again, very unusual. It&amp;#39;s like &amp;quot;&lt;span style=&quot;font-style: italic&quot;&gt;Let&amp;#39;s publish this API so that we can see what others can find out with it, but doing it so that we don&amp;#39;t have to announce it&lt;/span&gt;&amp;quot;.&lt;br /&gt;&lt;br /&gt;I wouldn&amp;#39;t be suprised if the &lt;span style=&quot;font-weight: bold&quot;&gt;accelerometer eventually had something to do with the touchless UI&lt;/span&gt;.
I have the feeling, since I&amp;#39;m a programmer, that even with the array of
transducers (see the patent) it&amp;#39;s not trivial to figure out what the
user has done with her fingers. For example, it might be very important
to know in what angle the user&amp;#39;s hand is to the device ... and this is
the point where the accelerometer comes in handy. It helps to know how
the user&amp;#39;s one hand holds the phone while making gestures with the
other. &lt;span style=&quot;font-weight: bold&quot;&gt;And this altogether is the new thing.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Originally from&lt;/strong&gt; &lt;a href=&quot;http://mobile-thoughts.blogspot.com/2008/01/touchless-ui-accelerometer.html&quot;&gt;mobile-thoughts.blogspot.com&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;Can&amp;#39;t wait to read your comments,&lt;br /&gt;&lt;br /&gt;Tote&lt;/p&gt;</dc:description>
      
    <dc:subject>Mobile OS</dc:subject>
      
    <dc:subject>UI</dc:subject>
     
    
  <dc:date>2008-01-13T01:44:19Z</dc:date>
    <dc:creator>tote_b5</dc:creator>
 </item>
 </rdf:RDF>