: What's the pro/cons of Adobe TypeKit API? Any best practices? With all the Open Source fonts I have available, and I can download them via the CSS font directive, what's the benefit of the

@Speyer207

Annoyingly on-line fonts are not supported by all browsers (Opera on the iPhone being a pet peeve).

Google Fonts pure CSS system seems to work better than the alternatives, but you can end up with a FoUC on many browsers.

Google Font API "...was co-developed by Google and TypeKit" so I hope the following experience is similar enough:


the JavaScript library is quite light, but watch out for any serious increase in latency from the extra DNS lookups and HTTP connections that may be caused by cross-domain resources
using the JSAPI version is quite slow on an empty cache (as a side note you also can't combine JS requests into one big file)
being able to declare the fonts needed separately from the JavaScript include allows for post-loading the library and really helps with (X)HTML template flexibility
the extra paint events triggered when the JavaScript library re-paints the entire screen by changing page-wide classes will mean your CSS has to be efficient (Google offer a guide on this)
whilst having to declare italics and different weights with some fonts decreases the download size, it adds an extra burden to either the designer or the programmer
custom fonts, used tastefully, look beautiful

Vote Up Vote Down