Can Typekit Bring Fonts to the Web?
When I first heard about Typekit, a new service that aims to bring typography to the web, I was skeptical. I’ve been around the high-tech sector long enough to know that most of these new products are a rehash of technologies past. And from what I had heard, Typekit just sounded like another way to hack fonts on the web. Methods like sIFR and Cúfon already exist, and though successful, they’re not the most elegant ways to address a very real problem: Designers have seven core fonts to use reliably on the web, and four of those are horrendous.
Then I read the blog post announcing Typekit—a post that garnered 328 comments in three days—and talked to a few other people about what the service actually was going to be. Quietly, I started to feel that kind of anticipation one gets when a really great movie is about to be released. Could it be real?
Jeffrey Veen, the founder of Silicon Valley start-up Small Batch and the brains behind Typekit, started out as HotWired’s lead interface designer in the early days of the web boom, then went on to become a founding member of Adaptive Path, a design and technology-services company in the Bay Area. From there, he helped design what became Google Analytics. Last Christmas, when he met up with John Allsopp, a prominent web designer and developer, the conversation turned to @font-face and how to make it work, given the current licensing models.
@font-face gives web designers the ability to use additional fonts beyond the usual seven available from OS manufacturers, including access to features in OpenType like ligatures and swashes. You can now de-
sign for the web the way you design print, motion, or any other media. The problem is that, although the World Wide Web Consortium has created a standard to render fonts in a web page via a CSS rule, @font-face still leaves the fonts accessible on a web server. Anyone who knows how to find the font can then download it easily without paying for it. Type foundries, in an act of self-preservation, have written licenses to exclude this behavior, fearing (with good reason) that if their fonts are opened up for download, people will just copy them endlessly from servers around the world. So while designers can use @font-face, oftentimes in doing so they are violating the license and breaking the law.
Veen proposes a different model. “I basically realized what was needed was to build fonts as a service,” he says. Rather than attempt to sell fonts for individual computer use, which is how most type foundries treat the licensing of their fonts, the service sells access to fonts for the explicit purpose of being used on the web, built in a similar way to Google AdWords or Amazon Web Services. Typekit is most innovative as a business model—the technology it’s based on has been around for a few years.
There are two important questions, however. First, how much will it cost? Veen is hesitant to answer directly. He hopes that designers will pay somewhere between $50 to $150 a year for an account; large corporate accounts will cost more. Veen’s primary concern, however, is to create a price point that will let nondesigners access fonts for their blogs or other emerging online presences. It’s here that Veen thinks Small Batch has a big opportunity to expand the typography market.
The second question is whether the foundries will sign on. Some remain skeptical, although Veen says that smaller foundries are enthusiastic, seeing the service as a way to access a whole new market. Meanwhile, the big foundries are trying to avoid the hard lessons of the music industry.
Will Typekit be the way to reinvent typography and, as a result, the design of the web itself? This designer is hopeful that the result matches the expectations.