<?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>dsigned</title>
	<atom:link href="http://dsigned.gr/feed/rss2/" rel="self" type="application/rss+xml" />
	<link>http://dsigned.gr</link>
	<description>notes to self by a web developer</description>
	<lastBuildDate>Fri, 18 Jun 2010 00:01:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Facebook will bite you in the ass (if you are an online publisher)</title>
		<link>http://dsigned.gr/2010/06/17/facebook-will-bite-you-in-the-ass-if-you-are-an-online-publisher/</link>
		<comments>http://dsigned.gr/2010/06/17/facebook-will-bite-you-in-the-ass-if-you-are-an-online-publisher/#comments</comments>
		<pubDate>Thu, 17 Jun 2010 21:43:07 +0000</pubDate>
		<dc:creator>nk</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://dsigned.gr/?p=6</guid>
		<description><![CDATA[As you might have noticed lately Facebook began a huge effort to expand their reach outside Facebook with widgets like the share this button, the like this button etc. They also began a huge effort to convince on-line publishers that placing those widgets on their pages increases their reach and attract traffic. While it is [...]]]></description>
			<content:encoded><![CDATA[<p>As you might have noticed lately Facebook began a huge effort to expand their reach outside Facebook with widgets like the share this button, the like this button etc. They also began a huge effort to convince on-line publishers that placing those widgets on their pages increases their reach and attract traffic.</p>
<p>While it is true that Facebook is currently the 2nd traffic source behind search engines, statistics show that users coming from Facebook tend to have very low pageviews/visit* (consistently lower than the site average, in some cases as low as 2 p/v) compared to users coming from search engines (consistently higher than the site average). As it seems the use case is that someone posts a link on Facebook to an article, a friend of that user sees that link, visits the page (maybe even reads the article) and goes back to Facebook to comment,like or ignore the link and move on. It is therefore the case that Facebook traffic brings low quality, drive by, disloyal users which statistics show that it&#8217;s very unlikely that will stick around on the site or repeat the visit. Is this a sustainable source of traffic for on-line publishers ?</p>
<p>At a recent event here in Greece a Facebook representative made the case that by embracing Facebook and using Facebook&#8217;s marketing tools (Connect, like button, like box, Pages/Groups) brands can have more reach and better engagement with their users. He even gave a very impressive example in the case of the<a href="http://store.levi.com/" target="_blank"> Levi&#8217;s Friend Store </a>where the store shows you only what clothes your friends on Facebook &#8220;liked&#8221;. Impressive stuff which, for off-line brands, are extremely good tools to create an on-line presence and engage users in a more interactive environment than just a branded site. Adidas even goes as far to <a href="http://www.youtube.com/watch?v=8e0G2_elmmM#t=45s" target="_blank">display their Facebook page on tv ads</a> rather than their actual website or store. Where does online publishers fit in this scenario, though? As demonstrated earlier the usual case is that a user will click on a link on Facebook, visit the site to read/see the content, return to Facebook to comment.  Facebook gets the pageviews, the user generated content (comments) and the repeat visits every time someone interacts with that content/comment. The publisher will be happy if he even gets a 2nd pageview and he is the one that is burdened with the cost of producing the content in the first place. That&#8217;s a pretty bad deal.</p>
<p>To make matters even worse Facebook is also in the business of selling advertising space on their site, a traditional source of revenue of online publishers. If Facebook succeeds in building a momentum as an advertising platform, online publishers will see their customer&#8217;s (advertising agencies) budgets being diverted to a platform that they helped promote and is fueled by their content.</p>
<p>So why do publishers still use Facebook&#8217;s tools? It seems that there are numerous reasons. Partly because everyone is doing it, partly because they think that some more traffic never hurt anyone and partly because no one gave it any serious thought when the announcements were made  (the privacy debate helped divert the public focus elsewhere).</p>
<p>So the question remains, is there a way to leverage Facebook&#8217;s large user base without the drawbacks? I believe there is but that&#8217;s a whole new blog post.</p>
<p>*: Based on statistics from several sites with medium to large traffic and big Facebook presence (groups, pages, like buttons etc).</p>
]]></content:encoded>
			<wfw:commentRss>http://dsigned.gr/2010/06/17/facebook-will-bite-you-in-the-ass-if-you-are-an-online-publisher/feed/rss2/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why you should develop one and only one mockup</title>
		<link>http://dsigned.gr/2010/04/28/why-you-should-develop-one-and-only-one-mockup/</link>
		<comments>http://dsigned.gr/2010/04/28/why-you-should-develop-one-and-only-one-mockup/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 22:32:38 +0000</pubDate>
		<dc:creator>nk</dc:creator>
				<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://dsigned.gr/?p=4</guid>
		<description><![CDATA[1) Since design sits between art and engineering mock-ups should be backed by statistical analysis. If this is not the case it is not design, it&#8217;s painting. If you analyze your numbers correctly it is very rare that they justify or suggest a second design. 2) The devil is in the details. The amount of [...]]]></description>
			<content:encoded><![CDATA[<p>1) Since design sits between art and engineering mock-ups should be backed by statistical analysis. If this is not the case it is not design, it&#8217;s painting.<br />
If you analyze your numbers correctly it is very rare that they justify or suggest a second design.</p>
<p>2) The devil is in the details. The amount of detail that makes up a great design is huge.  Every single element must designed and placed in its optimal position with the right style while keeping the whole balanced and aesthetically pleasing.  Meanwhile it must be in line with business goals and be technically feasible.  The designer must walk the fine line of compromises that lead to a good design each time reasoning against competing constraints.  It is impossible to do this dance twice and still produce a different design (unless suffering from split personality disorders)</p>
<p>3) A good designer will always be opinionated.  He/she will have an idea on what the end result should be based on instinct, experience and eye for aesthetics. This is why he gets the big money after all.  Asking the same designer to make a second mock-up is like asking him to change his personality.</p>
<p>4) If the client really needs 2 mock-ups to decide then it&#8217;s fairly certain that the client does not know what he wants in the first place and any amount of mock-ups will not help. By sticking to one design and incrementally refining it will help both the designer and the client understand what needs to be done. It also helps keeping both parties focused instead of overloading them with too much choices and options. At the end of the day the client&#8217;s focus and feedback are important resources and it&#8217;s counterproductive to dilute them on multiple mock-ups.</p>
]]></content:encoded>
			<wfw:commentRss>http://dsigned.gr/2010/04/28/why-you-should-develop-one-and-only-one-mockup/feed/rss2/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hello world!</title>
		<link>http://dsigned.gr/2010/04/27/hello-world/</link>
		<comments>http://dsigned.gr/2010/04/27/hello-world/#comments</comments>
		<pubDate>Tue, 27 Apr 2010 22:11:08 +0000</pubDate>
		<dc:creator>nk</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://dsigned.gr/?p=1</guid>
		<description><![CDATA[package gr.dsigned; public class HelloWorld { public static void main(String[] args) { System.out.println("Hello, World"); } }]]></description>
			<content:encoded><![CDATA[<pre name="code" class="java">package gr.dsigned;
public class HelloWorld {
    public static void main(String[] args) {
        System.out.println("Hello, World");
    }
}
</pre>
]]></content:encoded>
			<wfw:commentRss>http://dsigned.gr/2010/04/27/hello-world/feed/rss2/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

