<?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>Comments on: Judgement Day for Snap Preview</title>
	<atom:link href="http://kanevski.org/2007/02/judgement-day-for-snap-preview/feed/" rel="self" type="application/rss+xml" />
	<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 02 Mar 2011 12:56:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: alisty</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-22275</link>
		<dc:creator>alisty</dc:creator>
		<pubDate>Sat, 24 May 2008 04:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-22275</guid>
		<description>snap has improved the preview service a lot by letting site owners to decide which link (blocks) they are willing to enable... i think the preview idea is not bad, if they can make it more informative and customizable.</description>
		<content:encoded><![CDATA[<p>snap has improved the preview service a lot by letting site owners to decide which link (blocks) they are willing to enable&#8230; i think the preview idea is not bad, if they can make it more informative and customizable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: subcorpus</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-912</link>
		<dc:creator>subcorpus</dc:creator>
		<pubDate>Wed, 02 May 2007 07:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-912</guid>
		<description>yes its good when it works fine ...
but on slow connection and pages ...
it actually becomes a disruption to the browsing experience ...
it hides what i am trying to read ...
may be it&#039;ll develop into something less intrusive ...
its kewl ...</description>
		<content:encoded><![CDATA[<p>yes its good when it works fine &#8230;<br />
but on slow connection and pages &#8230;<br />
it actually becomes a disruption to the browsing experience &#8230;<br />
it hides what i am trying to read &#8230;<br />
may be it&#8217;ll develop into something less intrusive &#8230;<br />
its kewl &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ephram Zerb &#187; Snap Preview Extreme Make-out</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-183</link>
		<dc:creator>Ephram Zerb &#187; Snap Preview Extreme Make-out</dc:creator>
		<pubDate>Thu, 15 Mar 2007 06:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-183</guid>
		<description>[...] About a month ago, Snap Preview was dodging a backlash to its suddenly-pervasive preview tool. Along with dozens of bloggers, I offered my assessment and promised to post a follow up with some solutions and approaches to using Snap Preview effectively. [...]</description>
		<content:encoded><![CDATA[<p>[...] About a month ago, Snap Preview was dodging a backlash to its suddenly-pervasive preview tool. Along with dozens of bloggers, I offered my assessment and promised to post a follow up with some solutions and approaches to using Snap Preview effectively. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Haarball</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-38</link>
		<dc:creator>Haarball</dc:creator>
		<pubDate>Fri, 23 Feb 2007 23:58:54 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-38</guid>
		<description>This is interesting, but as many of you have summarised, it is at times useless, maybe even obtrusive.

I see it as more of a niche product. I can only speak for myself, but I often browse around the web in search of design inspiration. I look for certain aspects of sites I like, certain types of layouts, etc. and in this respect I can see how Snap would be useful in speeding up my browsing. It can be useful in regular web browsing as well, but not more often than it would be obtrusive and slow the user down. 

I&#039;d say it&#039;s a feature that would have to be carefully considered *with each link* in relation to the nature of the given link and whether or not Snap would improve or worsen the usability -- a huge obstacle towards making it a successful feature.

Due to the inherent nature of web browsing, given the existence of the status bar and the fact that a visual overview of a site won&#039;t necessarily give the user any relevant information, I can hardly see this feature becoming widespread and widely successful among regular web users. UX might be better off focusing on people whose web experience is more likely to be enhanced by a visual overview - Web Designers, for example - and thus alter their goals as far as a user base goes. I don&#039;t know what they regard as their user base -- nevertheless meeting the needs of 80 percent seems over-ambitious at best.

Best of luck with the project, but I fear this is one feature that has lost before it&#039;s even started due to the very nature of browsing the web -- that is if the regular web user is considered as part of the demographic.</description>
		<content:encoded><![CDATA[<p>This is interesting, but as many of you have summarised, it is at times useless, maybe even obtrusive.</p>
<p>I see it as more of a niche product. I can only speak for myself, but I often browse around the web in search of design inspiration. I look for certain aspects of sites I like, certain types of layouts, etc. and in this respect I can see how Snap would be useful in speeding up my browsing. It can be useful in regular web browsing as well, but not more often than it would be obtrusive and slow the user down. </p>
<p>I&#8217;d say it&#8217;s a feature that would have to be carefully considered *with each link* in relation to the nature of the given link and whether or not Snap would improve or worsen the usability &#8212; a huge obstacle towards making it a successful feature.</p>
<p>Due to the inherent nature of web browsing, given the existence of the status bar and the fact that a visual overview of a site won&#8217;t necessarily give the user any relevant information, I can hardly see this feature becoming widespread and widely successful among regular web users. UX might be better off focusing on people whose web experience is more likely to be enhanced by a visual overview &#8211; Web Designers, for example &#8211; and thus alter their goals as far as a user base goes. I don&#8217;t know what they regard as their user base &#8212; nevertheless meeting the needs of 80 percent seems over-ambitious at best.</p>
<p>Best of luck with the project, but I fear this is one feature that has lost before it&#8217;s even started due to the very nature of browsing the web &#8212; that is if the regular web user is considered as part of the demographic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Nicol</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-23</link>
		<dc:creator>Jonathan Nicol</dc:creator>
		<pubDate>Mon, 05 Feb 2007 00:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-23</guid>
		<description>I admit that prior to reading this post I haven&#039;t given much thought to Snap Preview Anywhere, but when I had encountered SPA links in the past, my user experience was a negative one. Here is an attempt to qualify my negative reaction:

1. SPA previews look like a popup, which is intrinsically associated with advertising. The presence of a company logo on the &#039;popup&#039; did little to disillusion me of this notion.

2. I fail to see how a thumbnail representation of a website will help me make a decision whether to click a link. It might allow me to see the masthead of the site that the link points at (a site I may, or may not recognize by its logo), but it doesn&#039;t allow me to evaluate the content potential of the site. In many respects, the anchor text can perform this task more adequately. A link such as &quot;... recent [statistics show] that ...&quot; informs me perfectly adequately that I&#039;m about to see some statistics proving the author&#039;s point. I&#039;m not sure how a Snap preview adds value to the proposition. As Erik #1 has already mentioned, the humble status bar will allow me to ascertain the URL of the target website. Lets not forget the &#039;title&#039; attribute either, which allows the author to specify an unobtrusive hover that explains the link in more depth. For example: title=&quot;Read survey results on the National Statics Bureau website&quot; does a great job of telling me what will happen when I click a link, and where it will take me.

3. It is distracting to wait a second for a preview image to load, look at and absorb the image information. In other words, it slows me down.

4. Previews can be misleading. On the SPA website, there is an SPA enabled link to the SPA blog. In the preview I can make out the headline &quot;Snap Image Search Adds Filtering Options&quot;. Of course, when I navigate to the SPA blog that is not the current headline.</description>
		<content:encoded><![CDATA[<p>I admit that prior to reading this post I haven&#8217;t given much thought to Snap Preview Anywhere, but when I had encountered SPA links in the past, my user experience was a negative one. Here is an attempt to qualify my negative reaction:</p>
<p>1. SPA previews look like a popup, which is intrinsically associated with advertising. The presence of a company logo on the &#8216;popup&#8217; did little to disillusion me of this notion.</p>
<p>2. I fail to see how a thumbnail representation of a website will help me make a decision whether to click a link. It might allow me to see the masthead of the site that the link points at (a site I may, or may not recognize by its logo), but it doesn&#8217;t allow me to evaluate the content potential of the site. In many respects, the anchor text can perform this task more adequately. A link such as &#8220;&#8230; recent [statistics show] that &#8230;&#8221; informs me perfectly adequately that I&#8217;m about to see some statistics proving the author&#8217;s point. I&#8217;m not sure how a Snap preview adds value to the proposition. As Erik #1 has already mentioned, the humble status bar will allow me to ascertain the URL of the target website. Lets not forget the &#8216;title&#8217; attribute either, which allows the author to specify an unobtrusive hover that explains the link in more depth. For example: title=&#8221;Read survey results on the National Statics Bureau website&#8221; does a great job of telling me what will happen when I click a link, and where it will take me.</p>
<p>3. It is distracting to wait a second for a preview image to load, look at and absorb the image information. In other words, it slows me down.</p>
<p>4. Previews can be misleading. On the SPA website, there is an SPA enabled link to the SPA blog. In the preview I can make out the headline &#8220;Snap Image Search Adds Filtering Options&#8221;. Of course, when I navigate to the SPA blog that is not the current headline.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Wingren</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-21</link>
		<dc:creator>Erik Wingren</dc:creator>
		<pubDate>Sat, 03 Feb 2007 07:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-21</guid>
		<description>My name is Erik Wingren and I head up UX Research for Snap -- the company behind the Snap Preview Anywhere (SPA) service.

&lt;b&gt;@ Ephram:&lt;/b&gt; I am extremely impressed with your analysis of the user experience of our product. I can&#039;t go into details on everything we are doing but I wanted to share some of the near-term updates, aimed at solving some of the usability issues described here and elsewhere:

- This afternoon we released an update to the SPA code that disables the preview functionality while the mouse-wheel is in use. Since users hardly ever use the mouse to scroll and point at the same time this enhancement *should* eliminate a large number of the &quot;accidental triggering&quot; instances. Please let me know if this in fact solves the problem for you.

- We are exploring different solutions to the linked image problem you point out. This one is a little tricky — some users see this as a feature while others, like yourself, see it as broken functionality.

- We are currently in the final stages of testing a new control that will let the site owners manage readers&#039; expectations by visually denoting which links are SPA-enabled and which ones are not, and thereby in effect eliminate the &quot;surprise element&quot; of rolling over links on sites that uses SPA.

&lt;b&gt;@ Erik:&lt;/b&gt; I believe you represent the very definition of user that we are currently failing to serve.

I believe that unless we design the technology to meet the needs/wants of at least 80 percent of the user base we are not doing our job right. As of right now you are in the &quot;other&quot; percentile... and I would love to understand what it would take to get you over on our side ;)

If you have the time and energy, I would be very interested in what type of at-a-glance-information would help you navigate with greater speed and accuracy?

Again, to the both of you: Thank you for your articulate and insightful feedback. Your viewpoints are informing the ongoing development of this product. And I sincerely hope you will continue to share your thoughts as this product evolves.

P.S. 2 x Erik with a &quot;K&quot; on the same thread is a first for me! D.S.

Best Regards,
--
Erik Wingren
Snap UX Research
erik[@]snap[.]com</description>
		<content:encoded><![CDATA[<p>My name is Erik Wingren and I head up UX Research for Snap &#8212; the company behind the Snap Preview Anywhere (SPA) service.</p>
<p><b>@ Ephram:</b> I am extremely impressed with your analysis of the user experience of our product. I can&#8217;t go into details on everything we are doing but I wanted to share some of the near-term updates, aimed at solving some of the usability issues described here and elsewhere:</p>
<p>- This afternoon we released an update to the SPA code that disables the preview functionality while the mouse-wheel is in use. Since users hardly ever use the mouse to scroll and point at the same time this enhancement *should* eliminate a large number of the &#8220;accidental triggering&#8221; instances. Please let me know if this in fact solves the problem for you.</p>
<p>- We are exploring different solutions to the linked image problem you point out. This one is a little tricky — some users see this as a feature while others, like yourself, see it as broken functionality.</p>
<p>- We are currently in the final stages of testing a new control that will let the site owners manage readers&#8217; expectations by visually denoting which links are SPA-enabled and which ones are not, and thereby in effect eliminate the &#8220;surprise element&#8221; of rolling over links on sites that uses SPA.</p>
<p><b>@ Erik:</b> I believe you represent the very definition of user that we are currently failing to serve.</p>
<p>I believe that unless we design the technology to meet the needs/wants of at least 80 percent of the user base we are not doing our job right. As of right now you are in the &#8220;other&#8221; percentile&#8230; and I would love to understand what it would take to get you over on our side ;)</p>
<p>If you have the time and energy, I would be very interested in what type of at-a-glance-information would help you navigate with greater speed and accuracy?</p>
<p>Again, to the both of you: Thank you for your articulate and insightful feedback. Your viewpoints are informing the ongoing development of this product. And I sincerely hope you will continue to share your thoughts as this product evolves.</p>
<p>P.S. 2 x Erik with a &#8220;K&#8221; on the same thread is a first for me! D.S.</p>
<p>Best Regards,<br />
&#8211;<br />
Erik Wingren<br />
Snap UX Research<br />
erik[@]snap[.]com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-20</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Fri, 02 Feb 2007 00:07:51 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-20</guid>
		<description>For some reason the list item tags were stripped out of my previous comment, so please forgive the literal list enumeration below.  (You might want to change that behavior or at least warn users about it.)

A hyperlinked thumbnail is suitable for high-resolution photographs because:
1. a photograph is a static, well-defined entity
2. a scaled-down representation of a photograph provides an impression of the whole
3. it offers significant bandwidth savings

Web pages, on the other hand:
1. encapsulate dynamic content, feeds, hyperlinks, etc.
2. lose meaning when text is scaled down to the point of illegibility
3. are designed to load quickly

Unlike a photograph, the content of a web page is not easily summarized in image form.

It is the responsibility of the author to summarize it between the opening and closing of an anchor tag.  &lt;a href=&quot;http://www.google.com/technology/&quot; rel=&quot;nofollow&quot;&gt;Google&#039;s PageRank&lt;/a&gt; algorithm works as well as it does, in part, because authors tend to do this as well as they do.  When an anchor&#039;s reference is ambiguous, a user can hover over it and look in the status bar to see the referent.  Beyond that, the best way for a user to evaluate the quality of a link is to click on it.</description>
		<content:encoded><![CDATA[<p>For some reason the list item tags were stripped out of my previous comment, so please forgive the literal list enumeration below.  (You might want to change that behavior or at least warn users about it.)</p>
<p>A hyperlinked thumbnail is suitable for high-resolution photographs because:<br />
1. a photograph is a static, well-defined entity<br />
2. a scaled-down representation of a photograph provides an impression of the whole<br />
3. it offers significant bandwidth savings</p>
<p>Web pages, on the other hand:<br />
1. encapsulate dynamic content, feeds, hyperlinks, etc.<br />
2. lose meaning when text is scaled down to the point of illegibility<br />
3. are designed to load quickly</p>
<p>Unlike a photograph, the content of a web page is not easily summarized in image form.</p>
<p>It is the responsibility of the author to summarize it between the opening and closing of an anchor tag.  <a href="http://www.google.com/technology/" rel="nofollow">Google&#8217;s PageRank</a> algorithm works as well as it does, in part, because authors tend to do this as well as they do.  When an anchor&#8217;s reference is ambiguous, a user can hover over it and look in the status bar to see the referent.  Beyond that, the best way for a user to evaluate the quality of a link is to click on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ephram Zerb</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-19</link>
		<dc:creator>Ephram Zerb</dc:creator>
		<pubDate>Thu, 01 Feb 2007 21:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-19</guid>
		<description>@Erik. You&#039;re absolutely right, for most users, the status bar will help them answer questions like the wikipedia one more efficiently (it certainly does for me).  Knowing you personally, I know you&#039;re an engineer, and a URL communicates much more to you than it would for a typical website visitor.

As for checking if a destination website is a blog: this example was derived from a conversation I had with someone who cited this as the reason they like Snap Preview.

Admittedly, &quot;Is this the same website the author linked to earlier?&quot; is not a clear example.  What I was trying to illustrate is that a visitor&#039;s representation of a website in memory definitely includes visual information.  If I visit a website for the first time, I will more likely remember what it looks like before I remember what URL it was at.

Regardless, a successful use of Snap Preview would have to be a considerate improvement on what the status bar.  Thanks for your input.</description>
		<content:encoded><![CDATA[<p>@Erik. You&#8217;re absolutely right, for most users, the status bar will help them answer questions like the wikipedia one more efficiently (it certainly does for me).  Knowing you personally, I know you&#8217;re an engineer, and a URL communicates much more to you than it would for a typical website visitor.</p>
<p>As for checking if a destination website is a blog: this example was derived from a conversation I had with someone who cited this as the reason they like Snap Preview.</p>
<p>Admittedly, &#8220;Is this the same website the author linked to earlier?&#8221; is not a clear example.  What I was trying to illustrate is that a visitor&#8217;s representation of a website in memory definitely includes visual information.  If I visit a website for the first time, I will more likely remember what it looks like before I remember what URL it was at.</p>
<p>Regardless, a successful use of Snap Preview would have to be a considerate improvement on what the status bar.  Thanks for your input.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://kanevski.org/2007/02/judgement-day-for-snap-preview/comment-page-1/#comment-18</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Thu, 01 Feb 2007 20:34:30 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/02/judgement-day-for-snap-preview/#comment-18</guid>
		<description>&lt;blockquote&gt;
Overusing any tool without first addressing what problem it tries to solve will leave you with frustrating results.  The Preview has the capacity to provide extra information on a destination link that the user wouldn&#8217;t be privvy to unless they visited the website, such as:

Is the destination website a blog?
Does this link point to a wikipedia entry?
Is this the same website the author linked to earlier?

&lt;/blockquote&gt;

This information is unobtrusively visible to the user in the status bar.</description>
		<content:encoded><![CDATA[<blockquote><p>
Overusing any tool without first addressing what problem it tries to solve will leave you with frustrating results.  The Preview has the capacity to provide extra information on a destination link that the user wouldn&#8217;t be privvy to unless they visited the website, such as:</p>
<p>Is the destination website a blog?<br />
Does this link point to a wikipedia entry?<br />
Is this the same website the author linked to earlier?</p>
</blockquote>
<p>This information is unobtrusively visible to the user in the status bar.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

