<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en">
<title>Risto Helin&#039;s Forum Nokia Blog</title> 
<subtitle type="html">&lt;p&gt;Works for Forum Nokia where his task is to represent Nokia in Symbian Signed and Java Verified.&lt;/p&gt;
</subtitle>
 
<updated>2009-01-02T15:05:58+02:00</updated> 
<id>http://www.lifetype.net,1.2/</id>
<link rel="alternate" type="text/html"  hreflang="en" href="http://blogs.forum.nokia.com/blog/risto-helins-forum-nokia-blog" />
 
<rights>Copyright (c) Rippe</rights>
<generator uri="http://www.lifetype.net/" version="1.2">LifeType at Forum Nokia</generator> 
 
<entry> 
<title>UE?</title>
<link rel="alternate" type="text/html" href="http://blogs.forum.nokia.com/blog/risto-helins-forum-nokia-blog/2009/01/02/ue" /> 
<id>tag:blogs.forum.nokia.com,2009-01-02:1919</id>
 
<updated>2009-01-02T15:05:58+02:00</updated> 
<published>2009-01-02T15:05:58+02:00</published> 
<summary type="html"> 
I was told that it is fashionable to use the abbreviation UX in stead of UE. Fashionable or not, I&#039;m now referring to User Experience and using the abbreviation UE.&amp;nbsp; 
 
 
What does that ...</summary> 
<author> 
 
<name>Rippe</name> 
<uri>http://blogs.forum.nokia.com/blog/risto-helins-forum-nokia-blog</uri> 
</author> 
<dc:subject>
Testing 
User Experience 
</dc:subject> 
<content type="text/html" xml:lang="en" xml:base="http://blogs.forum.nokia.com/blog/risto-helins-forum-nokia-blog"> 
&lt;p&gt;
I was told that it is fashionable to use the abbreviation UX in stead of UE. Fashionable or not, I&#039;m now referring to User Experience and using the abbreviation UE.&amp;nbsp; 
&lt;/p&gt;
&lt;p&gt;
What does that mean to you?
&lt;/p&gt;
&lt;p&gt;
For me personally, as an end user, it means that I do not need to read a manual or help to use an application on my mobile. So &amp;quot;intuitive to use&amp;quot; comes to mind. Also &amp;quot;for my device&amp;quot; is an other phrase to use. It might be interesting to use an application intended for a touch screen device on a device without a touch screen. Or vice versa. 
&lt;/p&gt;
&lt;p&gt;
I&#039;ve herd the term WOW also related to user experience. &amp;quot;WOW this looks cool!&amp;quot; I seldom get that. Maybe its my basic engineering character to get more exited on features than the looks. Well, the &lt;a href=&quot;http://www.forum.nokia.com/devices/E71&quot; target=&quot;_blank&quot;&gt;Nokia E71&lt;/a&gt; did get me all exited and provided me with a WOW to the power of 10...
&lt;/p&gt;
&lt;p&gt;
User Experience for me is also &amp;quot;working as expected&amp;quot;. I don&#039;t want the application or my device (the E71) to crash or freeze. I want to use the features which the application is supposed to have, no more no less.
&lt;/p&gt;
&lt;p&gt;
The last thing is naturally the usage security. No malicious features, my data is safe. That is partially related to the number of features.
&lt;/p&gt;
&lt;p&gt;
Are you with me? Do you as application developers see something differently?
&lt;/p&gt; 
</content> 
</entry> 
 
</feed>