<?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>Yan Pritzker &#187; usability</title>
	<atom:link href="http://yanpritzker.com/category/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://yanpritzker.com</link>
	<description>photographer, entrepreneur, software engineer, musician, skier</description>
	<lastBuildDate>Sat, 21 Jan 2012 01:18:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<atom:link rel="next" href="http://yanpritzker.com/category/usability/feed/?page=2" />

		<item>
		<title>How Facebook can dramatically improve Pages</title>
		<link>http://yanpritzker.com/2009/06/18/how-facebook-can-dramatically-improve-pages/</link>
		<comments>http://yanpritzker.com/2009/06/18/how-facebook-can-dramatically-improve-pages/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 15:16:57 +0000</pubDate>
		<dc:creator>yan</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[facebook]]></category>

		<guid isPermaLink="false">http://skwpspace.com/2009/06/18/how-facebook-can-dramatically-improve-pages/</guid>
		<description><![CDATA[Despite all the bitching and moaning, I think the recent facebook redesign is great. Focusing on the stream, and the ease of sharing a variety of content works very well. But Facebook Pages feel like an afterthought that was tacked on, hacked on, and clearly never thought through. And now, let the Airing of Grievances [...]]]></description>
			<content:encoded><![CDATA[<p>Despite all the bitching and moaning, I think the recent facebook redesign is great. Focusing on the stream, and the ease of sharing a variety of content works very well. But Facebook Pages feel like an afterthought that was tacked on, hacked on, and clearly never thought through. And now, let the Airing of Grievances begin.</p>
<ol>
<li>Music pages need a prominent and centered Music Player. For all the fail of Myspace the one thing they got right is that a band&#8217;s page is about its music. The first thing front and center needs to be a Music Player. Instead we get a half-assed music player option which either has to sit quietly in the bottom left hand corner below the fold, or on the Boxes page (if you make Boxes page the default), but then your page looks fairly stupid, because the rest of the good content (Wall) is elsewhere. So &#8211; a very quick and dramatic improvement would be to place the Music Player box right at the top of the Wall tab, so that visitors can hear the music and read the news and talk with the band at the same time.</li>
<li>A Page&#8217;s administrators need a way to get a solid news stream from the page including all comments, likes, and etc. Without this feature it is difficult to communicate with fans. I run a <a href="http://facebook.com/pages/Yan-Pritzker-Photography/104996292362">page for my photography</a> on facebook, but I find there is no good way to get all the comments. Instead I have to notice that someone commented, then find the photoset and look at the photoset&#8217;s comments to find the actual comment. There is no good way to know that someone&#8217;s written on the page&#8217;s wall either, unless you have the wall display in Page + Fans mode, and physically check back. A page can only be an effective tool if it enables the administrators to communicate with the people, but without a feed it&#8217;s nearly useless.</li>
<li>RSS. Come on facebook, it&#8217;s 2009! What is the excuse for not having an RSS feed for the page? What&#8217;s more, several places on the site have very carefully hidden RSS links (such as Notes), but they don&#8217;t even bother putting in the proper HTML LINK element to get it to show up in the browser&#8217;s url bar. Get with the program, please.</li>
</ol>
<p>I don&#8217;t doubt that facebook&#8217;s engineers are busy cooking up the next redesign and improvement, but I think that if facebook wants Pages to be a successful tool for businesses, bands, and other commercial-ish entities that are starting to make facebook their home, then that area should be their next target for a redesign and rethink.</p>
]]></content:encoded>
			<wfw:commentRss>http://yanpritzker.com/2009/06/18/how-facebook-can-dramatically-improve-pages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Safari 4&#8242;s new tab layout is detrimental to usability</title>
		<link>http://yanpritzker.com/2009/02/25/why-safari-4s-new-tab-layout-is-detrimental-to-usability/</link>
		<comments>http://yanpritzker.com/2009/02/25/why-safari-4s-new-tab-layout-is-detrimental-to-usability/#comments</comments>
		<pubDate>Wed, 25 Feb 2009 05:20:51 +0000</pubDate>
		<dc:creator>yan</dc:creator>
				<category><![CDATA[usability]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[desgin]]></category>

		<guid isPermaLink="false">http://skwpspace.com/2009/02/25/why-safari-4s-new-tab-layout-is-detrimental-to-usability/</guid>
		<description><![CDATA[While there were many good improvements made to Safari 4 beta, I hope that Apple considers bringing the tabs back to their rightful place, or at least offering an option for classic tab view. Here are the reasons I believe the new tab layout is actually detrimental to usability. Fitts&#8217;s law. When I click to [...]]]></description>
			<content:encoded><![CDATA[<p>While there were many good improvements made to Safari 4 beta, I hope that Apple considers bringing the tabs back to their rightful place, or at least offering an option for classic tab view. Here are the reasons I believe the new tab layout is actually detrimental to usability.</p>
<ol>
<li>Fitts&#8217;s law. When I click to open a new tab, I previously had immediate visual feedback that this had occurred. Now I have to look past two additional rows of screen real estate (the shortcut bar, and the url bar) to spot the change. I have already had a few times where I command-clicked a link to open in a tab and had a bit of trouble spotting that the tab had actually opened. Not only does it affect the distance my gaze has to travel, but also my mouse, when going from page content to clicking between tabs I now have to pass two additional rows.</li>
<li>Inconsistency. Up to the release of Safari 4, all Mac applications had a uniform title bar. The top line of the window was reserved as a place to display the window title. Now the top line is taken up by tabs, making this application behave differently than every other. Not only is this visually inconsistent, but if you click the corner of a tab you can end up dragging the tab instead of the window. You can also (with admittedly small probability) land on the close tab icon when trying to drag the window, which will not enable you to drag at all. While both of these events have small target areas, and thus low probability of being hit, the fact that it&#8217;s possible makes it a worse choice for usability.</li>
</ol>
<p>Why did they do it? I am guessing that eliminating the standard title bar and using that real estate for tabs enables us to gain about 25 pixels more vertical space for actual page content. But I don&#8217;t think 25 pixels of content is a fair tradeoff for the usability problems introduced by the change.</p>
<p><b>Update:</b> Restore your sanity:</p>
<pre style='font-size:10px'>
defaults write com.apple.Safari DebugSafari4TabBarIsOnTop -bool NO
</pre>
]]></content:encoded>
			<wfw:commentRss>http://yanpritzker.com/2009/02/25/why-safari-4s-new-tab-layout-is-detrimental-to-usability/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Rails moves to Lighthouse</title>
		<link>http://yanpritzker.com/2008/04/16/rails-moves-to-lighthouse/</link>
		<comments>http://yanpritzker.com/2008/04/16/rails-moves-to-lighthouse/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 16:39:26 +0000</pubDate>
		<dc:creator>yan</dc:creator>
				<category><![CDATA[bugtracking]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[thoughts]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://skwpspace.com/2008/04/16/rails-moves-to-lighthouse/</guid>
		<description><![CDATA[In a series of dev infrastructure changes, the Rails team is moving to Lighthouse as its bugtracking system. I wrote about Lighthouse more than a year ago as an application to watch in the bugtracking space, and now they&#8217;re coming into the limelight with official support from the Rails team. I&#8217;m really happy to see [...]]]></description>
			<content:encoded><![CDATA[<p>In a series of dev infrastructure changes, the <a href="http://weblog.rubyonrails.com/2008/4/15/rails-and-family-on-lighthouse">Rails team is moving to Lighthouse as its bugtracking system.</a> I <a href="http://skwpspace.com/2007/04/02/ui-matters/">wrote about Lighthouse</a> more than a year ago as an application to watch in the bugtracking space, and now they&#8217;re coming into the limelight with official support from the Rails team. </p>
<p>I&#8217;m really happy to see that the Rails team and 37 Signals are making this move because it will force Lighthouse to become an even better application as it meets demands of many projects that are sure to follow Rails. </p>
<p>Too many teams put up with products that have terrible usability like Bugzilla because many programmers tend not to think about usability as an important factor. We are used to command line interfaces and white text on black backgrounds. But believe it or not, using something like <a href="http://lighthouseapp.com/">Lighthouse</a> over say, Bugzilla, boosts your productivity because it is well designed and lets you get to the information you need more quickly and with less frustration. That said, <a href="http://trac.edgewall.org/">Trac</a> is still many levels above Bugzilla in usability and design so if you&#8217;re using an in-house product, I don&#8217;t know of many better ones.</p>
]]></content:encoded>
			<wfw:commentRss>http://yanpritzker.com/2008/04/16/rails-moves-to-lighthouse/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

