<?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>Reacties op: UI for the People</title>
	<atom:link href="http://jdevelopment.nl/java/ui-for-the-people/feed/" rel="self" type="application/rss+xml" />
	<link>http://jdevelopment.nl/java/ui-for-the-people/</link>
	<description>designing a new generation of software</description>
	<lastBuildDate>Mon, 02 Aug 2010 11:00:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>Door: BlackWasp</title>
		<link>http://jdevelopment.nl/java/ui-for-the-people/comment-page-1/#comment-362</link>
		<dc:creator>BlackWasp</dc:creator>
		<pubDate>Sat, 05 Apr 2008 22:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://jdevelopment.nl/java/ui-for-the-people/#comment-362</guid>
		<description>Nice article.  I also remember the days when we just copied forms.  Of course, Microsoft are helping to maintain, though improve, that path with InfoPath solutions.

Interesting point on making the UI guide the user and provide documentation.  I am not sure how useful this would be for the 95% of users who will not read this kind of information unless they are really stuck.  I prefer the idea of making the user interface as simple and obvious as possible.  I like the mantra of &quot;If in doubt, think Apple design.&quot;

The other issue that I run into often is the user-controlled UI design problem.  This is where you know that the usability will suffer but the customer still insists that their snazzy new Windows-based UI with icons and menus should run exactly like the old Alpha green-screen because the users won&#039;t have to get used to it.

Hey ho, what can you do, eh?</description>
		<content:encoded><![CDATA[<p>Nice article.  I also remember the days when we just copied forms.  Of course, Microsoft are helping to maintain, though improve, that path with InfoPath solutions.</p>
<p>Interesting point on making the UI guide the user and provide documentation.  I am not sure how useful this would be for the 95% of users who will not read this kind of information unless they are really stuck.  I prefer the idea of making the user interface as simple and obvious as possible.  I like the mantra of &#8220;If in doubt, think Apple design.&#8221;</p>
<p>The other issue that I run into often is the user-controlled UI design problem.  This is where you know that the usability will suffer but the customer still insists that their snazzy new Windows-based UI with icons and menus should run exactly like the old Alpha green-screen because the users won&#8217;t have to get used to it.</p>
<p>Hey ho, what can you do, eh?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
