<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Dutchability</title>
	
	<link>http://www.dutchability.com</link>
	<description>Home of Jeroen Bet</description>
	<lastBuildDate>Fri, 11 Mar 2011 04:25:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/Dutchability" /><feedburner:info uri="dutchability" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Screen sizes and user agent trends</title>
		<link>http://feedproxy.google.com/~r/Dutchability/~3/-49Fh1WA2Wo/</link>
		<comments>http://www.dutchability.com/screen-sizes-and-user-agent-trends/#comments</comments>
		<pubDate>Tue, 05 Oct 2010 18:35:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[user agents]]></category>
		<category><![CDATA[log files]]></category>
		<category><![CDATA[screen sizes]]></category>

		<guid isPermaLink="false">http://www.dutchability.com/?p=128</guid>
		<description><![CDATA[This week had me looking at log files for various websites I worked on. These websites are both B2B and B2C with the majority of users originating from North America. A few obervations: 1024 x 768 is no longer the most commonly used screen resolution. This surprised me somewhat, but here in North America 1280&#215;800 [...]]]></description>
			<content:encoded><![CDATA[<p>This week had me looking at log files for various websites I worked on. These websites are both B2B and B2C with the majority of users originating from North America. A few obervations:</p>
<p><strong>1024 x 768 is no longer the most commonly used screen resolution</strong>. This surprised me somewhat, but here in North America 1280&#215;800 seems to be the dominant screen resolution nowadays. Granted, it&#8217;s followed very closely by 1024 x 768, but larger resolutions combined make up for a larger share. 800 x 600 seems to be completely wiped out.</p>
<p><strong>iPhone screen resolutions total about 5% of all users.</strong> That means that 1 in every 20 visitors uses an iPhone to look at these websites,  more than Android clients (about 2%). iPads are not a significant percentage yet, except on one site I checked where they had a 3% market share.</p>
<p><strong>IE is still the dominant browser</strong>, making up for almost 55% of the browsers. The majority of IE versions used is IE8. Firefox is second followed closely by Safari (Mac, iPhone) and Chrome.<br />
Chrome on Mac is no more than 3 %.</p>
<p><strong>IE6 is still around</strong> With 5% percent of the total users, this group is as big as all iPhone users. So 1 in every 20 visitors is using IE6. Scary.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dutchability.com/screen-sizes-and-user-agent-trends/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dutchability.com/screen-sizes-and-user-agent-trends/</feedburner:origLink></item>
		<item>
		<title>Naming PDFs and other downloadable files</title>
		<link>http://feedproxy.google.com/~r/Dutchability/~3/jPTeYDgfGXM/</link>
		<comments>http://www.dutchability.com/naming-pdfs-and-other-downloadable-files/#comments</comments>
		<pubDate>Sun, 29 Aug 2010 18:38:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.dutchability.com/?p=91</guid>
		<description><![CDATA[Imagine the following scenario: while looking for specific information you came across a PDF file that had all the information in it you wanted. You downloaded the file and saved it in your documents folder. Since you didn&#8217;t have time to organize files &#8211; you never seem to have enough time &#8211; the file isn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>Imagine the following scenario: while looking for specific information you came across a PDF file that had all the information in it you wanted. You downloaded the file and saved it in your documents folder. Since you didn&#8217;t have time to organize files &#8211; you never seem to have enough time &#8211; the file isn&#8217;t renamed and sits among a couple of hundred other files.  A couple of weeks later you are trying to retrieve the file but have a hard time finding it. Sounds familiar? This happens to many people I know (me for one).</p>
<p>Wouldn&#8217;t it be nice if the webmaster had named the file something else than &#8220;info.pdf&#8221;?<br />
It&#8217;s really not so hard to give your downloadables a more descriptive name. Even a file name like &#8220;annual-report.pdf&#8221; can be made more descriptive by adding the company name and the year. It&#8217;s a simple improvement, that is easily overlooked. Just keep this in mind: if a file is for download give it a descriptive name, so your user can find it later.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dutchability.com/naming-pdfs-and-other-downloadable-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dutchability.com/naming-pdfs-and-other-downloadable-files/</feedburner:origLink></item>
		<item>
		<title>Google calendar button variety?</title>
		<link>http://feedproxy.google.com/~r/Dutchability/~3/0EkK_9IyKNs/</link>
		<comments>http://www.dutchability.com/google-calendar-button-variety/#comments</comments>
		<pubDate>Fri, 30 Jul 2010 14:33:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Calendar]]></category>

		<guid isPermaLink="false">http://www.dutchability.com/?p=67</guid>
		<description><![CDATA[Don&#8217;t you just love the choice Google offers for their &#8220;Add to Google Calendar&#8221; buttons? They even dare to call it &#8220;A variety&#8221;. Yeah sure. Worst of all, there&#8217;s no choice of using your own button or, using no button at all. Of Course when you know a little HTML it&#8217;s no problem to take [...]]]></description>
			<content:encoded><![CDATA[<p>Don&#8217;t you just love the choice Google offers for their &#8220;Add to Google Calendar&#8221; buttons? They even dare to call it &#8220;A variety&#8221;. Yeah sure.<br />
Worst of all, there&#8217;s no choice of using your own button or, using no button at all. Of Course when you know a little HTML it&#8217;s no problem to take the button out, but for CMS editors or otherwise technically challenged users it&#8217;s a pain in the freakin&#8217; butt.</p>
<a href="http://www.dutchability.com/wp-content/uploads/2010/07/google-calendar2.png"><img src="http://www.dutchability.com/wp-content/uploads/2010/07/google-calendar2.png" alt="Google&#039;s &quot;choice&quot; a calendar buttons" title="google-calendar" width="600" height="143" class="size-full wp-image-76" /></a>
<p>What would be your solution?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dutchability.com/google-calendar-button-variety/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dutchability.com/google-calendar-button-variety/</feedburner:origLink></item>
		<item>
		<title>Link your images, it’s easier for handheld devices</title>
		<link>http://feedproxy.google.com/~r/Dutchability/~3/mPtD3a6Df94/</link>
		<comments>http://www.dutchability.com/link-your-images-its-easier-for-handheld-devices/#comments</comments>
		<pubDate>Mon, 26 Jul 2010 22:07:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Usability]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://www.dutchability.com/?p=58</guid>
		<description><![CDATA[After experiencing my iPhone for the last 2 weeks, I noticed that the worst user experiences I had with websites were the ones with one-word hyperlinks. It is very hard to actually tap a one word hyper link if you have anything but the tiniest fingers. A solution for this is to make sure you [...]]]></description>
			<content:encoded><![CDATA[<p>After experiencing my iPhone for the last 2 weeks, I noticed that the worst user experiences I had with websites were the ones with one-word hyperlinks. It is very hard to actually tap a one word hyper link if you have anything but the tiniest fingers. A solution for this is to make sure you link multiple words. Not only is this better for usability &#8211; you can actually describe what happens when a user clicks the link &#8211; it also increases the probability of &#8216;hitting the target&#8217; on a mobile phone. </p>
<p>The best experience is when there&#8217;s a lot of white space around the link and/or where images are linked, for instance in big call-outs or sub navigation.  When designing Greenstar-na.com, we tried to keep this in mind.<br />
On <a href="http://greenstar-na.com/services/" target="_blank">the new Greenstar North America site</a> we tried to make both the images and the section titles clickable, to make it easy for anyone not on a PC or Mac to follow the links.</p>
<p>What are your experiences with usability of websites on mobile phones?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dutchability.com/link-your-images-its-easier-for-handheld-devices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dutchability.com/link-your-images-its-easier-for-handheld-devices/</feedburner:origLink></item>
		<item>
		<title>Hi, I’m Jeroen Bet</title>
		<link>http://feedproxy.google.com/~r/Dutchability/~3/dVCmUH5Vvhw/</link>
		<comments>http://www.dutchability.com/jeroenbet/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 03:18:50 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[About Me]]></category>
		<category><![CDATA[Hobe Sound]]></category>
		<category><![CDATA[Information Architect]]></category>
		<category><![CDATA[Jeroen Bet]]></category>
		<category><![CDATA[ripe ncc]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://www.dutchability.com/?p=1</guid>
		<description><![CDATA[Welcome to my new WordPress Website. I live in Houston, TX and work as an Information Architect at BrandExtract. A bit of history&#8230; Born in 1964 in the Netherlands, I started working in the Internet industry in 1998 after leaving my job at the biggest Telecommunications company in Amsterdam, the Netherlands. After a brief spell [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.dutchability.com/wp-content/uploads/2010/04/jeroen.jpg"><img class="alignright size-full wp-image-20 greyborder" title="Jeroen Bet" src="http://www.dutchability.com/wp-content/uploads/2010/04/jeroen.jpg" alt="Jeroen Bet - Information Architect, User Experience Designer" width="200" height="198" /></a>Welcome to my new WordPress Website.</p>
<p>I live in Houston, TX and work as an Information Architect at <a href="http://www.brandextract.com">BrandExtract</a>. </p>
<h2>A bit of history&#8230;</h2>
<p>Born in 1964 in the Netherlands, I started working in the Internet  industry in 1998 after leaving my job at the biggest  Telecommunications company in  Amsterdam, the Netherlands. After a brief spell with the largest  Internet hosting company in Holland, I worked as a  web content manager for the <a title="Click  here to visit the RIPE.NET website" href="http://www.ripe.net/">RIPE NCC</a>, a  not for  profit organisating serving Internet Service Professionals globally. As a  project  manager, I took the lead in re-designing  their existing website and incorporating many additional features.</p>
<p>In the period I worked for the RIPE NCC, I dealt with setting up the  website for the <a href="http://www.nro.net/">Numbers  Resource Organization</a> and setting up the members&#8217; only area of the  RIPE.NET website.</p>
<p>I also helped various other successful websites to emerge, providing  my expertise and talents. Additionally, I created   restricted websites for several conferences and helped setting up a  training tutorial website. I was also the managing  content editor for most of the websites mentioned above; making sure the  information on the websites was correct and  up-to-date.</p>
<p>After relocating to Hobe Sound, Florida, I started my own company,  working on various websites. in 1997, I  relocated to Seattle, Washington and started at Eben Design before moving to Houston where I now work as Master Information Architect at BrandExtract.</p>
<h2>My Background</h2>
<p>I have a background in journalism, public relations and education and  have attended courses in project management, writing,  XML, usability,  JavaScript  and  Microsoft Certified training.</p>
<p>Please read <a href="http://www.dutchability.com/?page_id=4">my  resume</a> for more about me.</p>
<p>For more information, <strong>please give me a call on (206) 617 0444  or send me  an <a title="Click here  to send me an e-mail" href="http://www.dutchability.com/contact/">e-mail</a></strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dutchability.com/jeroenbet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.dutchability.com/jeroenbet/</feedburner:origLink></item>
	</channel>
</rss>

