<?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: Snapping at pop-ups 2.0</title>
	<atom:link href="http://www.mediainfluencer.net/2007/02/snapping-at-pop-ups-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mediainfluencer.net/2007/02/snapping-at-pop-ups-20/</link>
	<description>helping people break out of pigeonholes since 2003</description>
	<lastBuildDate>Wed, 08 Feb 2012 15:15:59 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Erik Wingren</title>
		<link>http://www.mediainfluencer.net/2007/02/snapping-at-pop-ups-20/comment-page-1/#comment-441</link>
		<dc:creator>Erik Wingren</dc:creator>
		<pubDate>Mon, 19 Feb 2007 23:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://mediainfluencer.bigblogcompany.net/wp/index.php/2007/02/snapping-at-pop-ups-20/#comment-441</guid>
		<description>&lt;b&gt;@ Perry,&lt;/b&gt;

I completely agree.

Snap Preview Anywhere is not a back-end tweak. If you install SPA you should announce the new functionality to your readers. The announcement should include instructions how your visitors can disable the functionality if they don’t want it:

1. Click &quot;Options&quot; in the upper right corner of any preview bubble.
2. Click Disable (for the site in question or globally)
3. Reload the page — Done!

And for those who want to take an even more cautious approach, as of Friday Feb 9th,  we offer an option that allow site owners to install SPA on their site but let the end-users enable the functionality themselves. &lt;a href=&quot;http://laughingsquid.com/&quot; rel=&quot;nofollow&quot;&gt;Laughing Squid&lt;/a&gt; is an example of a site that implements Snap Previews in this way (look for the badge in the right side bar).

Cheers.
--
Erik Wingren
Snap UX Research
</description>
		<content:encoded><![CDATA[<p><b>@ Perry,</b></p>
<p>I completely agree.</p>
<p>Snap Preview Anywhere is not a back-end tweak. If you install SPA you should announce the new functionality to your readers. The announcement should include instructions how your visitors can disable the functionality if they don’t want it:</p>
<p>1. Click &#8220;Options&#8221; in the upper right corner of any preview bubble.<br />
2. Click Disable (for the site in question or globally)<br />
3. Reload the page — Done!</p>
<p>And for those who want to take an even more cautious approach, as of Friday Feb 9th,  we offer an option that allow site owners to install SPA on their site but let the end-users enable the functionality themselves. <a href="http://laughingsquid.com/" rel="nofollow">Laughing Squid</a> is an example of a site that implements Snap Previews in this way (look for the badge in the right side bar).</p>
<p>Cheers.<br />
&#8211;<br />
Erik Wingren<br />
Snap UX Research</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Perry de Havilland</title>
		<link>http://www.mediainfluencer.net/2007/02/snapping-at-pop-ups-20/comment-page-1/#comment-440</link>
		<dc:creator>Perry de Havilland</dc:creator>
		<pubDate>Mon, 19 Feb 2007 19:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://mediainfluencer.bigblogcompany.net/wp/index.php/2007/02/snapping-at-pop-ups-20/#comment-440</guid>
		<description>But the trouble is Erik that whilst their might be some truth to what you say about inexperienced web users, it is equally important to not annoy the experienced viewer by inflicting unwanted things on them that can obscure what you are looking at or trying to click on.</description>
		<content:encoded><![CDATA[<p>But the trouble is Erik that whilst their might be some truth to what you say about inexperienced web users, it is equally important to not annoy the experienced viewer by inflicting unwanted things on them that can obscure what you are looking at or trying to click on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Wingren</title>
		<link>http://www.mediainfluencer.net/2007/02/snapping-at-pop-ups-20/comment-page-1/#comment-439</link>
		<dc:creator>Erik Wingren</dc:creator>
		<pubDate>Sun, 18 Feb 2007 22:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://mediainfluencer.bigblogcompany.net/wp/index.php/2007/02/snapping-at-pop-ups-20/#comment-439</guid>
		<description>&lt;b&gt;Adriana,&lt;/b&gt;

As a publisher you have a responsibility to your audience. If I was to attempt boiling down the science of audience research I would say this comes down to a combination of knowing who they are, what they want and what they need.

Ask yourself the following questions:
- Is your audience *exclusively* made up of experienced Internet users that read your blog using browsers that support tabbed browsing (essentially IE7, Firefox, Opera or Safari)?
- Are you *not* interested in attracting and retaining readers that doesn’t fit this narrow user profile? 
- Are your hyperlinks blue and underlined?
- Do you consistently follow &quot;proper&quot; markup protocol, defining the target and title of the link within the opening and closing of the anchor tag?

If so, your audience is likely to find the usefulness of SPA marginal. If so, your audience is trained to pick up on the subtle cues already provided by the browser framework — the browser status bar and anchor link title attribute provide these users with most of what they need to determine where links are pointing — and the cost of occasional erroneous clicks are often mitigated through the use of advanced browser functionality such as tabbed browsing...

However, if the user profile or markup principles described above are too narrow for your taste or ambition, I believe that by implementing Snap Preview Anywhere you would in fact offer ALL your readers MORE information to base their decision on which links to click or not to click, REDUCING the number of unwanted outbound clicks mid-read and, in effect, IMPROVE their ability to focus on YOUR content, or the content you link to that they TRULY wanted to visit.

I really appreciate the fact that you read up on the documentation and challenge the assumptions within. I hope the above will shed a little more light on the issues you raise. If not, I would be happy to continue the conversation here or &lt;a href=&quot;http://blog.snap.com/2007/02/09/spa-use-case/#continued-dialogue&quot; rel=&quot;nofollow&quot;&gt;there&lt;/a&gt;.

Cheers.
--
Erik Wingren
Snap UX Research</description>
		<content:encoded><![CDATA[<p><b>Adriana,</b></p>
<p>As a publisher you have a responsibility to your audience. If I was to attempt boiling down the science of audience research I would say this comes down to a combination of knowing who they are, what they want and what they need.</p>
<p>Ask yourself the following questions:<br />
- Is your audience *exclusively* made up of experienced Internet users that read your blog using browsers that support tabbed browsing (essentially IE7, Firefox, Opera or Safari)?<br />
- Are you *not* interested in attracting and retaining readers that doesn’t fit this narrow user profile?<br />
- Are your hyperlinks blue and underlined?<br />
- Do you consistently follow &#8220;proper&#8221; markup protocol, defining the target and title of the link within the opening and closing of the anchor tag?</p>
<p>If so, your audience is likely to find the usefulness of SPA marginal. If so, your audience is trained to pick up on the subtle cues already provided by the browser framework — the browser status bar and anchor link title attribute provide these users with most of what they need to determine where links are pointing — and the cost of occasional erroneous clicks are often mitigated through the use of advanced browser functionality such as tabbed browsing&#8230;</p>
<p>However, if the user profile or markup principles described above are too narrow for your taste or ambition, I believe that by implementing Snap Preview Anywhere you would in fact offer ALL your readers MORE information to base their decision on which links to click or not to click, REDUCING the number of unwanted outbound clicks mid-read and, in effect, IMPROVE their ability to focus on YOUR content, or the content you link to that they TRULY wanted to visit.</p>
<p>I really appreciate the fact that you read up on the documentation and challenge the assumptions within. I hope the above will shed a little more light on the issues you raise. If not, I would be happy to continue the conversation here or <a href="http://blog.snap.com/2007/02/09/spa-use-case/#continued-dialogue" rel="nofollow">there</a>.</p>
<p>Cheers.<br />
&#8211;<br />
Erik Wingren<br />
Snap UX Research</p>
]]></content:encoded>
	</item>
</channel>
</rss>

