<?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>Designed for Satisfaction &#187; Human/Computer Interaction</title>
	<atom:link href="http://guywyant.info/log/category/compute/hci/feed/" rel="self" type="application/rss+xml" />
	<link>http://guywyant.info/log</link>
	<description>and how</description>
	<lastBuildDate>Thu, 29 Sep 2011 17:27:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Flattened Email</title>
		<link>http://guywyant.info/log/191/flattened-email/</link>
		<comments>http://guywyant.info/log/191/flattened-email/#comments</comments>
		<pubDate>Thu, 21 Jul 2011 02:33:29 +0000</pubDate>
		<dc:creator>Guy</dc:creator>
				<category><![CDATA[Compute]]></category>
		<category><![CDATA[Human/Computer Interaction]]></category>

		<guid isPermaLink="false">http://guywyant.info/log/191/flattened-email/</guid>
		<description><![CDATA[Recently I’ve been thinking of services like Google+ and Chatter as flattened email. A post on one of those networks is quite similar to an email that you send-to-all, and to replicate email in Google+, you can simply make a &#8230; <a href="http://guywyant.info/log/191/flattened-email/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Recently I’ve been thinking of services like Google+ and Chatter as flattened email. A post on one of those networks is quite similar to an email that you send-to-all, and to replicate email in Google+, you can simply make a post private between you and another person. The differences, then, lie in your interface to the conversation. This interface has profound effects – just think if you had to click the subject of every post on Google+ to open it for reading, then click back out of that post to see the stream again. Would that change how you used it?<img style="display: block; float: none; margin-left: auto; margin-right: auto;" title="" src="http://guywyant.info/log/wp-content/uploads/2011/07/email-vs-google1.png" alt="Email is peaked, Google+ is flattened" width="371" height="260" /><em style="width: 370px; display: block; margin: 0 auto;"><span style="font-size: x-small;">Email shows you the tip of each iceberg, whereas Google+ flattens them out and shows you the whole chunk at once.</span></em></p>
<p>We could say that Google+ and email are merely different interfaces to the same core features. Email is an efficient way to get an overview of all of your active or recent conversations, since it hides most of the content. Google+, on the other hand, splays it all out in front of you, which makes access to threads from further in the past more difficult, but makes interacting with recent content much easier.</p>
<p>Flattened-email products, which seem to be on the rise, tend to focus on the <em>now</em>,<em> </em>and less so on the ease of finding a conversation from the past, or storing it for reference. These problems will need to be dealt with quickly, or flattened-email will end up having usability problems that are different than, but equally maddening as, those that email has today.</p>
]]></content:encoded>
			<wfw:commentRss>http://guywyant.info/log/191/flattened-email/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Thoughts on Google Plus &#8745; UX Design</title>
		<link>http://guywyant.info/log/179/thoughts-on-google-plus-ux-design/</link>
		<comments>http://guywyant.info/log/179/thoughts-on-google-plus-ux-design/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 03:25:00 +0000</pubDate>
		<dc:creator>Guy</dc:creator>
				<category><![CDATA[Compute]]></category>
		<category><![CDATA[Human/Computer Interaction]]></category>

		<guid isPermaLink="false">http://guywyant.info/log/179/thoughts-on-google-plus-ux-design/</guid>
		<description><![CDATA[The enthusiast quickly discovers that new social networks like Google Plus are not interesting for their explicit, outlineable featuresets, but rather the subtle, practically indescribable usage-guidance that each included element of design provides to the user. These affordances not only &#8230; <a href="http://guywyant.info/log/179/thoughts-on-google-plus-ux-design/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The enthusiast quickly discovers that new social networks like Google Plus are not interesting for their explicit, outlineable featuresets, but rather the subtle, practically indescribable usage-guidance that each included element of design provides to the user.</p>
<p>These affordances not only enable or discourage communication in each area of the site, they also help shape the more “fluffy bits” of writing, from the length of content to its mood – how playfully, introspectively, or authoritatively one speaks. </p>
<p>And these subtle affordances are what takes longer to grok. This explains why it takes a mere five minutes to use every feature of Google Plus, while the great technologists of our day have spent days “playing around” within the network – and we must use a kiddish phrase, because we don&#8217;t have the words to describe the type of familiarity we gain from sustained usage of a website, rather than quick perusal.</p>
<p>And so, welcome to the world of interaction design. One wonders why those roles are <a href="http://uxmag.com/technology/hi-im-a-ux-developer-youre-a-what">so hard to describe</a> comprehensively – it’s because their raw materials are, instead of concrete and steel, hints and hooks into the subconscious.</p>
<p>Sure, to many, the only apparent business of the UX professional is in building bridges out of pixels. But their real challenge is building those bridges in such a way that the people driving can’t help but to buckle their seatbelt, or tune in to FM 90.1, or start craving ice cream.</p>
]]></content:encoded>
			<wfw:commentRss>http://guywyant.info/log/179/thoughts-on-google-plus-ux-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Most Ambiguous Button Award</title>
		<link>http://guywyant.info/log/126/most-ambiguous-button-award/</link>
		<comments>http://guywyant.info/log/126/most-ambiguous-button-award/#comments</comments>
		<pubDate>Wed, 10 Feb 2010 23:55:31 +0000</pubDate>
		<dc:creator>Guy</dc:creator>
				<category><![CDATA[Aside]]></category>
		<category><![CDATA[Compute]]></category>
		<category><![CDATA[Human/Computer Interaction]]></category>

		<guid isPermaLink="false">http://guywyant.info/log/?p=126</guid>
		<description><![CDATA[The Akismet plugin for WordPress wins today&#8217;s Most Ambiguous Button award. After subconsciously struggling with the meaning of the &#8220;Update options »&#8221; button, I realized why I was having such trouble: &#8220;update&#8221; could be either a noun or a verb, and &#8230; <a href="http://guywyant.info/log/126/most-ambiguous-button-award/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The Akismet plugin for WordPress wins today&#8217;s Most Ambiguous Button award. After subconsciously struggling with the meaning of the &#8220;Update options »&#8221; button, I realized why I was having such trouble: &#8220;update&#8221; could be either a noun or a verb, and both words can mean a variety of things in different user interfaces. Moral:  always choose a label for a button that makes its meaning intuitive, or familiar to users, rather than labeling it according to what it does on the back end. &#8220;Save changes&#8221; would be a good choice here.</p>
]]></content:encoded>
			<wfw:commentRss>http://guywyant.info/log/126/most-ambiguous-button-award/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>On Google Wave&#8217;s UI: Where to Put the Blip-contributors</title>
		<link>http://guywyant.info/log/107/on-google-waves-ui-where-to-put-the-blip-creator/</link>
		<comments>http://guywyant.info/log/107/on-google-waves-ui-where-to-put-the-blip-creator/#comments</comments>
		<pubDate>Mon, 01 Feb 2010 02:27:46 +0000</pubDate>
		<dc:creator>Guy</dc:creator>
				<category><![CDATA[Compute]]></category>
		<category><![CDATA[Google Wave]]></category>
		<category><![CDATA[Human/Computer Interaction]]></category>

		<guid isPermaLink="false">http://guywyant.info/log/107/on-google-waves-ui-where-to-put-the-blip-creator/</guid>
		<description><![CDATA[In most of the Google Wave waves I use, it would make more sense to have the blip-creator thumbnail and name changed to be right-aligned, basically what I’ve mocked up below. This style is less disruptive to the overall document’s &#8230; <a href="http://guywyant.info/log/107/on-google-waves-ui-where-to-put-the-blip-creator/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>In most of the Google Wave waves I use, it would make more sense to have the blip-creator thumbnail and name changed to be right-aligned, basically what I’ve mocked up below.</p>
<p><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="" border="0" alt="" src="http://guywyant.info/log/wp-content/uploads/2010/01/Capture.png" width="538" height="534" /> </p>
</p>
<p>This style is less disruptive to the overall document’s formatting, and makes the wave look much more cohesive and professional. For chat-style exchanges, it’s important to keep what is said closely linked to who’s saying it, but when collaboratively editing, it’s rather unnecessary, and turns out to be more distracting than anything else.</p>
<p>[Continued 10 minutes after realizing this would actually be doable with Stylish]</p>
<p>Here I present to you, the smallest style with the largest impact for Google Wave: Now all of my waves look like this (except they’re not in Russian).</p>
<p><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="1" border="0" alt="1" src="http://guywyant.info/log/wp-content/uploads/2010/02/1.jpg" width="538" height="477" /> </p>
</p>
<p>The names of the blip’s contributors are hidden, as well as the time/date (I don’t need either one near enough to justify how much they mess up the formatting of blips). The drop-down menu is made smaller but still displayed. The good part for you is that each part is incredibly easy to hide or show; the CSS is below, and if you want to hide or show the time, names, or menu, just add or delete the appropriate item from the list! </p>
<p>Want it quick? Firefox users,&#160; <a href="http://userstyles.org/styles/24776">install it from here</a> as a Stylish style or a Greasemonkey script. I also threw together a simple <a href="https://chrome.google.com/extensions/detail/epdjafiljkbgphifdghjennmeadnjnel/">Chrome extension</a>.</p>
<div style="border-bottom: silver 1px solid; text-align: left; border-left: silver 1px solid; padding-bottom: 4px; line-height: 12pt; background-color: #f4f4f4; margin: 20px 0px 10px; padding-left: 4px; width: 97.5%; padding-right: 4px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; max-height: 200px; font-size: 8pt; overflow: auto; border-top: silver 1px solid; cursor: text; border-right: silver 1px solid; padding-top: 4px" id="codeSnippetWrapper">
<div style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: #f4f4f4; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px" id="codeSnippet">
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: white; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px"><span style="color: #cc6633">.GTB</span>[dc=contributors] {</pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: #f4f4f4; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">    <span style="color: #0000ff">float</span>: <span style="color: #0000ff">right</span> <span style="color: #006080">!important;</span></pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: white; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">    <span style="color: #0000ff">margin</span>-<span style="color: #0000ff">right</span>: 0 <span style="color: #006080">!important;</span></pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: #f4f4f4; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">    <span style="color: #0000ff">margin</span>-<span style="color: #0000ff">left</span>: 2px <span style="color: #006080">!important;</span></pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: white; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">}</pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: #f4f4f4; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">[dc=<span style="color: #0000ff">menu</span>] {</pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: white; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">    <span style="color: #0000ff">width</span>: 9px <span style="color: #006080">!important;</span></pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: #f4f4f4; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">}</pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: white; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px"><span style="color: #cc6633">.MTB</span>[dc=time], <span style="color: #cc6633">.KTB</span>[dc=names] {</pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: #f4f4f4; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">    <span style="color: #0000ff">display</span>: none <span style="color: #006080">!important;</span></pre>
<p><!--CRLF--></p>
<pre style="border-bottom-style: none; text-align: left; padding-bottom: 0px; line-height: 12pt; border-right-style: none; background-color: white; margin: 0em; padding-left: 0px; width: 100%; padding-right: 0px; font-family: &#39;Courier New&#39;, courier, monospace; direction: ltr; border-top-style: none; color: black; font-size: 8pt; border-left-style: none; overflow: visible; padding-top: 0px">}</pre>
<p><!--CRLF--></div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://guywyant.info/log/107/on-google-waves-ui-where-to-put-the-blip-creator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chapple and Operational Transformation</title>
		<link>http://guywyant.info/log/46/chapple-and-operational-transformation/</link>
		<comments>http://guywyant.info/log/46/chapple-and-operational-transformation/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 23:22:55 +0000</pubDate>
		<dc:creator>Guy</dc:creator>
				<category><![CDATA[Aside]]></category>
		<category><![CDATA[Compute]]></category>
		<category><![CDATA[Human/Computer Interaction]]></category>

		<guid isPermaLink="false">http://guywyant.info/log/?p=46</guid>
		<description><![CDATA[I&#8217;d love to experiment with adding a simple form of operational transformation to my HCI chat app project, Chapple, but sadly I&#8217;m out of time. Operational transformation in Google Wave, as an example, is what prevents the simultaneous edits of &#8230; <a href="http://guywyant.info/log/46/chapple-and-operational-transformation/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;d love to experiment with adding a simple form of <a href="http://en.wikipedia.org/wiki/Operational_transformation">operational transformation</a> to my HCI chat app project, Chapple, but sadly I&#8217;m out of time. Operational transformation in Google Wave, as an example, is what prevents the simultaneous edits of multiple people from being put in all the wrong places within the wave. Chapple is still pretty jazzy; perhaps adding OT is a project for the future.</p>
]]></content:encoded>
			<wfw:commentRss>http://guywyant.info/log/46/chapple-and-operational-transformation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using CSS to Fix WebAdvisor&#8217;s UI Mistakes</title>
		<link>http://guywyant.info/log/31/using-css-to-fix-webadvisors-ui-mistakes/</link>
		<comments>http://guywyant.info/log/31/using-css-to-fix-webadvisors-ui-mistakes/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 05:09:57 +0000</pubDate>
		<dc:creator>Guy</dc:creator>
				<category><![CDATA[Compute]]></category>
		<category><![CDATA[Human/Computer Interaction]]></category>

		<guid isPermaLink="false">http://guywyant.info/log/?p=31</guid>
		<description><![CDATA[The University of Evansville recently moved to using Datatel&#8217;s WebAdvisor for student and faculty accounts management. The migration of data and the training process apparently took all of 18 months, so when we were finally given access to the WebAdvisor &#8230; <a href="http://guywyant.info/log/31/using-css-to-fix-webadvisors-ui-mistakes/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The University of Evansville recently moved to using <a href="http://www.datatel.com/products/products_a-z/webadvisor.cfm">Datatel&#8217;s WebAdvisor</a> for student and faculty accounts management. The migration of data and the training process apparently took all of 18 months, so when we were finally given access to the WebAdvisor system, my hopes were probably&#8230; a bit too high.</p>
<p>While the abilities that the Datatel system provides are probably a refreshing change for the administrators of UE, the company seems oblivious to the fact that websites should be designed by people who have, well, at least rudimentary knowledge of user interaction guidelines. And interaction aside, it seems that Datatel never found it necessary to hire a single person able to design an eye-pleasing layout (individual color schemes for WebAdvisors vary from school to school, so at least I can&#8217;t fault them entirely for the color).</p>
<p>It&#8217;s not just me that&#8217;s amazed at this lack of effort in user interaction. I&#8217;ve discussed it with several other students and faculty members, all of whom expressed feelings rather far from adoration over the user interface.</p>
<h2>Fixing Their Mistakes</h2>
<p>Over the past week or so I&#8217;ve cobbled together some custom CSS in an attempt to rectify a few of the design faux pas exhibited so prevalently in WebAdvisor. By installing the style using the Firefox plugins Stylish or Greasemonkey, <em>you too</em> can get a slightly more attractive WebAdvisor!</p>
<p>So far, the rudimentary changes have been as follows:</p>
<ul>
<li>Navigation bar alterations:
<ul>
<li>Links behave like links (added mouseovers)</li>
<li>Took away horrendous small-caps and boldness</li>
</ul>
</li>
<li>Made the content fixed width (things on the far edges of the page were just too far apart)</li>
<li>On pages with tables:
<ul>
<li>Made even-odd row highlighting less distracting: lowered contrast</li>
<li>Removed cell borders (may add back in less distracting form)</li>
</ul>
</li>
<li>Reset the bottom-of-page buttons on each page to the default style, rather than the strange beveled and all-caps style</li>
<li>Made student-menu homepage section headings more readable</li>
</ul>
<p>The perplexing parts about this are (a) I&#8217;ve not spent much time on it, especially with how easy it is to do on-the-fly CSS edits with <a href="http://getfirebug.com">Firebug</a>, and (b) I&#8217;ve had to edit <em>only</em> the CSS to get such an improvement in overall usability (and especially readability).  This means that Datatel could hire a freelance webdesigner and fix half of their interface problems right away, for the dozens of universities using the WebAdvisor system! The user interaction failures, however, are another story entirely.</p>
<p><strong>Want to see WebAdvisor prettier than it was before?</strong> You can install my stylesheet with either Stylish or Greasemonkey at <a href="http://userstyles.org">userstyles.org</a> listed under <a href="http://userstyles.org/styles/21681">WebAdvisor: Stop the Epic Fail</a>.  WebAdvisor is customized for each university to a certain degree, and this style applies vaguely UE-themed colors to some elements, so please go right now and tweak it for your own system &#8212; it should be easy!</p>
]]></content:encoded>
			<wfw:commentRss>http://guywyant.info/log/31/using-css-to-fix-webadvisors-ui-mistakes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UI Responsiveness in Google Wave</title>
		<link>http://guywyant.info/log/21/ui-responsiveness-in-wave/</link>
		<comments>http://guywyant.info/log/21/ui-responsiveness-in-wave/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 00:32:20 +0000</pubDate>
		<dc:creator>Guy</dc:creator>
				<category><![CDATA[Aside]]></category>
		<category><![CDATA[Compute]]></category>
		<category><![CDATA[Google Wave]]></category>
		<category><![CDATA[Human/Computer Interaction]]></category>

		<guid isPermaLink="false">http://guywyant.info/log/?p=21</guid>
		<description><![CDATA[Responsiveness is an absolute must in any UI, and it&#8217;s one must that the Google Wave client won&#8217;t have, until they implement better lazy loading practices.  When marking something as read/unread (amongst other actions in your inbox), there is a &#8230; <a href="http://guywyant.info/log/21/ui-responsiveness-in-wave/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Responsiveness is an absolute must in any UI, and it&#8217;s one must that the Google Wave client won&#8217;t have, until they implement better lazy loading practices.  When marking something as read/unread (amongst other actions in your inbox), there is a tangible pause until the wave you&#8217;ve selected is loaded, before the action happens.</p>
]]></content:encoded>
			<wfw:commentRss>http://guywyant.info/log/21/ui-responsiveness-in-wave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

