<?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: Typekit</title>
	<atom:link href="http://iloveusability.com/usability-review/typekit/feed/" rel="self" type="application/rss+xml" />
	<link>http://iloveusability.com/usability-review/typekit/</link>
	<description>Reviews &#38; articles about rock-solid usability and stunning user experiences.</description>
	<lastBuildDate>Wed, 14 Jul 2010 21:31:54 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike</title>
		<link>http://iloveusability.com/usability-review/typekit/#comment-563</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 14 Jul 2010 21:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://iloveusability.com/?p=204#comment-563</guid>
		<description>Too bad TypeKit delivered fonts on Windows look like a toothless dog chewed them up. Also too bad that the CSS file Typekit serves you is larger than the font files themselves. I got really excited at how a test site looked on my Mac, but when I checked it on Windows I sent Typekit an email for my money back.</description>
		<content:encoded><![CDATA[<p>Too bad TypeKit delivered fonts on Windows look like a toothless dog chewed them up. Also too bad that the CSS file Typekit serves you is larger than the font files themselves. I got really excited at how a test site looked on my Mac, but when I checked it on Windows I sent Typekit an email for my money back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Bolt</title>
		<link>http://iloveusability.com/usability-review/typekit/#comment-108</link>
		<dc:creator>Nate Bolt</dc:creator>
		<pubDate>Sun, 15 Nov 2009 01:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://iloveusability.com/?p=204#comment-108</guid>
		<description>Kevin - Awesome thorough review, and love the embedded vimeo clip to illustrate a simple UX issue. I found this searching around for help getting the CSS classes working.</description>
		<content:encoded><![CDATA[<p>Kevin &#8211; Awesome thorough review, and love the embedded vimeo clip to illustrate a simple UX issue. I found this searching around for help getting the CSS classes working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://iloveusability.com/usability-review/typekit/#comment-27</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Wed, 30 Sep 2009 01:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://iloveusability.com/?p=204#comment-27</guid>
		<description>@Bryan,

Great to hear you&#039;re open to feedback from your customers. I appreciate the kind words toward my review.

I didn&#039;t realize how many servers you had running on the backend. It sounds like you won&#039;t have many issues with heavy traffic.

I&#039;m really looking forward to using Typekit in my future work. It is by FAR the easiest (and least stressful) way I&#039;ve found to use unique fonts on my designs.</description>
		<content:encoded><![CDATA[<p>@Bryan,</p>
<p>Great to hear you&#8217;re open to feedback from your customers. I appreciate the kind words toward my review.</p>
<p>I didn&#8217;t realize how many servers you had running on the backend. It sounds like you won&#8217;t have many issues with heavy traffic.</p>
<p>I&#8217;m really looking forward to using Typekit in my future work. It is by FAR the easiest (and least stressful) way I&#8217;ve found to use unique fonts on my designs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Mason</title>
		<link>http://iloveusability.com/usability-review/typekit/#comment-26</link>
		<dc:creator>Bryan Mason</dc:creator>
		<pubDate>Wed, 30 Sep 2009 00:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://iloveusability.com/?p=204#comment-26</guid>
		<description>Kevin - Thanks for the thoughtful and thorough analysis. A couple of points I want to address:
 
&lt;em&gt;&quot;but how it will perform under a heavy server load remains to be seen.&quot;&lt;/em&gt;

We&#039;re working with a CDN that has server-centers on five continents. We have a 100% uptime and latency guarantees.

We&#039;re looking at all your suggestions and really appreciate the feedback.

And Wolfgang&#039;s suggestions about search and discoverability are right on, and we&#039;re working on it.</description>
		<content:encoded><![CDATA[<p>Kevin &#8211; Thanks for the thoughtful and thorough analysis. A couple of points I want to address:</p>
<p><em>&#8220;but how it will perform under a heavy server load remains to be seen.&#8221;</em></p>
<p>We&#8217;re working with a CDN that has server-centers on five continents. We have a 100% uptime and latency guarantees.</p>
<p>We&#8217;re looking at all your suggestions and really appreciate the feedback.</p>
<p>And Wolfgang&#8217;s suggestions about search and discoverability are right on, and we&#8217;re working on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://iloveusability.com/usability-review/typekit/#comment-25</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Mon, 28 Sep 2009 20:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://iloveusability.com/?p=204#comment-25</guid>
		<description>Definitely agree with you there, Wolfgang!

All it would take to fix that problem is to have a tiny search box on the sidebar (possibly right under the &quot;Invite your friends&quot; box).</description>
		<content:encoded><![CDATA[<p>Definitely agree with you there, Wolfgang!</p>
<p>All it would take to fix that problem is to have a tiny search box on the sidebar (possibly right under the &#8220;Invite your friends&#8221; box).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wolfgang Wopperer</title>
		<link>http://iloveusability.com/usability-review/typekit/#comment-24</link>
		<dc:creator>Wolfgang Wopperer</dc:creator>
		<pubDate>Mon, 28 Sep 2009 19:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://iloveusability.com/?p=204#comment-24</guid>
		<description>thanks for the review!

last time i used typekit, though, i sorely missed another feature: to search for fonts more easily. browsing fonts by type was quite easy, but checking if a certain font was there (or if a similar font is available) wasn&#039;t possible. for my use cases, this is vitally important, and i would love to see this feature in the near future.</description>
		<content:encoded><![CDATA[<p>thanks for the review!</p>
<p>last time i used typekit, though, i sorely missed another feature: to search for fonts more easily. browsing fonts by type was quite easy, but checking if a certain font was there (or if a similar font is available) wasn&#8217;t possible. for my use cases, this is vitally important, and i would love to see this feature in the near future.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
