339: ‘2006: Hard Work’, With Ken Kocienda

Episode Summary

Executive Summary: The conversation centers on Ken Kocienda’s path from working on Safari/WebKit to joining the secret iPhone team, where he created the original software keyboard and helped shape the touch-first interaction model. It also explores Apple’s culture of speed, focus, secrecy, and ruthless product trade-offs, plus Kocienda’s writing process, his book Creative Selection, and his current work at Humane and on the game Up Spell.

Main Topics: Origins of Safari and WebKit (Priority: 5/5): Kocienda recounts joining Apple in 2001, being recruited by Don Melton, and the early uncertainty around building a Mac browser and web framework. The team evaluated multiple paths before settling on KHTML/KJS, which became WebKit and later influenced much of the modern browser ecosystem. The Secret iPhone Project and Touchscreen Bet (Priority: 5/5): He explains how he joined the iPhone effort in 2005 after stepping away from a management role, signing an extra NDA, and learning Apple was building a phone. The team bet on a full touchscreen interface and had to solve text entry and interaction from scratch. Designing the iPhone Keyboard (Priority: 5/5): A major focus is the keyboard bake-off, iterative rewrites, and the eventual breakthrough of a predictive text system that let software infer intent from taps. The story illustrates how the keyboard became a foundational example of Apple’s software-first product thinking. Apple’s Culture of Performance and Trade-Offs (Priority: 4/5): The discussion emphasizes Don Melton’s no-regressions browser rule, Steve Jobs’ insistence on making great products and moving on, and Apple’s willingness to abandon or revise ideas that didn’t meet standards. Speed, simplicity, and user experience repeatedly trumped feature accumulation. Writing a Book vs. Blogging (Priority: 3/5): Kocienda reflects on whether he will ever write another book, contrasting long-form writing with Daring Fireball’s column format. He describes his own writing process as disciplined and constrained, inspired by Stephen King’s advice and by organizing Creative Selection as a sequence of chapters. Current Work: Humane and Up Spell (Priority: 2/5): He briefly mentions working at Humane, which is hiring, but avoids discussing the project in detail. He also notes his pandemic-era iPhone word game Up Spell, which he uses as a lighter creative outlet and a contrast to Wordle-style play.

Key Arguments: Apple’s success depended on small teams making ambitious bets, but those bets only worked because the company paired vision with relentless execution and the willingness to kill or revise weak ideas. WebKit and Safari were not inevitable; they emerged from a few engineers, open-source experimentation, and strong product judgment, and the decision to build a framework as well as a browser proved crucial later. The iPhone keyboard succeeded because it used software to compensate for the loss of tactile hardware input, turning a seemingly obvious touchscreen keyboard into a flexible predictive system. Keeping the browser fast was a product requirement, not a nice-to-have; Don Melton’s rule that code could not make Safari slower forced the team to optimize continuously instead of accumulating debt. Apple’s touch UI philosophy prioritized one-to-one finger tracking over perfect rendering, accepting temporary hacks like checkerboarding to preserve the illusion of direct manipulation. Kocienda argues that writing books is less about deciding to write a book and more about finding an idea that demands long-form treatment; his best work comes from digging out a “fossil” already in his head. The iPhone team’s breakthrough depended on a generalist culture where engineers could rapidly pivot, unlike specialists locked into legacy phone assumptions. Steve Jobs’ role was less about individual implementation and more about editing, selecting, and aligning pieces into a coherent whole. The Motorola ROKR episode reinforced Apple’s desire to control the whole experience and showed why a fully Apple-made phone was necessary. Kocienda sees product development as a series of trade-offs between incomplete options, not a simple march toward perfection; the key is choosing the right compromise at the right time.

Data Points: Creative Selection publication date: September 3 or 4, 2018 - Used to frame the podcast’s late timing relative to the book release. Time between book release and interview: 3+ years late - The host jokes that the guest appeared years after the ideal promotional window. Daring Fireball anniversary: 20th year approaching - Kocienda notes it is his 20th year of writing Daring Fireball. Daring Fireball 15-year word count: 2,000,000 total words; about 1,000,000 original words - Kocienda cites a script he wrote to count the site’s output at its 15-year mark. Daring Fireball output at 15 years: 1,173 full columns and 25,486 link-list entries - Quantifies the volume of his writing over 15 years. Creative Selection manuscript length: About 110,000 words before editing; final book about 77,000-80,000 words - He describes drafting the book in roughly 100 days and later editing it down. Writing pace for the book: 1,000 words/day - Kocienda says he set a goal of 1,000 new words per day, 7 days a week. Stephen King’s benchmark: 2,000 words/day - Kocienda references King’s writing discipline from On Writing. Safari/browser early team size: 3 people initially; eventually about 8-10 people - Describes the tiny team that created Safari/WebKit. iOS software team size: About 10-15 software engineers and 8-10 designers - Approximate size of the iPhone software effort when he joined. Phone project start window: May-July 2005 - UIViews in UIKit were being created in May 2005; Kocienda joined in July 2005. ROKR announcement timing: September 2005 - The Motorola/Apple iTunes phone was unveiled after the iPhone effort had begun. Browser performance gap at start: 3-5x slower than IE on Windows - Early Safari/WebKit performance was benchmarked against Internet Explorer on Windows. Mobile form factor: 3.5-inch diagonal screen - Describes the wallaby iPhone prototype hardware. Book count used in research: 6 books with about 8 bookmarks each - Kocienda mentions juggling multiple sources while researching the iPhone origin story.

Pivotal Quotes: "If you do something and it turns out pretty good, then you should go do something else wonderful, not dwell on it for too long. Just figure out what’s next." — Steve Jobs (quoted by Ken Kocienda): Cited as a core Apple cultural principle about moving forward rather than celebrating past wins. "The way we were going to make the web browser faster is by never making it slower." — Don Melton (quoted by Ken Kocienda): Describes the no-regressions rule that governed Safari/WebKit development. "We’re going to make a cell phone." — Henri Lamoureux (as recounted by Ken Kocienda): The moment Kocienda officially learned he was being added to the secret iPhone project.

Implications: The episode shows how major products emerge from disciplined teams, clear constraints, and uncompromising attention to user experience. It also suggests that software frameworks, not just hardware, can shape entire industries for decades.