Judson Collier

NOTE: In this article, I pose many questions to both TypeKit and to foundries. I’m not exactly suggesting these things will happen, but they are in the realm of possibility and should be answered. I’m a skeptic at best, and I only criticize it because I want web fonts to succeed.

As of late, the hot issue is fonts on the web, with font-face. To keep it simple, Font-Face allows us to upload fonts on our server so *any* font can be used, rather than just the standard set.  That said, the fonts are unprotected, so everyones in a tizzy on how to fix that (which is fine; i’d rather not deal with it, but I don’t have much of a choice).

So, fast forward a few years later, Jeffery Veen leaves Veer, and creates TypeKit: a system that masks the location of your font so we can now use font-face. Sweet.  The Catch? Annual fees, limited by the participation of font foundries.

In reality, although I totally dig the concept of TypeKit, it doesn’t seem like a sustainable model for delivering fonts. Realistically we should be getting our web license directly from the foundry, and in a pricing structure that makes more sense.

(Click through for the rest, folks)