<?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>Observation and Design &#187; android</title>
	<atom:link href="http://blog.richardstowey.co.uk/tag/android/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.richardstowey.co.uk</link>
	<description>Richard Stowey&#039;s localised view of the world.</description>
	<lastBuildDate>Thu, 08 Dec 2011 14:27:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Information Architecture Starts at Home</title>
		<link>http://blog.richardstowey.co.uk/2011/03/information-architecture-starts-home/</link>
		<comments>http://blog.richardstowey.co.uk/2011/03/information-architecture-starts-home/#comments</comments>
		<pubDate>Mon, 07 Mar 2011 14:53:17 +0000</pubDate>
		<dc:creator>Richard Stowey</dc:creator>
				<category><![CDATA[Information Architecture]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[benefits]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[grouping]]></category>
		<category><![CDATA[IA]]></category>
		<category><![CDATA[information architecture]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[operating system]]></category>
		<category><![CDATA[organisation]]></category>
		<category><![CDATA[smart phones]]></category>

		<guid isPermaLink="false">http://blog.richardstowey.co.uk/?p=603</guid>
		<description><![CDATA[At it&#8217;s highest level, Information Architecture is described by Wikipedia as the art of expressing a model or concept of information. In laymans terms, and within my day-to-day work as a Digital Project Manager, it is methods of organising and labelling websites and applications. Information Archiecture improves user interaction and experience by making content easy to find because of it&#8217;s nomenclature and grouping. Information architecture (IA) is the art of... <a href="http://blog.richardstowey.co.uk/2011/03/information-architecture-starts-home/"> Read entire post</a>]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="aligncenter" src="http://farm6.static.flickr.com/5098/5485817879_97f867c5a6.jpg" alt="Android Travel Screen" width="500" height="305" /></p>
<p>At it&#8217;s highest level, Information Architecture is described by Wikipedia as the art of expressing a model or concept of information. In laymans terms, and within my day-to-day work as a <a target="_blank" title="Digital Project Manager" href="http://www.richardstowey.co.uk">Digital Project Manager</a>, it is methods of organising and labelling websites and applications.</p>
<p><span id="more-603"></span><strong>Information Archiecture </strong>improves user interaction and experience by making content easy to find because of it&#8217;s nomenclature and grouping.</p>
<blockquote><p>Information architecture (IA) is the art of expressing a model or concept of information used in activities that require explicit details of complex systems. <em>- Wikipedia</em></p></blockquote>
<p>These days, whether people realise it or not, Information Architecture is actually performed by a lot more people, on-the-fly, every day!</p>
<p>Modern smart phones including Android, iPhone, Blackberryor even Nokia allow users to manage and group the content on their phones. This of course stems from the introduction of downloadable applications. People can simply drag and drop (or select and move) their applications into groups on different screens. For example, I have screens set up for the following:</p>
<ul>
<li>Travel</li>
<li>Calendar</li>
<li>Popular Items</li>
<li>Social Applications</li>
<li>Phone settings and search</li>
</ul>
<p>These theoretical groups allow me to manage the contents and applications within my phone into more manageable screens. If I can remember the rough subject of each screen then I&#8217;m sure to find other applications nearby.</p>
<p>Simply having the ability to rearrange the icons on my android phone makes me want to arrange them into groups, categorizing what they are to make them easier to find.</p>
<p>So, more and more people are performing the art of <strong>Information Architecture</strong>, without even realising it!</p>
<p><em>Photo: <a target="_blank" title="Android Travel Screen by Richard Stowey, on Flickr" href="http://www.flickr.com/photos/richardstowey/5485817879/">Android Travel Screen by Richard Stowey, on Flickr</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.richardstowey.co.uk/2011/03/information-architecture-starts-home/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quality of Text Input on a Handheld Device</title>
		<link>http://blog.richardstowey.co.uk/2011/01/text-input-handheld-device/</link>
		<comments>http://blog.richardstowey.co.uk/2011/01/text-input-handheld-device/#comments</comments>
		<pubDate>Sat, 15 Jan 2011 20:22:43 +0000</pubDate>
		<dc:creator>Richard Stowey</dc:creator>
				<category><![CDATA[Product Design]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[HTC Hero]]></category>
		<category><![CDATA[input devices]]></category>
		<category><![CDATA[ipad]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[keyboard]]></category>
		<category><![CDATA[keypad]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[Samsung Galaxy Tab]]></category>
		<category><![CDATA[text input]]></category>
		<category><![CDATA[touch screens]]></category>

		<guid isPermaLink="false">http://blog.richardstowey.co.uk/?p=430</guid>
		<description><![CDATA[I&#8217;ve used a few handheld devices over the years, and as there are a few more on the market now, but I&#8217;m wondering whether any of them are as efficient as they could be. The Psion, Tapwave Zodiac, Nokia mobile phones, iPhone, iPad, Blackberry, HTC Hero and Samsung Galaxy Tab &#8211; It&#8217;s interesting how the text input on these devices has developed over time and it got me wondering which... <a href="http://blog.richardstowey.co.uk/2011/01/text-input-handheld-device/"> Read entire post</a>]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="aligncenter" src="http://farm3.static.flickr.com/2544/3860586028_91fc01ed6f.jpg" alt="Blackberry Curve black closeup" width="500" height="333" /></p>
<p>I&#8217;ve used a few handheld devices over the years, and as there are a few more on the market now, but I&#8217;m wondering whether any of them are as efficient as they could be.</p>
<p><span id="more-430"></span>The Psion, Tapwave Zodiac, Nokia mobile phones, iPhone, iPad, Blackberry, HTC Hero and Samsung Galaxy Tab &#8211; It&#8217;s interesting how the text input on these devices has developed over time and it got me wondering which input method is the most efficient. But there are lots of things which affect how good an input is.</p>
<p>Weighing them all up provides an accurate view of which one is the best. So bearing that in mind, I&#8217;ve separated the devices I&#8217;ve used into the types of input in order to compare.</p>
<p>I&#8217;ve rated them from a 1-5 (1=low, 5=high)</p>
<table cellpadding="5">
<tbody>
<tr>
<td></td>
<td>speed</td>
<td>accuracy</td>
<td>feedback</td>
<td>accessibility</td>
<td>difficulty</td>
<td>learning curve</td>
<td>usability</td>
</tr>
<tr>
<td>physical QUERTY keyboard</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>5</td>
<td>1</td>
<td>1</td>
<td>5</td>
</tr>
<tr>
<td>physical numerical keyboard</td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>5</td>
<td>1</td>
<td>1</td>
<td>4</td>
</tr>
<tr>
<td>touch screen keyboard (iPhone/iPad)</td>
<td>2</td>
<td>3</td>
<td>1</td>
<td>4</td>
<td>3</td>
<td>3</td>
<td>4</td>
</tr>
<tr>
<td>touch screen keyboard (Android)</td>
<td>2</td>
<td>3</td>
<td>4</td>
<td>4</td>
<td>3</td>
<td>3</td>
<td>4</td>
</tr>
<tr>
<td>Swype touch keyboard (Android)</td>
<td>3</td>
<td>4</td>
<td>1</td>
<td>4</td>
<td>3</td>
<td>4</td>
<td>4</td>
</tr>
<tr>
<td>pen handwriting recognition</td>
<td>1</td>
<td>3</td>
<td>1</td>
<td>4</td>
<td>5</td>
<td>5</td>
<td>2</td>
</tr>
</tbody>
</table>
<p>The early transition from QUERTY keyboard to was clearly met with issues. The pen input of the Tapwave Zodiac and other Palm based devices has definitely improved with the use of finger based touch inputs. I find that the next step now is to refine the devices and make them much easier to use, fool proof and really try and understand how people use their devices.</p>
<p>For me, QUERTY keyboards are still the clear winners, but they aren&#8217;t as versatile and interesting to use with other applications.</p>
<p>The next steps are ones of refinement rather than major changes, and I think that there will be a battle between the touch screen keyboard and the QUERTY keyboard for mobile devices.</p>
<p><em><a target="_blank" title="Blackberry Curve black closeup by bigpresh, on Flickr" href="http://www.flickr.com/photos/bigpresh/3860586028/">Blackberry Curve black closeup by bigpresh, on Flickr</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.richardstowey.co.uk/2011/01/text-input-handheld-device/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Swype Keyboard Review for HTC Hero on Android</title>
		<link>http://blog.richardstowey.co.uk/2011/01/swype-keyboard-review-htc-hero-android/</link>
		<comments>http://blog.richardstowey.co.uk/2011/01/swype-keyboard-review-htc-hero-android/#comments</comments>
		<pubDate>Wed, 12 Jan 2011 12:37:50 +0000</pubDate>
		<dc:creator>Richard Stowey</dc:creator>
				<category><![CDATA[Product Design]]></category>
		<category><![CDATA[Product Review]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[User Inferface Design]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[HTC Hero]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[keyboard]]></category>
		<category><![CDATA[new touch screen keyboard]]></category>
		<category><![CDATA[software review]]></category>
		<category><![CDATA[Swype]]></category>
		<category><![CDATA[typing]]></category>

		<guid isPermaLink="false">http://blog.richardstowey.co.uk/?p=485</guid>
		<description><![CDATA[Swype launched a new beta programme recently for their unique swyping keyboard. I decided to install the software on my HTC Hero and since then I&#8217;ve been trying to get used to the new way of typing on touch screen mobile phones. It works quite simply by allowing the user to draw one continuous line between the letters on the keyboard which make up your chosen words. It automatically puts... <a href="http://blog.richardstowey.co.uk/2011/01/swype-keyboard-review-htc-hero-android/"> Read entire post</a>]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="aligncenter" src="http://farm4.static.flickr.com/3054/2844541922_3f7a443107.jpg" alt="TechCrunch50 Day 2" width="500" height="375" /></p>
<p>Swype launched a new beta programme recently for their unique swyping keyboard. I decided to install the software on my HTC Hero and since then I&#8217;ve been trying to get used to the new way of typing on touch screen mobile phones.</p>
<p><span id="more-485"></span>It works quite simply by allowing the user to draw one continuous line between the letters on the keyboard which make up your chosen words. It automatically puts spaces into the sentence when you lift off your finger to start the next word.</p>
<p>Its fairly hard to get used to at first and that&#8217;s not just because of the new way of typing. There are other differences such as the layout of symbols, removal of the button to hide the keyboard and the introduction of a microphone key. it&#8217;s slightly alarming at first but you get used to it the more you use it.</p>
<p>One of the harder elements to get used to is the new predictive text (unfortunately out doesn&#8217;t iuse the same library as the default keyboard) and making edits to text you have already written. Typing words which contain double letters also seems a little tricky resulting in a little finger wiggle to get it sorted.</p>
<p>Above all it&#8217;s pretty satisfying to use especially when it comes to typing longer words and the actual user input is fairly easy and interesting. Much more thought is required when putting in the words though, and if you make a mistake on a long word then it can be annoying.</p>
<p>After using the input for a little while and to start writing this blog article, I have found that it is definitely quicker than the standard htc keyboard. That is only if you use one finger to type. If you are a multi-finger touch screen typist, then stick with that! The swype keyboard has specific other uses too, such as aboard public transport. Not having to lift your finger from the keyboard as often definitely improves accuracy!</p>
<p>The use of hardware is petty good and performance verses the default HTC Hero keyboard is definitely better and it copes with hardware lag better and more obviously.</p>
<p>Overall I would recommend giving it a try. Its now my default keyboard for most things except entering postcodes and telephone numbers! And the best bit is that you can choose when to use it, and even switch to it half way through typing!!</p>
<p><a target="_blank" title="TechCrunch50 Day 2 by magerleagues, on Flickr" href="http://www.flickr.com/photos/mager/2844541922/"><em>TechCrunch50 Day 2 by magerleagues, on Flickr</em></a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.richardstowey.co.uk/2011/01/swype-keyboard-review-htc-hero-android/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Me and My Android: Predictive Text Improvement Suggestions</title>
		<link>http://blog.richardstowey.co.uk/2009/12/me-and-my-android-predictive-text-improvement-suggestions/</link>
		<comments>http://blog.richardstowey.co.uk/2009/12/me-and-my-android-predictive-text-improvement-suggestions/#comments</comments>
		<pubDate>Sat, 19 Dec 2009 12:16:51 +0000</pubDate>
		<dc:creator>Richard Stowey</dc:creator>
				<category><![CDATA[Product Review]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[google android]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[HTC Hero]]></category>
		<category><![CDATA[htc sense]]></category>
		<category><![CDATA[Ideas]]></category>
		<category><![CDATA[Observations]]></category>
		<category><![CDATA[phone]]></category>
		<category><![CDATA[predictive text]]></category>
		<category><![CDATA[smart phone]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[solutions]]></category>
		<category><![CDATA[suggestions]]></category>
		<category><![CDATA[touch phone]]></category>
		<category><![CDATA[upgrades]]></category>
		<category><![CDATA[versions]]></category>

		<guid isPermaLink="false">http://blog.richardstowey.co.uk/?p=133</guid>
		<description><![CDATA[I&#8217;ve been using my HTC Hero, which is powered by Google Android, for a few months now and really like the jump i&#8217;ve taken from my previous Sony Ericsson K810i. It&#8217;s quite interesting to use something with such a technology jump, and it&#8217;s amazing how easily I have become used to the advances. But there are a few things I would change&#8230; I gladly accept the fact that I can... <a href="http://blog.richardstowey.co.uk/2009/12/me-and-my-android-predictive-text-improvement-suggestions/"> Read entire post</a>]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="aligncenter" title="Hero on ThinkPad by Patrick He" src="http://farm3.static.flickr.com/2628/4105393892_19328a98dc.jpg" alt="" width="500" height="332" /></p>
<p>I&#8217;ve been using my HTC Hero, which is powered by Google Android, for a few months now and really like the jump i&#8217;ve taken from my previous Sony Ericsson K810i. It&#8217;s quite interesting to use something with such a technology jump, and it&#8217;s amazing how easily I have become used to the advances. But there are a few things I would change&#8230;</p>
<p><span id="more-133"></span></p>
<p>I gladly accept the fact that I can check where I am with GPS and google maps, send twitter updates from the train, broadcast video live on the move, check my emails and upload a picture of what&#8217;s in front of me straight to facebook.</p>
<p>But there are a few things which I believe could come in handy in future iterations. These mainly lie under the category of the predictive text. The predictive text simply improves the likelyhood of typing sensible sentences by guessing what the word should be when various letters are pressed in sequence.</p>
<p>In comparison to traditional keys which are physical, where one can touch the key to locate a finger or thumb, and then press the key in two separate actions, the use of a touch screen forces a locate and confirm in one action. This, some might argue, enforces a greater reliance on improved predictive text, as opposed to traditional keyboards which require no predictive text at all.</p>
<p>So, what needs to be improved?</p>
<ol>
<li>Improve hardware spec</li>
<li>Additional or subtrational letters within words</li>
<li>Optional spaces</li>
</ol>
<p>Due to hardware issues and the occasional slowdown, the phone often thinks that the keys are pressed for longer than they actually are. This leads to a number or symbol appearing within a word and the predictive text stumbles.<strong> Symbols and numbers should be interchangeable with letters within the predictive text.</strong></p>
<p>Additional letters are often pressed by accident or missed out altogether. The preictive text within the HTC Hero <strong>should give additional options based upon adding or subtracting letters</strong>.</p>
<p>Spaces are critical to a sentence. I will often type two words, one after another without spaces in between. It would be nice if the Android predictive text would <strong>offer two-word alternatives when two words are typed next to each other</strong>.</p>
<p>So, there we have it, a few worthy upgrades to the Android / HTC Hero predictive text system. Probably, all of which have been addressed in versions of Android above 1.5. Roll on the next version, please!</p>
<p>Photo by <a target="_blank" href="http://www.flickr.com/photos/patrickhe/4105393892/">Patrick He</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.richardstowey.co.uk/2009/12/me-and-my-android-predictive-text-improvement-suggestions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

