Podcast Search

The Talk Show

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

Select a time to play from there. The line being spoken is highlighted as the audio plays.

0:00:00Ken Kishenda, welcome to the talk show. You're overdue.

0:00:02A little bit. By how many years would you make it out to be?

0:00:07Your book, let me actually check the copyright date. 2018.

0:00:11So what time of the year in 2018 did creative selection come out?

0:00:14It was September the third or fourth as I recall.

0:00:20So what, three plus years late. Because, and I call the show the talk show, and I like to think

0:00:26it is like a real talk show, but the whole point of actual most actual talk shows is that when you

0:00:33have a guest with something to promote, if it's on the Stephen Colbert show or something like that,

0:00:38and there's a movie, they'll have the actor come out right before or right when the movie first

0:00:43hits theaters or in that would have made my publisher really happy. I can say the bright

0:00:49side of that. I tell you though, the bright side of the publisher was very happy with you because

0:00:55your link to the book was by far the best publicity that the book had. There was a huge bump

0:01:05in pre-orders right after you linked. And I tell you a funny story about that is that I didn't know

0:01:11that was going to happen. And my wife and I were in the car. We were driving down the coast towards

0:01:19Santa Barbara for just a weekend getaway. And maybe we can look back at the date. Maybe it

0:01:24was a Friday or a Saturday or something like that. So we were going into a part where I was

0:01:29going to lose cell phone coverage. And I wasn't looking at my phone anyway, because my wife and I

0:01:33were enjoying the conversation, enjoying our company, enjoying the beautiful scenery. And then

0:01:39you link to my book. It's all Holy cow, wait a minute. I got to look at it. I got to read this,

0:01:46what he said, and then be looking at what the feedback would be. And then it's like the

0:01:51cell phone coverage dropped out from the hour. And it was a pretty agonizing hour, not knowing

0:01:57what was going on in the virtual world when all of this beautiful scenery was going by in the

0:02:02real world. And I couldn't pay attention to it. Thanks for that, John. I don't know. I don't know

0:02:07where I'm not quite sure what to say. I cannot explain it. The way my mind works is inscrutable.

0:02:15And I really did plan on having you on the show shortly after before around when the book came out.

0:02:21And somehow felt overwhelmed because the book I really am not I'm not just saying this because

0:02:26you're on the show right now. But I partly it was because the book is so good. And I didn't even

0:02:33know where to start. And I'm going to tell you, here we are three and a half years later, I still

0:02:37don't quite know where to start. But based on the piece I just published last night that I've been

0:02:43working on for a while, let's let me just take my best stab right now at delineating the origin of

0:02:49the iPhone and putting it into a timeline go. And I your tweets in response to the stuff that I you

0:02:57know, it started a month ago, I'm assuming most people listening to this read my piece or at least

0:03:02follow during fireball closely enough that they saw it because it was pretty big. But basically,

0:03:06a month ago, there was a story came out about Facebook having two competing VRXR OS's for years

0:03:14with hundreds of people working on this other one and then pulled the plug on it late last year.

0:03:19And the executive in charge of it left to go to Google to head up AR VR XR and I offhandedly a

0:03:26short post on during fireball compared it to the famed bake off at Apple in the early days of the

0:03:33iPhone project between sort of a ground up Linux embedded OS sort of thing to make a phone versus

0:03:41what we now know as iOS famously a sort of let's take Mac OS 10 and strip it down to make something

0:03:48new that both performance wise can run on a tiny little cell phone of 2006 2007 era hardware,

0:03:56which would be a hell of a thing to do with Mac OS 10 at the time, and redo the whole UI to work

0:04:02with this new metaphor. Long story short, we all know how it turned out. But it was anyway,

0:04:06my linking to it was a bad comparison. And we could start there. I think it's not all that bad,

0:04:12because how many operating systems get started at all at companies that could realistically

0:04:21finish it. And so it was an interesting story and an interesting occurrence at Facebook.

0:04:30Obviously, they bet the whole at least the whole name of the company on on a future that is

0:04:39different than their past. And Facebook just being an app and their future maybe being something more

0:04:46like a platform kind of makes sense that you would want your own operating system. And so

0:04:51the change in the direction of that is interesting. There is this story that maybe we're, you know,

0:04:59going to get to the bottom of it a little bit more given your looking into it, and maybe some

0:05:05of the stories that I can tell, but I think it's a perfectly interesting and valid analogy. Or maybe,

0:05:11and maybe that's an analogy that it's maybe less of a comparison and more of a contrast.

0:05:16But maybe I can thank you because that's what then led to us talking right now. I can't think

0:05:23you really too much. But I do think it is an interesting comparison. And it would be interesting

0:05:28if you could find people someday to come on and talk to you about the effort that went on

0:05:34inside Facebook matter what led to their decision being what it is particularly of meta turns out to

0:05:40be as successful as the iPhone was. Yeah, maybe here. Let me just take a break though, before we

0:05:45get rolling and figure out how we're going to do this. Let me take a break right here and thank our

0:05:52first sponsor and it is our good friends at remote. Do you employ or pay workers in other countries,

0:05:59even if you don't yet, you might soon now that remote work is the norm employees have more

0:06:04freedom than ever to move around. If you want to keep your best people, you want to hire the best

0:06:08people, you have to stay flexible. That's why remote makes it easy for companies of all sizes

0:06:14to employ global teams. They take care of international payroll benefits, taxes and

0:06:20local compliance so you can focus less on paperwork and bureaucracy and more on growing

0:06:26your business. Remote helps you onboard full-time employees or contractors in countries all over the

0:06:31world in minutes on its simple easy to use platform. Even better remote lets you rest easy

0:06:37by providing the most comprehensive intellectual property protections and data security in the

0:06:42industry. They own full legal local entities in all their covered countries, guaranteeing you

0:06:47never have to deal with a third party ever. You just deal with remote to save you money.

0:06:52Remote never charges any fees or salary percentages. You get access to everything remote

0:06:57offers from payroll to compliance to benefits management for one low flat rate, no hidden fees,

0:07:02no surprises ever. Just the best global employment solution in the business. Best of all,

0:07:08listeners to this show, the talk show, get an even bigger discount. You get 50% off remote's full

0:07:13suite of global employment solutions for your first employee for three months. Just visit

0:07:19remote.com/thetalkshow. That's remote.com/thetalkshow and use that promo code,

0:07:27the talk show, 50% off your first employee for three months. See why top global companies like

0:07:32GitLab trust remote to manage and pay their international teams. Whether you want to hire

0:07:38one person or 100, remote makes it easy. Just go to remote.com/thetalkshow and remember that

0:07:44promo code, the talk show. We can talk about remote work later too. That's been in the news

0:07:51with Apple and is an interesting comparison. Oh, for sure. Particularly given my great preference

0:07:57to work in person with people and trying to balance that out, given how the world has changed

0:08:04over the last couple of years. Even just today, I was, and it's a Saturday that we're recording,

0:08:11I went in extra to spend some time with Imran Chaudhry, my colleague, and he's one of the

0:08:18co-founders at the company I'm working on now. And that's about all that I'm going to be able to say

0:08:24about what I'm doing at Humane. That could be maybe a future topic for another visit with the

0:08:32factor of how long it would take me to have you invite me back on. I can't maybe really speculate

0:08:39how long that would be, but we have plenty to talk about now. I'd never known about it, the future,

0:08:44but the past, what could I tell you about the book? Maybe even the process of writing the book.

0:08:50I mean, one of the things I wanted to ask you about is that you're a writer. What is your idea

0:08:56about whether you might write a book of your own someday, or is it just daring fireball? Is there

0:09:02something about the format, the kind of blogging format that just fits you better as opposed to

0:09:09something more long form? That's a tough question. I mean, I've obviously thought about it, but one

0:09:13of the things I wanted to, and rereading your book and revisiting all of this, which now, you know,

0:09:20let's face it, it's history, right? And it's like you get to a certain age, and I swear this

0:09:25digression is going somewhere, but when you're young, let's just say right out of college, 22,

0:09:3023, around that age, when you think about things that happened 20 years before that,

0:09:37it feels like ancient history. And even if you were technically alive, like for me, like Nixon

0:09:42resigning from the presidency, and I was like, I don't know, one and a half years old, it happened

0:09:47in my lifetime, but it feels, I don't know, it felt like true history, like history with a capital H,

0:09:53not like lived history, you know, and you hear about things like the creation of Unix, and like,

0:10:00why did they pick 1971 as the epoch date for time? It's because that's like when they first had it

0:10:05running, and it's like, sure, in 1991, that was 20 years ago, but the original version of Unix

0:10:11felt like ancient computer history 20 years prior. But now, here I am in my late 40s, and

0:10:19it feels like stuff that happened 20 years ago. I know it wasn't recent, but boy, it sure feels

0:10:25more relevant than it did. And so here I am in the 20th year, going into the 20th year later this

0:10:33year of writing Daring Fireball, and the— Well, that's an amazing milestone. Congratulations.

0:10:40Well, congratulate me when I get there. And I've never won, I think I've only

0:10:45even commemorated one anniversary, I think the 15th or something on Daring Fireball. I'm not one to

0:10:50make a show of stuff like that. Not out of—it's not that I'm overly humble, it's just like an

0:10:57innate sense of that Steve Jobs axiom, and I'm sure he'll come up more times here, but that's

0:11:03sort of, if you do something good, take a moment to appreciate it. I'm paraphrasing here, but move

0:11:07on to the next thing and make something else that's good. It's, you know—

0:11:10That's right. As a matter of fact, that quotation, at least when I worked on the Infinite Loop campus

0:11:18for all the years that I did, more than 15 years, certainly in the later part, maybe it was even

0:11:24after his passing that that quote that you're mentioning was painted up on the wall outside

0:11:30of the town hall, the on-campus auditorium. I mean, really quite famously, Steve was

0:11:36uninterested in the past, and certainly uninterested in reveling in the past.

0:11:45I remember when I joined Apple in June of 2001, I worked on the Infinite Loop campus in Cupertino

0:11:52in Building 2, and on the second floor, there was a miniature NeXT museum. There was some NeXT

0:12:02hardware, there was a cube and a slab, and then some Sun hardware, I think, that was running

0:12:09NeXT step. Once NeXT got out of the business of making its own hardware and making software for

0:12:14other platforms, so there was maybe six or eight machines there. And of course, this was 2001,

0:12:20so Steve had been back at Apple for years by that point, but not long after that, the word came down,

0:12:27"Nope, that stuff is just getting bundled up and sent off." I either sent it to the

0:12:32Computer History Museum in Mountain View, just close by, or I think maybe, as I'm thinking about

0:12:38it now, somebody at Stanford took it, but he was just like, "Clean that stuff out. We're making

0:12:43new things. Just don't worry about the past. These computers running this ancient software with little

0:12:50cards and exp—what place does that have in a company that is focused on innovating and making

0:12:59new products that are going to, at that point, trying to dig Apple out of a hole of having only

0:13:075% market share in desktop computing." And thinking about that from the point from June of 2001,

0:13:14it was only four months later that the iPod was announced. And that was, in some ways,

0:13:23the real solution, the real jumping-off point for Apple, the moment where Apple ceased to be

0:13:31what it was and started being what it has become—new products, new platforms, and a whole

0:13:38different order of success. I have the quote in front of me. "I think if you do something," this

0:13:44is from Steve Jobs, "I think if you do something and it turns out pretty good, then you should go

0:13:49do something else wonderful, not dwell on it for too long, just figure out what's next." I believe

0:13:54that's the part of the quote that's on the wall. Last time I was at town hall for a media event,

0:13:59it was certainly still there. I certainly can't believe they'll take that down.

0:14:02But I don't know what they use town hall for anymore. COVID restrictions aside,

0:14:08media events are now on the new campus. It's never going to stop seeming weird to me that the old

0:14:13campus was infinite loop and the new campus is a building that's a loop. So I always want to say

0:14:19infinite— Well, there is a loop of six buildings. I wish I had a count. I wish I had a nickel for

0:14:27every time that during the day, either solving a—trying to work through a hard problem that I did

0:14:32laps around the outside of that loop. Yeah, it is aptly named. It was really a beautiful place to

0:14:38spend 15 years of my working career, for sure. But that quote really does sum up so much of

0:14:46the culture that Steve tried to bring to Apple that people like me, an individual contributor,

0:14:53never a big executive, never really spent that much time with Steve, although I did

0:14:59a couple of times. And as I tried to write in my book, those few times affected me very greatly,

0:15:05had a huge influence on the way that I did my work. And so quotes like that, it's part of the

0:15:12culture, it's part of the lore, it's part of what we were shooting for, part of what inspired me to

0:15:18do the work that I did on the products we were trying to make. Yeah, it definitely expresses its

0:15:23sentiments. The other thing I know that I think it was Steve Jobs who got rid of was the icon garden.

0:15:29They had some of the original Mac, like, 1984 icons somewhere in the infinite loop. Not really

0:15:36sculptures, but two-dimensional things stuck in the grass, and they got rid of them. Yeah,

0:15:40so they got rid of those things. The numbers outside of the building are the last vestige

0:15:45of that. They never replaced those. But even back in 2001, you'd go into the reception area

0:15:52of infinite loop 2, and then there was a glass door, a set of glass doors that, I mean, you've

0:16:00probably seen them, John, but other visitors will have as well. But the glass right at a

0:16:07RAM maybe chest level had some stenciling on the glass of those old one-bit icons. And yeah,

0:16:14just maybe 2002, 2003, they just come in one morning and that day they were scraped off and

0:16:21never put back. Again, not focusing too much on the glorious past, but trying to make a better

0:16:29future. I don't want to keep moving on. We can do this. We can talk about you writing your book

0:16:34next. First, starting, dodge the question of, do I think I have a book or books in me? Where I was

0:16:39going is I always thought maybe, and let's put aside the idea of best of collection from Daring

0:16:45Fireball, which is sort of a cop-out, right? You can put that in a book. People might enjoy it as

0:16:50a book, but that's not writing a book. That is, it's a different thing. So I've always had the

0:16:55idea and it always, in some self-effacing way, felt like real writers are book writers. And not

0:17:05real writers, that's even too dismissive. But for whatever reason, I've always, even before Daring

0:17:11Fireball became a thing, I always felt like a columnist is the scope of my aptitude. And it's

0:17:22not Stephen King, whose book on writing is one of the best writing books I have ever read. One of his

0:17:28things though, is that if you don't have time to read, you don't have time to write. You have to

0:17:32read to be a writer. And I read voraciously, of course. And I do read, I read a tremendous more

0:17:38amount of short form writing on news and stuff like that, stuff that I link to, then I do read

0:17:44books. And I read fewer books than I used to. And I can't explain why and I feel a little guilty

0:17:50about it. But long story short, I don't know. I don't know if I have it in me. I don't know.

0:17:56And I guess the big thing is that whenever I do write something, it's because I feel like I've got

0:18:00this idea in my head and I need to get it out. And one of Stephen King's analogies is that all

0:18:05of the things he's written, he imagines them as like fossils in the sand or in the dirt.

0:18:10Writing is like digging out the fossil. He doesn't know how big it is because it's in the ground. And

0:18:15then he digs it out. And of course, for Stephen King, a lot of these are like 500 page novels.

0:18:19I feel the same way though about articles that I wrote, like the one I wrote on the origin of the

0:18:25iPhone. So I've got to write this. I don't know how long it's going to take me. I don't know how

0:18:29long it's going to be. Is it a thousand words? Is it 3000 words? Is it somewhere in between? I don't

0:18:34know. I just have never started digging on an idea where it feels like this is a 60,000 word

0:18:39book broken into chapters. But maybe I approach it wrong. And this, I would love to know the way

0:18:44you approached your book is maybe it's, you shouldn't, maybe you shouldn't think, I shouldn't

0:18:49think about writing a book, but instead think about an idea for a book that is composed of

0:18:55chapters and chapters are more like articles, which is what I write and think more about

0:19:00the practicality of writing chapters as opposed to just sitting down, start to finish writing a book.

0:19:05I, to go back to Stephen King, he, I found his book extraordinarily helpful to those of you

0:19:13listening who are unfamiliar with the book. It's, it's wonderful, highly recommended the first,

0:19:20and he breaks it up into two parts. The first part of the book is autobiographical. He tells the

0:19:25story of how he and, but really more almost like a memoir because he doesn't from start to finish,

0:19:32tell the story of his life, but tells enough of his earlier life to understand how it is that

0:19:39he became a writer and how it was something similar to this fossil analogy that he uncovered.

0:19:50In some ways he couldn't help himself. And so it can have been some respects. It's, it really is

0:19:56the right job for him. And he also did address the subject matter that he uses as his raw material

0:20:05for his writing and how for a long time, he felt that there was something either cheap or coarse

0:20:17around writing the sorts of books that he did. He almost felt sorry for it. Sorry about it.

0:20:24Felt that he needed to apologize. And he's saying, you know, he said that it was really

0:20:30later on in his life that it's just like, Hey, now look, this is what I have. This is what,

0:20:36when he turns his mind toward being creative, this is what just comes out.

0:20:41And, you know, and I think that in some ways that is that that's the answer for you. I mean, look,

0:20:48daring fireball is something that probably I have read every day since you start, since I discovered

0:20:57it shortly after you started writing it. And so sort of second guessing yourself on what you

0:21:03should write, you know, seems to me not to be a question really worth thinking about for as long

0:21:09as there's something that comes along that you say you have to do. It's like, you have to write this

0:21:14story on the origin of the iPhone. Then you're probably doing as well as you can. I mean, you

0:21:19know, if you can find inspiration in things and there's something that's going to get you out of

0:21:24bed in the morning and work creatively, then, you know, who's anybody to second guess what that is?

0:21:31I don't worry about it. I've never felt too bad about it. My dad seems to want me to write a book.

0:21:36I'm glad he doesn't listen to the podcast. But it's sort of like, you know, I tell this story.

0:21:43I've told it often where my dad has always been very supportive, both my parents, very supportive

0:21:49of what I do, but they don't really get it. They don't, you know, I've been doing it enough years

0:21:54now that they trust me now and they see that I'm successful. But in the early years, they really

0:21:59didn't get it because the web is just not of the, I mean, they go to the web, but this just never

0:22:04seems as real to them. At some point, several years into writing Daring Fireball, I got to

0:22:09start writing occasional back page columns for Macworld, which for Apple punditry was always the,

0:22:17you know, that's the prime spot, right? There's only one back page column on Macworld and Macworld

0:22:24was always the sort of, you know, the gold standard of Mac. Oh, it's very prestigious. Sure.

0:22:30And it really, really impressed my dad. I mean, he was just like tears in his eyes blown away,

0:22:37like, oh, and I'm thinking like, I should have bought more copies of this for him, you know?

0:22:43But like my wife said afterwards, and my wife loves my dad, but she was just like,

0:22:47doesn't he understand that you've built something way better, you know? You know what I mean? Like,

0:22:53building Daring Fireball by that time was more of an accomplishment than getting on the back page of

0:22:57Macworld. But being in print, I still do love print. I always will. And that sort of dates me.

0:23:04I'm, you know, student newspaper guy coming up through college. I do love print. I love typography.

0:23:10I don't think typography ever looks as good on a glowing screen, no matter how many pixels it has,

0:23:15than it does printed on paper. I love it. I love the tangibleness of it. I do love it. So,

0:23:23you know, never say never on me writing a book or collecting stuff into a book or something. I just

0:23:27said that to somebody on Twitter again today. Never say never, but I don't know. But, yeah,

0:23:34I mean, it's finding the right medium for the message that you're trying to convey to people

0:23:42is a trick. To me, I like having constraints. And when I left Apple in May of 2017, I didn't know

0:23:58what I was going to do. And as I was contemplating leaving, I had a friend get in touch. Her name is

0:24:10Kim Scott. And she is the author of two books that have gotten some mindshare out of the world.

0:24:19Radical Candor is one and Just Work is her more recent book. And right at that moment,

0:24:25when I was really thinking about, well, what's next for me? Her book Radical Candor came out,

0:24:32and she invited me to the book release party, which took place in Palo Alto. And so I wrote

0:24:40over there after work one evening, and she introduced me to her editor. And her editor,

0:24:47you know, started questioning me. Well, hey, Ken, what are you doing? You know, maybe you should

0:24:52write a book. And I found out later that Kim Scott, it was a total setup that she had been

0:24:58like a blind into her editor about it. So it really was blind. It's a blind date. Yeah,

0:25:04it actually actually totally was. And fortunately, the fellow, his name is Tim Bartlett. He's he's an

0:25:13absolutely marvelous, marvelous editor and so smart, so, so good at his job. And he said,

0:25:24well, you know, you if you want to write a book, just send me a proposal. And I got the wheels

0:25:28turning. And, you know, I'd really already decided, but not not yet announced that I was going to be

0:25:34leaving shortly thereafter. And, you know, it just kind of like all the planets aligned. So within

0:25:43just a few days of leaving Apple, I had sat down and started started keyboarding started didn't

0:25:53quite put pen to paper I was I did the whole thing electronically. But this gets me back to then

0:25:59Stephen King. The other thing I wanted to say about the other half, the second half of the

0:26:03on writing book, which is Stephen King's advice on how to do the job of writing. And again, he

0:26:12made it very personal related what he did. And the that whole section is and I have to say that I

0:26:21didn't actually read the book. I had Stephen King read it to me. And he's a marvelous reader of his

0:26:27own material. So, so he told me he came to your house or you listen to the audio book.

0:26:34No, no, I listened to the audio book.

0:26:36All right. I just didn't know I just wasn't being unclear. No, no, no, no, no. I wasn't quite sure.

0:26:41I wasn't quite sure how just how well you did at Apple.

0:26:46Not not that well, I doubt sincerely, although Stephen King is an avid user of Apple products,

0:26:55I doubt very sincerely that he has ever, ever heard of me. But so I had the audio book to be

0:27:03perfectly clear. And so listening to him, he said that what he did, he had a process is that he

0:27:10wrote 2000 new words every day, he'd get up in the morning, and he would set about putting those 2000

0:27:17words down. And he said, Well, you know, if if he had a good day, and and the writing was easy,

0:27:24he finishes up 10am. And then he can go get a cup of coffee, have a walk, why did you do some

0:27:30shopping? That's it, he's done. He satisfied his obligation, and the pressure is off. Now,

0:27:37other times the writing is more difficult to do. And he says, you know, he's particularly as he

0:27:42started getting older, that he was still at work at four and five in the afternoon, but the goal

0:27:48was to set down 2000 new words a day. And that seemed to be a really wonderful discipline. And

0:27:56so like I said before, I like to have constraints. And and so I said, Well, I'm not nearly as good as

0:28:03Stephen King, but I set myself the ambitious goal of writing 1000 new words a day. And,

0:28:07and that's what I did seven days a week. Yeah, I wasn't working anymore. And so this was the job

0:28:15that actually worked out pretty well. I actually have a spreadsheet on my machine, I don't have it

0:28:21up here now. But I would write down every day, how many how many words I did. And it was, I was

0:28:30pretty good. And with within 100 days, I had about 110,000 words, because sometimes I, you know,

0:28:39you kind of kept going. And that formed the core of the whole of the whole book. And you know,

0:28:47the interest, you know, the part of it is that I kind of knew what I wanted to say. And so the

0:28:53writing was kind of easy, because it was going back over my memory and trying to tell this

0:29:01firsthand account of what what happened. So I, you know, I have a lot of sympathy in a way,

0:29:08for you trying to write this story, like on the origin of the iPhone, because you're not just

0:29:14going back over your own memory, you're trying to disclose and uncover facts that either don't exist

0:29:20or are locked away in somebody else's memory. And you have to try to piece together all of these

0:29:27accounts, I didn't set myself that nearly as difficult a task as that, in some ways, I marvel

0:29:34at what you're able to do with with a story like that. How do you get this idea in your mind that

0:29:41you want to write this story on the origin of the iPhone? What do you do? Well, here, let me say

0:29:46this. Let me just go back before I forget, while we're sticking our fingers and pages and going

0:29:50back to them as we continue forward. I did I did write a post when Daring Fireball turned 15,

0:29:56in August of 2017. And I ran, I don't think I mentioned this in the article. Now, I will put

0:30:01this in the show notes. But my friend Jim crude all had suggested I do this at some point when

0:30:06we had gotten together, then he was just like, I wonder how many words you've written, you know,

0:30:09at Daring Fireball. So I wrote a little script to do a word count. And it five years ago, I guess

0:30:17that would be four and a half years ago, I had written 1173 full columns, that's the full length

0:30:25articles, and 25,486 link list entries where I linked to somebody else in the full columns I had,

0:30:34and it's amazing how even it worked out 1,048,000 words. So let's call it a million, a million

0:30:40original words, and 200,000 extra words that were in block quotes. So in other words, when I quote

0:30:47from somebody else in one of my articles, which I obviously, you know, anybody familiar with my

0:30:50style knows that's sort of fundamental to the whole format is a lot, but in the full articles,

0:30:56you know, a million original words, linked list entries, 950,000 original words, but of course,

0:31:03in those entries, 2,000,000 total words, including block quotes, but that added up to two over just

0:31:09over literally, it was I honestly did not plan this combined original words 2,001,516. So just

0:31:20two million on the button for 15 years. Sounds like a lot, and it did, it was, it was, it's sort

0:31:25of like a lot. It's sort of what made me like, okay, I'll publish it, I'll commemorate this

0:31:30milestone. But then you think about Stephen King's productivity, if he gets 2,000 a day,

0:31:36that's only 1,000 days. Like three, that's under three years. But I just look at my own bookshelf

0:31:44full of Stephen King novels, and I don't have all of them. And there's only one Stephen King, productivity wise.

0:31:51Well, look, he's special. I mean, obviously, he has an incredible talent that, and a genius for

0:31:59doing what he does. And so I don't seek to compare myself to him. How could I? Having written one,

0:32:08let's see, it turned out to be 80,000 words in the final, or in this version, I think it even

0:32:16got edited down something like 77,000 words in the final book is what I recall. I actually have

0:32:22this spreadsheet here. And yeah, probably about two out of every three days, I got to a thousand words.

0:32:29And so, you know, any aspiring writers out there, if you wanted to, you know, write a book of the

0:32:33magnitude of creative selection, you can do a thousand words a day, you could have it in three months.

0:32:39I mean, so it's just, it's all, you know, kind of the numbers game is one thing,

0:32:46but you know, kind of figuring out what you want to say is another. I mean, so do you find

0:32:52the writing process easy? I mean, what do you, you know, you say that you had this

0:32:59this burning desire to, well, I don't want to put words in your mouth. You said you had this,

0:33:03this idea in your mind that you wanted to write this origin of iPhone story. It's like, well,

0:33:13you know, how do you, how do you go about putting something together when you don't have all of the

0:33:18information right in front of you? Well, this was it. I don't want to talk too much. I want

0:33:23to talk about your stuff. Not me, but it does, it intertwines, obviously the creation of the iPhone,

0:33:30obviously intertwines with your stuff very much. Just so anybody who is not familiar with your

0:33:35work, your role on the original iPhone is you were the directly responsible individual,

0:33:41the that's the term right inside Apple, DRI? DRI, yeah. For the keyboard. And we can get to

0:33:49a little bit of that story. You tell the whole story here, but it, you know, long story short,

0:33:53very fair to say the, you created the original iPhone software keyboard. And so obviously,

0:34:00and you were, well, you joined obviously to, you know, you joined Scott Forstall's iOS software team

0:34:07early because, you know, the keyboard was there when the iPhone was announced. So you were there

0:34:14from very early stages. I probably should have, if I were a better host, probably would have

0:34:18introduced you with a bit of a biography for people who aren't familiar. But I also,

0:34:23I want to assume that people are pretty familiar with you by this point.

0:34:26Basically my burning desire for this came out of, well, it's long nagged me that I never put the

0:34:35whole story together. You know, Apple's people famously, because it's a prerequisite to work

0:34:41there. You keep your mouth shut on what you're working on when you're working there. It's a

0:34:45tight-lipped company, secret, whatever you, whatever adjectives you want to apply. And then

0:34:50as time goes on and people leave, they can be freer or feel freer to talk about what happened.

0:34:56And nobody's going to be too sensitive about, you know, stuff that happened 15 or 20 years ago.

0:35:01Andy Hertzfeld, legendary engineer on the original Macintosh team, put together a great website

0:35:09called folklore.org, collecting stories of the creation of the original Macintosh. And then that

0:35:16got collected into a terrific book, which, you know, based on the website called Revolution in

0:35:22the Valley, which is just a terrific book. I have the book in my hand right now. I keep it right by

0:35:27my desk. It's marvelous. You know, and he, again, what a memory he had. I mean, it's just unbelievable

0:35:35how much stuff. And that's, you know, obviously, you know, that was a time when a lot of the

0:35:41digital artifacts didn't survive. There wasn't really email at the time, right? Like 1982,

0:35:46working at Apple on the prototypes for the Macintosh. There wasn't like email you could

0:35:51save. There weren't text messages. A lot of the stuff he had was like, you know, printouts of

0:35:56paper and graph paper and stuff like that. But by the time it came out, it wasn't spoiling anything.

0:36:01It was, you know, the classic Mac OS, I think. I forget if it was even still alive or if it was,

0:36:06you know, by that time. But, you know, you can do that.

0:36:09- Yeah, just looking at the copyright of Revolution in the Valley was,

0:36:13oh, Andy signed this one for me. That's very nice.

0:36:15- Well, we, but... - 2005.

0:36:17- So, yeah, the classic was already even dead. And not that it would have mattered if he had

0:36:22published it five years earlier. Nobody was thinking it was secret what happened in 1983

0:36:27or 1984 by that time. And now that the original iPhone is in our rearview mirror, we've had drips

0:36:35and drabs and things like your book and interviews with participants and stories that have leaked.

0:36:41And we on the outside know much more about how it happened than certainly the day that Steve Jobs

0:36:49held it up on stage when it seemed, you know, like almost a technical marvel, you know, almost

0:36:54too good to be true, both on the hardware and software side. Is this real? Is this really

0:36:59happening? We know so much more about it. But what's always nagged me is that so much of it

0:37:05is vague or conflicting, like what happened in 2006, what happened in 2005. And I'm not saying

0:37:13that my one 2000, 3000 word article put it all together. There's still so much more to dig there.

0:37:20There were iPod projects going on. There were pure research into multi touch projects going on

0:37:29with Boz. What's his last name? Boz Orting. Yeah, Boz Orting. And I know Greg Christie,

0:37:36whom I've met a few times, you know, was worked with with Boz on some of those ideas, as just like,

0:37:41hey, is this multi touch something we can use for anything? And we know that there were ideas that

0:37:46they would build a tablet first, and then it's like, no, let's build a phone. And then it's like,

0:37:50well, wait, should we use the multi touch stuff with the phone? We know all these things,

0:37:53drips and drabs. But that that stupid little Facebook story to his eye, I credit him,

0:38:01you know, it actually motivated me was Tony Fadal tweeting about it, like the day later. And,

0:38:08and I guess I, he said in a tweet that he tried to reach out to me about correcting the description

0:38:14of him being responsible or spearheading the Linux OS part. And I think it's a sensitive thing for

0:38:21him. But I didn't want to just take his word for it. And Oh, Tony Fadal says, it's not true. Well,

0:38:25then I should just publish a correction say it's not true. But I thought, you know what I this has

0:38:29been bothering me for years. Let me try to dig into this. Let me get something off my chest. And

0:38:35I started collecting talking to a few people. A few other people like noticed Fidel's tweet and

0:38:42sent me a few comments, people, a couple of people who still work at Apple. So I can't mention them,

0:38:47but who've been there long enough. Lots of people have been at Apple a long time. It's sort of one

0:38:51of the secret sauces at Apple, you know, that there's a long institutional memory. And I just

0:38:58thought, let me just see what I can collect and start putting it into an outline and collect some

0:39:02stuff. And it like time went on and I wanted to correct it quickly, because I felt like what I

0:39:10and it always bothers me when something I actually put on daring fireball is wrong. And I often say,

0:39:14my goal is to be right, always and have everything I write be tracked. I know I'm going to make

0:39:19mistakes. And so what I try to do is make as few mistakes as possible, but be open to the fact that

0:39:25I might be making a mistake anytime, recognize it, and correct it. And it bothered me that those

0:39:31posts I put up in January and you tweeted about them too. But there was if you just took them at

0:39:37face value, it was misleading about Fidel's role and misleading in terms of the scope of the bake

0:39:44off between these two OSS. Facebook's was clearly a years long thing with hundreds of employees

0:39:50working on the one they ended up abandoning. Whereas the bake off period at Apple was very

0:39:55short. I knew that I knew that. And yet I still published it just as a huh, that's a previous

0:40:02OS bake off story for a secret project that was coming up. And that's good enough. And then I just

0:40:07had all these notes. I had all these notes, a bunch of good sources, some of them public,

0:40:11like your tweets, some of them private. And I thought, how do I organize this together? I just

0:40:17felt like I just had like a shoebox of slips of paper. It's like, what do I do? And the stupid

0:40:23idea that hit me, the obvious idea that hit me. And I think you'll sympathize with this, where in

0:40:28hindsight, once you have it, Oh, how did we not think of this all along? You can't remember not

0:40:33having it, but I thought the whole thing should hinge upon putting together a timeline. And

0:40:37that's the middle of the article I posted last night is just here as best as I can figure is

0:40:43a timeline of certain events along the way, starting in like 2004 with the agreement to do

0:40:49the rocker phone with Motorola to 2005. And my favorite, and you, I was so glad to see you tweet

0:40:58it 2006 colon hard work. It really did. John, you nailed it. You really did. You weren't there,

0:41:10but, uh, you, you, you were able to divine what 2006 was all about. Right. Sure. But it does seem

0:41:17like that as a rough timeline, 2004 is this timeline where, and maybe all along it's in

0:41:24the 2000s, some somebody at Apple is thinking we should make a cell phone because cell phone is a

0:41:29computer type thing. The iPod in 2001, obviously showed that Apple can make handheld things that

0:41:35are actually extremely compelling. There's this pressure, which was obviously true that is circa

0:41:432004. Okay. The iPod is exploding in popularity, which is good. And the part of that hand in hand

0:41:51is the iTunes music store is exploding in popularity. That's from Apple's perspective,

0:41:56very good. And from a consumer perspective, I think it's turned out to be good. It was the

0:42:00first step towards making digital music without any sort of physical media, a business, as opposed

0:42:07to just something you've pirated over the internet. Right. But by 2004 cell phones were getting good

0:42:15enough that, you know, and I think, I don't think I quoted in my article, but in one of the books

0:42:20and I, you know, again, like a conspiracy theorist, for the last five weeks, I've had like six books

0:42:26each of them with eight bookmarks in it at the points that are relevant to what I was trying to

0:42:31put together. At one point though, Eddie Q spoke to someone, I think it was in the Becoming Steve

0:42:36Jobs book, but just said simply, look, it was obvious, you know, why carry two things in your

0:42:40pocket? Everybody at Apple, even people at Apple had an iPod in one pocket and a cell phone in the

0:42:45other. And if they were only going to get rid of one, it seems like they're probably going to get

0:42:49rid of the iPod if the, cause the iPod wasn't making phone calls, but the phone could play music.

0:42:54And so what are we going to do? Steve Jobs felt like Apple couldn't do Apple phone, the Apple

0:43:01way where Apple made the decisions and said, this is what we want to make. Here it is. It's finished

0:43:06ready for the world because cell phones all had to go through, as he called them the orifices,

0:43:10the carriers and the carriers notoriously dictated all sorts of nonsense to every single company that

0:43:17made phones at the time. You know, Nokia, Ericsson, Sony, whoever else was making popular phone,

0:43:23Blackberry at the time, everything had to be approved through the carriers. Apple didn't want

0:43:28to do that. Steve Jobs didn't want to do that. So, okay, fine. We'll let Motorola make a phone

0:43:32and we'll work with them to get iTunes working on it. And it turned out almost famously bad.

0:43:39I mean, the rocker is just famously bad. It's not a good phone. It seemed bad at the time.

0:43:45I, it was one of those things I revisited. I remember describing it like when the demo

0:43:50failed at the introduction and it was like Steve Jobs wanted to demonstrate that you'd be,

0:43:55if you played music and you got a phone call, it would like duck out the music and you'd take the

0:44:02phone call. And then when you're in the phone call, the music would resume and the music didn't

0:44:07resume. And I just remember writing that it seemed like he almost wanted to just throw the damn phone

0:44:13on the ground and onstage in front of everybody and say, ah, forget it. You know what? We're

0:44:16building our own phones. Stay tuned. But he didn't, he, you know, he was a pro and he stuck with it.

0:44:22But then I rewatched the video this week and I was like, nope. He, he thought about throwing that

0:44:26phone on the ground. He really was. He really did. Yeah. He broke character. Right. He really.

0:44:31Yeah. Yeah, for sure. It, it, for sure. It's interesting because you wonder what's going on

0:44:39in that moment. It's like, when did he decide that, okay, we're, we're actually doing this

0:44:44thing ourselves and you, it, you can almost, you can almost see the wheels turning in his mind.

0:44:50It's like, it's right, right now. Right. That's, this is it. You know, we just need to do better

0:44:56ourselves. And you know, it, it, you know, the, the iPod is, is all gave, I think I gave Apple

0:45:07the confidence that the company could do it at that. You know, you kind of, you kind of look at,

0:45:13um, you know, so much of what happened at Apple happened because of the talent that,

0:45:20that the company could attract, that there were these amazing designers and these highly skillful

0:45:27engineers and these excellent marketers and, you know, all of the lawyers and then the supply chain

0:45:33and the operations and everything like that goes into making a great product. But really,

0:45:40you know, what, what did Steve add? And, uh, you know, I think it's, you know, maybe clear and

0:45:46obvious to say, but I think still worth saying that he provided the vision. He provided that

0:45:51we're going to go and do that, that that's the product that we're going to make. And to just

0:45:56Marshall all those resources and point the point everybody in the same direction and give them a

0:46:02clear idea of what they wanted to do or what he wanted everybody to do. And, uh, you know, I,

0:46:10I think one of the great things, you know, going back and looking at, you know, you say,

0:46:14you mentioned looking at old videos, going back and looking at Steve say, when he was at the all

0:46:20things digital conferences with the Walt Mossberg and Kara Swisher up on stage over many years,

0:46:27he'll very often use the phrase making great products. What does Apple do? Well,

0:46:32we make great products. They ask him, what do you do in the morning? Well, I have a team of people

0:46:36get together and we figure out how to make great products. That's what he cared about.

0:46:40And so that's what he brought to the company. That's the momentum that he brought to the overall

0:46:47effort. So that then people like me, you know, eventually, you know, there's a problem like

0:46:52making a software keyboard for this new phone that we're going to make that, you know, it was just

0:46:56very, very clear to me that that's my piece in the puzzle. And so I just set about trying to actually

0:47:02deliver it so that there could be a whole product. And that, you know, that Steve was like gathering

0:47:08up all of these pieces and, you know, and figuring out, Oh, what the jigsaw looked like and, and how

0:47:16all of these pieces would come together and what the final picture would look like. And of course,

0:47:21one of the major things that he did as well was, you know, sometimes you wind up with a beautiful

0:47:26piece that's, you know, excellent and marvelous all by itself, but it doesn't fit into the puzzle.

0:47:34And so he had this, this intuition about, you know, what would be the pieces to keep and how

0:47:43should they be arranged so that the final picture would be, would be wonderful. And so in a way,

0:47:50you know, you think of, think about, you know, what was Steve's job is it's like, he was like

0:47:53an editor. He was just a great editor of of, of everybody's work. He'd give out the story

0:48:00assignments and then the work would come back and he would figure out, well, okay, well, how do we

0:48:04make a you know like either a magazine or a newspaper, you know, edition out of it. And he was

0:48:13an absolute genius at it. I always think of him as, as being analogous, his role being analogous

0:48:19to a film director in terms of the film director doesn't have to put their hands on the camera,

0:48:26didn't write the script, doesn't show up as an actor on camera, doesn't build the sets,

0:48:34may not even edit the film. There's an editor who edits the film after it's been shot, but is there

0:48:42every step of the way to say, this is what I want it to be like, or this isn't good enough,

0:48:46or that's great. That's, that's an amazing idea, but what if, yeah, I've always thought that,

0:48:52but let's, let's take a break. And then I want to ask you about how you got started on the iPhone

0:48:57team, because it's one of my favorite parts of the book, but let me tell you right now about our next

0:49:01sponsor. It is our good friends at Retool. Internal tools like dashboards, admin panels, custom crud

0:49:10apps, CRUD can dramatically speed up how your business operates, but building them from scratch

0:49:17and maintaining them over in time involves a lot of tedious work. Retool helps developers build

0:49:24these internal tools much faster. Retool offers a complete UI library with over 80 fully featured

0:49:32accessible components that you can drag and drop into any interface. And from there, you can connect

0:49:37your interface to any source, any data source, like a database, customize anything with JavaScript

0:49:44and deploy your apps all within Retool with app environment permissions, SSO, and other time

0:49:51saving features available out of the box. The result, you can build production grade business

0:49:57apps without Googling for component libraries, debugging dependencies, or rewinding, rewriting

0:50:03boilerplate code. Thousands of teams at companies like Amazon, DoorDash, Volvo, and Brex collaborate

0:50:12around custom built Retool apps that solve internal workflows. I've checked this out. They

0:50:19sponsored Daring Fireball a couple months ago. It is really, really, I love it. It's so good that

0:50:25it makes me want to use it to build something. I'm not saying, I know people throw around the

0:50:31sort of a hypercard for the modern age a lot and it don't get into specifics. It's not supposed to

0:50:36be a clone of hypercard, but it has that same sort of, Oh, you just drag things out and click

0:50:43on the thing you want to, Oh, here's the button, add the code that the button makes happen. When

0:50:48you click the button right there by clicking on the button, the sort of right combination of

0:50:53WYSIWYG visualness for dragging out the forms and connecting the visual parts to the code that you

0:50:59want to write. And then you just hit a button and then there it is, and it's just running and it

0:51:04works. And you're like, huh, I have an app. Really, really cool stuff. Great. It looks great. They're

0:51:11moving very fast. They've already added so much stuff just since the time they sponsored Daring

0:51:15Fireball a couple of months ago. Go to retool, R E T O O L dot com to find out more. That's retool

0:51:24dot com to find out more. One of my favorite parts of your book, Ken is, is that you almost didn't

0:51:31work on the iPhone. It sounds to me like, so long story short, when did you, when did you start at

0:51:37Apple around 2001? In June, I was on my birthday of June in June of 2001. All right. So June, 2001

0:51:48Mac OS X is brand new. And the first thing, the first project you worked on at Apple was what

0:51:56became known as Safari or WebKit. I mean, I guess before you'd even, there was a difference between

0:52:02Safari and WebKit. Which one would you actually, so yeah, so when I joined, I joined the same day

0:52:10as Don Melton and he and I had worked at a company called Easel, which interestingly was founded by

0:52:21Andy Hertzfeld, the fellow who did folklore.org. That's how I got him to sign the copy of the book

0:52:28that I have on my desk here that Andy of course was one of the instrumental developers in the

0:52:36original Mac OS in, in the eighties. And so, you know, Easel unfortunately didn't succeed,

0:52:44but it had gathered up this amazing set of talented people. And one of the other

0:52:52top executives at Easel was a fellow named Bud Tribble who went off with Steve Jobs when Steve

0:53:00left Apple or was ousted from Apple. However you want to characterize that in 1985 to found Next.

0:53:08And so Bud was our VP of engineering at Easel. And when it was clear that Easel didn't have a history

0:53:16anymore, he I pretty sure he just got on the phone and called Steve and said, Hey, we've got all of

0:53:23these wonderful engineers. Maybe you want to hire some. So Apple actually held a job fair for Easel.

0:53:31On the infinite loop campus. So, uh, I mean, it was really like, uh, you know, like, uh,

0:53:36like we were a high school and, uh, up on the fourth floor, which, uh, of infinite loop two,

0:53:42which at that time was a game room. It was a pool table and a couple of the old, uh, coin operated

0:53:47arcade machines. Uh, yeah, there was a bunch of hiring managers that, uh, uh, struck up

0:53:53conversations with a whole bunch of us. Uh, and so I was very interested in going to Apple because

0:54:00at that point, uh, Easel was, um, the fourth company that I had worked at in the preceding

0:54:08two years. Now, if you think about, you know, the, the kind of the.com era, there were these

0:54:12startups came and these startups went and you, you know, to me, Apple seemed like a, well,

0:54:19I'd always loved the company. Uh, and it just seemed like, you know, okay, this couldn't be

0:54:23as Mac OS 10 is out and you know, the company of Steve is back and the, the companies probably got

0:54:28a good future ahead of it. And it was actually making money, uh, which was more than you could

0:54:34say for any of these previous startups that I had worked for. So I was really enthusiastic about

0:54:39finding a job somewhere and I'd actually had a good lead on working for the system preferences

0:54:46team. And, uh, you know, before I could, uh, get even get an offer, uh, Don who, uh, again,

0:54:55I had worked with at easel, Don and I were the, uh, two directors of engineering reporting to bud.

0:55:01Uh, Don was doing the client side of our, our effort, which I won't get into. And I was doing

0:55:08the server side, uh, code for our effort, uh, at easel, uh, which was, well, basically it was

0:55:14Linux on the desktop with some online services layered on top and it didn't work. So we were

0:55:20trying to figure out what was, what, what we should do. And so Don pulled me aside and said,

0:55:25um, here, why don't you come and take a, take a ride with me? So we went over to the computer

0:55:30literacy bookshop. So we went to an actual physical brick and mortar bookstore, uh, and he

0:55:36went in and he, uh, you know, he bought a couple books and he came back out and we got in his car

0:55:42and he put down the O'Reilly rhino, uh, JavaScript book, right? JavaScript definitive guide,

0:55:50right, right. So he put that book down on the console in between the, the two, uh,

0:55:56seats in the front of his car. Uh, and he said, uh, Ken, you want to make a web browser?

0:56:02And it was like, uh, uh, uh, uh, sure. What did it sound completely crazy? Uh, but he said, yeah,

0:56:10uh, he was talking to, uh, Scott for stall and Scott with forestall, wanted to bring him on,

0:56:15start a new project. He was going to make Don the manager and Don in that moment offered, uh, to,

0:56:21uh, uh, uh, you know, me an opportunity to be his team. So, uh, he and I then, uh, just a couple

0:56:29of weeks later, uh, in June of 2001 started and, uh, the job was to make a web browser.

0:56:36He was the manager and I was his team to two people. And the idea at the time,

0:56:43basically, why make a web browser? Why should Apple make their own? There was internet explorer.

0:56:48There were, there was a Mozilla. There were fire or I guess Firefox wasn't named Firefox yet, but

0:56:56you know, there were other browsers. You could run them on the Mac. Uh, two things. I think if you're

0:57:03picky about the details, it was absolutely true that none of the browsers on Mac OS 10 felt native

0:57:11to Mac OS 10 and, you know, just little things like it with internet explorer, there were issues

0:57:18that it was ported from classic Mac OS to Mac OS 10 and had, you know, text rendering didn't quite

0:57:26look right on the Mac OS 10 side. And I know that's in some ways that sounds like such a silly

0:57:31little thing. Like, well, just render the text differently. But in that, those, those, uh,

0:57:37those transitional years, it, it really made a difference. And if you, and because screens had

0:57:44so many fewer pixels per inch at the time, the difference was, you know, very noticeable. You

0:57:49didn't really have to be a super picky font snob to say, oh, the text doesn't look as good, but,

0:57:55you know, the way the buttons look and things work, it, it, and it was never going to be,

0:58:00nobody was going to make a true great Mac browser unless Apple did it themselves. And then I think

0:58:07the other reason is that just web browsers were obviously so important, right? There's all sorts

0:58:13of other things that maybe there's not a great blank for the Mac. And you could say, well,

0:58:19but it's not that important, right? It's not so important that there's, you know, and fill in your

0:58:24product category here. Web browser didn't, you know, seemed like it was, you know, to put it in

0:58:31the Tim Cook terms, an essential technology that Apple should control, you know, that it was too

0:58:36important not to have their own. Right. And, and, and, and so one of the other things that, you know,

0:58:44you, you, you know, we're introducing this, this, this topic, you know, talking about both Safari

0:58:51and web kit. Well, I can tell you that from day one, both of those were absolutely essential

0:58:56that a part of our charge was to make a web browser, but that also we needed to make a web

0:59:04framework that you could use to make a web browser because man, I think it's really one of the

0:59:09underappreciated aspects of Apple's long-term success in the, you know, the, the Steve Jobs,

0:59:162.0, you know, you know, Steve returning to Apple, you know, starting from that date in the late

0:59:23nineties, all the way through to today is the success of Apple's software frameworks, giving

0:59:32not only third-party developers, but just as importantly, the internal first-party developers,

0:59:38these great software development tools to make great apps. And so the goal was that we needed to

0:59:49deliver a framework that we could give out to third-party developers to make great web app,

0:59:58web apps of their own. And they're not really web apps, but technologies that deeply integrated the

1:00:04web into the overall experience, right? Just to be very clear about that. So it, it, it, it was a part

1:00:12of the job right from the start to do both Safari and WebKit, but of course we didn't have those

1:00:17names. I mean, we really didn't have anything. We, we didn't know from day one, whether we were

1:00:23going to build something ourselves, whether, you know, I didn't know Don and I used to joke that we

1:00:28sit down, you know, we would get a terminal and we go VI web browser dot C and we just start typing,

1:00:34you know, the code to write a web browser. I mean, that was kind of the, the joke. Do we do that?

1:00:38You know, to buy or do we to build, or do we buy something from you know, some existing

1:00:46web browser vendor and bring that code in house and try to customize it? Or do we go and try to

1:00:54latch on to some open source that was available and begin our work by customizing that and, you

1:01:04know, to make a very long story short, what, you know, what we, you know, wound up, we wound up

1:01:08looking at Mozilla, we wound up looking at opera and we eventually fixed on the work the web

1:01:18browsing frameworks, K HTML and KJS from the KTE desktop environment on Linux. And we found that,

1:01:27it was, you know, pretty easy to work with. And it's actually is a one more digression is that

1:01:34this was a difficult thing for Don and I to, to, to, to decide on. We were actually really

1:01:42looking back quite indecisive about it. And we had going on, been going on for about six

1:01:48weeks saying, well, do we build, do we buy, do we do open source, do this investigation in this

1:01:53framework or that? And right around that time, we were saying, well, this is gonna be a pretty

1:01:58big job to make a web browser and a web framework. So we need to hire some people. And so we hired

1:02:05this fellow, Richard Williamson and Richard came on and he again, about six weeks into the effort

1:02:13and we didn't really have very much to show for what we, you know, that, that time between when

1:02:21Don and I started and when Richard started. And so Richard wanted, you know, kind of,

1:02:26we wanted to give him an update on what we were doing and he was interested to hear about our

1:02:29progress. And he was like, really not impressed at all. He kind of, he liked the idea of making a web

1:02:36browser seem like a big project, something worth doing, but he was completely unimpressed. So he

1:02:41went off by himself for like two days and we're gonna, Don and I were kind of looking at each

1:02:46other. It's like, well, Richard seems busy. I don't know. He seemed to, you know, maybe,

1:02:49you know, he's going to come up with something and he did most really quite remarkably. He had

1:02:54taken this KDE code from Linux and just absolutely jammed it onto the Mac, got X windows running on

1:03:03the Mac, took this Linux code, got it compiling on Mac OS 10 and brought the browser up under

1:03:13X windows on the Mac in like two days. And he called us into his office to give the,

1:03:20give us a demo of the thing. And he just starts browsing the web on, on, it was incredible.

1:03:27It was absolutely, absolutely one of the most awesome displays of just jam tied to hackery,

1:03:36chicken wire and duct tape to get something that provided us with a vision of the future.

1:03:43It was really just an absolutely remarkable piece of work. And that just the next day I went, we,

1:03:48I went home from that and you know, it came in the next day and stood up a Linux box and downloaded

1:03:54Katie and really did started doing some analysis to figure out what code, what, what files do we

1:04:00actually need to bring over from Katie and, and K K HTML and KJ KJS to, to get our project starting

1:04:12in earnest. So if you go and look, I mean, you can on track.webkit.org, I mean, it's a web kit,

1:04:18it's an open source project. You can go back and look in some of the first, you know, the first

1:04:22commit is mine of just a couple of files from from the KDE project. And we started on that.

1:04:32And you know, that development still proceeds more than, you know, 20, 20 years, you know,

1:04:4020 years on. It's no longer a fresh transition from K HTML to webkit. It's no, no, no, it has

1:04:49really had a whole life of its own. Now this story is told in great, in great detail in the book.

1:04:55But, but one of the things I read, that's one of the parts I reread. And one of the parts that

1:04:58really struck me is at that point, it's three of you, it's Don Melton, you, and now Richard

1:05:06Williamson. It's three people who are still like, just sort of, you know, and you do have a firm

1:05:11mission. The mission is pretty clear. You're going to build a great Mac web browser with a great

1:05:16engine that could be kitified in Apple's terms, right? And so then, you know, I think about the

1:05:23ways that Apple has used WebKit, not just Safari, but WebKit since. There was dashboard for a couple

1:05:29of years where the components were all built in WebKit. There are little parts, you know,

1:05:33like the help system could now be written, you know, now use WebKit as the rendering engine for

1:05:38help information. Parts of iTunes could be rendered as HTML. And, you know, Apple News today

1:05:46is, it's all over the place, which doesn't even get to the point that by the time you got to make

1:05:52a phone, now you have your own engine. And obviously, an engine needed to be customized

1:05:58greatly to run on a three and a half inch diagonal touchscreen with pinch zoom and all these other

1:06:04things, you know, even putting that part of the serendipity of having a great extensible

1:06:13componentized framework that could do it, you know, it obviously made sense. But at that point,

1:06:19it's just three of you. You and Don are mostly thinking, well, how can we shoehorn the Mozilla

1:06:25project into something that we can build on? And, you know, maybe if Richard Williamson hadn't been

1:06:33available, or if he hadn't taken the job, or you hadn't decided to hire him, or somebody else had

1:06:37been employee three, maybe WebKit is totally different today. You know, it's entirely possible.

1:06:43Trenton Larkin Yeah, we might have failed.

1:06:44Dave

1:06:53But failure was an option in this case where Apple had web browsers, right. And when Safari debuted,

1:07:00it was a surprise announcement. It wasn't like, you know, it wasn't completely obvious that Apple

1:07:06needed absolutely positively needed its own browser, it was well, it would be nice,

1:07:13it would be nicer to have their own web browser that rather than rely on Internet Explorer and

1:07:17these other options that people have that are mostly built on cross platform code bases,

1:07:22and therefore don't embrace the Mac. And, you know, maybe it can't be componentized easily.

1:07:26That was the whole problem. Again, long story short, that was the whole problem with Mozilla,

1:07:30was that it really was, it was sort of the opposite of the framework mentality. It was just

1:07:35this gigantic monolithic code base that they built to sort of abstract out all the details,

1:07:42because they wanted it to be cross platform, right, by wanting Mozilla to run anywhere,

1:07:46they sort of built effectively their own operating system at a conceptual level that everything ran

1:07:52on. And it was therefore hard to just pick out the, well, we just want the rendering part,

1:07:56you know, we just want the JavaScript engine. And it was like, no, you kind of got to take

1:08:00this whole thing. Right. Anyway, the WebKit thing turned out pretty well.

1:08:05You know, I just was looking at something came across my feed, I know it was Twitter somewhere,

1:08:15the latest web browser statistics. And so I went and looked and basically everybody uses WebKit to

1:08:23surf the web these days, whether it's in Safari, either on the Mac or in iOS, or in the fork of

1:08:32WebKit that happened some years ago, that now powers Chrome. Right. So the entire web, I mean,

1:08:38it's, it really is remarkable to think that it was just these three, you know, guys who didn't

1:08:43know anything about the web. Well, it's actually to be fair, Don was the one who did because he

1:08:48actually had worked at Netscape. So before easel. So it's one guy who knew about the web, two guys

1:08:54who didn't, and we're learning about it as quickly as we could. And that, you know, some help for

1:09:00some smart people who did some good work in the open source world. Yeah, now, in the fullness of

1:09:07time, you know, things have completely changed. I hate to say it, but I think it was me who linked

1:09:12to the thing about the web browsing statistics, but going by those stats. Oh, we did. But going

1:09:18by that. That is a way I would have seen it. It is true, but the path from KHTML to WebKit,

1:09:24and then for years, the first few years of Chrome, it was, they were just using WebKit. Then, you

1:09:30know, opinions divided on, you know, where it should go. So Google forked it and they have,

1:09:36I think they call it Blink or Chromium, whatever you want to call their version. But it clearly,

1:09:40it was a fork from WebKit. So the family tree is clear. And as the years have gone by, I think the

1:09:47only one left that's not derived from WebKit is the Mozilla engine in Firefox, which is still has

1:09:54like nine or let's give them 10%. Let's round up to be generous. 10% of desktop browsing,

1:10:00but mobile browsing is a majority of browsing. And so overall browsing usage, you know, it's got to

1:10:07be something like 96 or 97% WebKit or Chrome, which is derived from WebKit, including, you know,

1:10:15Microsoft's own browser edge, which is the most, that's the part that would seem bananas. I think

1:10:20if time-traveling John Gruber went back and met with Don Melton, Ken Kishenda, and Richard

1:10:26Williamson while you guys were noodling over his demo, two-day demo of getting Conquerer to run on

1:10:34the Mac. And I said, by the way, 20 years from now, 97% of all web browsing on all computing

1:10:40platforms, including those that haven't been, you haven't been invented yet, will be using the

1:10:45derivation of your work right here. And you would have said what?

1:10:47Yeah, it's pretty crazy because actually, you know, I write about it in the book about the

1:10:56effort to make a Safari and WebKit fast. We used, I had a windows machine in my office and re we ran

1:11:05IE on windows as the benchmark for how fast we needed to be. And in the beginning of the project,

1:11:15it was absolutely comical. We were three, four, five times slower than windows than IE on windows.

1:11:26As a matter of fact, it is really quite annoyingly. I had this, this obnoxious click sound

1:11:34when it would load, you know, go like go off and I'd probably begin fetching the URL.

1:11:40And so it would just go click, click, click, click, click. Cause we, it just was, it's like,

1:11:49how are we ever going to be that fast when I, you know, when ours was, was just going, uh, the three

1:11:57took three times as long or more to get through the thing. And, you know, it really, I have to

1:12:02give Don Melton just a huge amount of credit for saying, you know, it's almost like, you know,

1:12:07like a Zen master. He said the way we're going to make the web browser faster is by never making

1:12:12it slower. Right. He just absolutely refused to accept any check-ins into our code base. And then

1:12:19as the team grew, eventually we had probably about eight or nine or maybe even 10 people on the

1:12:25project by timely shift. A huge, huge team can just absolutely enormous, enormous Silicon Valley,

1:12:32team of almost, almost a dozen people. Almost for it to do a web browser. Well,

1:12:41what are you going to do? But that's it. I love that story from Don. I don't want to spend too

1:12:44much time on it, but to restate it, the basic rule instituted by Don Melton was anytime an engineer

1:12:51wanted to check in code for a new feature or an updated feature, you had to run your page load

1:12:57test. I think it was, you called it and it's just loading real world web pages from real sites that

1:13:03people actually use that were popular. And Safari had to be as fast or faster than it was, you know,

1:13:10preferably faster, but not slower. And if it was slower, then back to the drawing board,

1:13:15see what you can do in your code to make sure that when you do check this feature in,

1:13:19it always gets faster. And it sounds, I think people out there who don't program and certainly

1:13:23haven't been involved in larger software projects that you might think, well, that must be the norm

1:13:29everywhere, but the real norm everywhere is we'll fix it later. Right? Like, yep. Like we,

1:13:35we were told we've got to get support for blank in here. You know, like let's say it's a new CSS spec,

1:13:42right? CSS 1.1 came out. We only support 1.0. There's these things we need to do. We've checked

1:13:48them in. Ah, but look, when we use these CSS 1.1 things, it's 10% slower rendering yahoo.com and

1:13:56then New York times.com. We'll fix it later. Okay, let's go. Cause we've got these other things on

1:14:01our list. We've also got to support this other new thing and new technology. And we, you know,

1:14:06we've always been meaning to make printing better, keep going. And then those we'll fix it later is

1:14:10pile up and next thing you know, it's slow. Yeah. Yeah, it's absolutely true. And you know,

1:14:15there were, and Don just simply refused to have it be the way that we worked. I, I, I remember

1:14:23there was one time that I was working on some big feature. I actually don't remember the feature,

1:14:28but I do remember the phone call that I got on like the Friday evening that, Hey, I finished

1:14:33the work. And as I check it in, no, naturally, you know, another programmer joke, you know, you,

1:14:37you make a big check in and then you go home for the weekend. The you know, he gave me a call

1:14:44and said, Ken, I checked out your code and I ran the page load test and slower. It's got to come

1:14:48back out. And it's like, Don, you always, what do you, what do you mean? I mean, it's just like

1:14:52huge amount of work and it's all these new features. And he says, I don't care. And it was

1:14:57absolutely the right thing to do. And, and you would, you would think, you know, if you are,

1:15:02you know, a developer or maybe you're just thinking this through logically, well, how can

1:15:06you make the software do more add features and yet still have it be faster than it was without

1:15:15those features there. Like your, your mention of like CSS one.one, it's actually doing more to

1:15:23implement a more complex, complicated version of a spec. And the trick was, you know, that,

1:15:31that the code base was sufficiently large and sufficiently not or insufficiently understood by

1:15:40us that there was always an opportunity to go into some new area, understand it a little bit,

1:15:45optimize it a little bit and offset the, the, the, the cost of adding the new features

1:15:53in subsystem a with optimizations in subsystem B. And as long as the browser was faster,

1:16:03that was okay as fast or equal, then it was okay. We could proceed. And so it was just a

1:16:09matter of matter of kind of sometimes shuffling around these, these, these chips around the, the,

1:16:16the table and trying to think of, you know, like new and interesting ways that we could either

1:16:20optimize here or there, or it's sometimes gathering up little optimizations to, you know,

1:16:26to offset things. And we didn't really game the system either. You think that we could, you know,

1:16:30it's like save an optimization for when we needed it. And then we just very honestly and

1:16:34straightforwardly tried to do the best job adding features and never letting the thing get slower.

1:16:41And, you know, and, and crazy, you know, crazy enough, it worked.

1:16:44That would be that that would be dastardly if you like, you had part of the code in your purview

1:16:50and, and, and you had an optimization, but you, it was like, Ooh, but then if I do something else

1:16:56and it makes it slower, I'll check in my optimization for this other thing that I've had

1:17:00in my pocket. And then the whole thing feels faster. It's, you know, it just is, it's like,

1:17:06I'm an absolutely like horrid liar and I get, I get, you know, such like childlike enthusiasm.

1:17:12If I had actually discovered an excellent optimization, there's absolutely no way I

1:17:17would have been able to keep it to myself. And so, you know, it just was the, it was the culture,

1:17:22it was a good positive culture. And so, you know, and, and put that together with a plan and a clear

1:17:28goal and there you go. We're watching the, my wife and I are watching the show, Pam and Tommy on Hulu,

1:17:35which is about the Pamela Anderson, Tommy Lee, both their marriage personally, which is more,

1:17:42you know, I was around at the time, but the famous sex tape that came out and was sold over the web.

1:17:48And so, and you know, these, these scenes take place in 1996 of, of the people who stole this

1:17:54tape from them selling copies of, because you couldn't watch tape, you couldn't watch

1:18:00video on the web at the time, or if you did, it wasn't really, it wasn't even VHS quality. It was

1:18:05so, you know, tiny. So, the way to sell, the way to put a sex tape out in 1996 was to actually sell

1:18:11VHS copies of the tape, but to do it on the web, you'd send them a check and then they'd mail you

1:18:17a tape. But the thing that they, you know, I pay attention to stuff, everybody listening to the

1:18:25show pays attention to stuff like this. The thing they get right is how slow the web was at the time

1:18:32and they don't cheat. And it's like, you're watching these pages load over modems. And it's

1:18:37like everybody who went through this modem era knows, oh my God, it was so incredibly slow.

1:18:43And people would just make their web pages as tiny as they could be. And we'd compress, you know,

1:18:48use whatever tools we could to shrink a GIF from 15 kilobytes to 13 kilobytes. That was a win.

1:18:54And it still was so terribly slow. And I remember having a job interview coming out of college

1:18:58and, and, and they had a T1 line. And it was the first...

1:19:02Trenton Larkin Oh, wow.

1:19:03John Green Oh, I mean, we had some,

1:19:05some computers at Drexel University where we had that, but for the most part, when I was in the,

1:19:10like the comp sci lab, it was at like a Unix terminal, you know, and I'm just staring at

1:19:16a command prompt. I wasn't browsing the web. And it was like, oh my God, this is so fast.

1:19:21But then once you got past modem speeds and got, you know, real internet, you, at that time,

1:19:28you suddenly, it didn't take long where this thing that felt because you were no longer tied to this

1:19:34bandwidth of a modem, you're way faster than that bandwidth wise. You realized,

1:19:39rendering the web is extremely slow. It is just, it's just extremely difficult. HTML and what people

1:19:48wanted to build with HTML and JavaScript and what people wanted to build and did build. And the

1:19:54other thing too, is it's like, you can't just say, well, we won't, we won't do that because other,

1:19:58if other web browsers are rendering this popular webpage that was very difficult to render,

1:20:04fine, then you had to too, right? It was competition at work, but it was, it's

1:20:10incredibly, the combination of computers being slow, slow, not bandwidth, not modems, but just

1:20:15the actual CPUs being so slow compared to today and web pages being ever growing in complexity,

1:20:23the speed really mattered. And I remember when Safari was announced that it was, you know,

1:20:28to me, it was more interesting, like, hey, this is, this really is native. I don't, you know,

1:20:32and of course, as Steve Jobs was announcing, we didn't know what the underlying rendering engine

1:20:38was yet. I think it was, you know, like an email to the KHTML team after, you know, which again,

1:20:44I don't want to get into. It was like the KHTML team found out about this after it was announced,

1:20:48which is according to, you know, that that's within the rights of the license, you know,

1:20:53and that's why WebKit was then open source, but it was like, it dropped as a surprise even to them.

1:21:00But it was, to me, it was like, oh my God, it is native. It looks great. I love this interface

1:21:04and it renders text well, and the buttons look like Mac buttons, but it was fast, fast, fast.

1:21:09This is faster than the other browsers. And it was so important. Oh, you know, and again, just,

1:21:15you know, total, um, you know, I, you know, I give, you know, so much credit for Don Melton

1:21:20for figuring out the, the, the way that we were going to deliver on that goal, but it just comes

1:21:25down to Steve. That's what he said. And so he said, this thing has to be fast. And that, and

1:21:31that was that, I mean, there was no real arguing with Steve when he just said very, very clearly

1:21:35what he wanted and just an incredible amount of insight into what, where the web was going. I mean,

1:21:44you know, don't necessarily fit. I mean, Apple is not necessarily known, uh, perhaps with good

1:21:49reason as, as a company that really maybe understands the web or is, you know, uh, uh,

1:21:55internet native, maybe even, uh, you know, it bears so much of its history as being like this

1:22:01single user system that is, you know, people running Photoshop and illustrator and other

1:22:06graphics programs by themselves. Uh, and yet Steve did have this, you know, really, you know,

1:22:13amazing insight into where the future of the web was going, as you just described as people were

1:22:17coming off modems, uh, and we're going to be getting faster internet speeds, that this was

1:22:22something that, uh, he wanted to be a, uh, an important part of the overall, you know,

1:22:29experience of having, uh, you know, then Apple web browsing, um, uh, experience.

1:22:36So Safari ships, webkit ships, it's a hit. It, it takes off on the Mac. It, it's growing,

1:22:42you're working on it for a few years. Um, but then long story short, you, you kind of ended up

1:22:49Peter printer, principal in yourself, right? The Peter principle is the, is the adage that

1:22:54employees in an organization rise to the level of their incompetence. And you think, oh, well,

1:23:01that's, that's, that sounds, well, you think that sounds brutal. That can't be right, but it makes

1:23:05sense. Like if you're really good at your job and you deserve to be promoted in a well-run

1:23:11org organization, that will be recognized and you will get the promotion you deserve.

1:23:16And then eventually you'll get a promotion to a point where you're, you're no longer

1:23:20looking like you need another promotion or deserve another promotion. You've risen to the level of,

1:23:27of your incompetence. Um, and maybe in your case, again, it's not, maybe not even incompetent.

1:23:33It sounds like from your book, it was just, you rose to the level of your dissatisfaction,

1:23:39right? You you'd gone to me. I asked for it too. Right. You asked for a promotion,

1:23:45became a manager and, and very, very quickly just discovered that I didn't like it. Uh, it was,

1:23:54I just missed coming in every day and worrying about the technology, you know, and, and realizing,

1:24:00uh, uh, after the fact, rather than having, you know, sufficient foresight to understand it, uh,

1:24:07you know, before I, I made the commitment that when you're a manager, your job is to worry about

1:24:12your people, you know, and to make sure that they're productive, that, that, Hey, they have

1:24:17what they need so that they can do the, the, the work to make the, make the products. And, uh, I

1:24:24just missed making the technology by mist mist, uh, coming in and having the difficult, interesting

1:24:31technical problems to solve myself. And, um, I, I just, uh, after, you know, maybe two or three

1:24:39months, I realized that it was just absolutely not for me. And, and so I'll just continue to continue

1:24:46with the story is that I just went and told Scott for stall. It's like, Scott, uh, this, uh, I'm

1:24:52miserable and, uh, I want out and he's like, wait a minute. No, he's like, just three months ago,

1:24:58you committed to me that you were going to take this team on and that you were going to get some

1:25:01good things done. Um, and I said, no, I say, well, look, I'm willing to resign over it. I understand

1:25:08that I made this commitment to you and that now I'm reneging and that I'm willing to, um, you

1:25:15know, to, you know, to just leave the company over and I'll go find a job someplace else, but I feel

1:25:20like I let you down and I'm sorry. And he's like, whoa, wait a minute, wait, wait, wait, wait. He

1:25:25was pretty upset with me, but he said, Ken, tell you what, go away. I'm going to work on this and

1:25:32we'll figure it out. And this is around 2000. This is early 2005. I believe this is in it's actually

1:25:41in, um, uh, it's like in July of 2005. Okay. So middle of two, I had made, yeah, I had made the

1:25:49final decision to, uh, you know, to throw myself on the mercy of forestall, uh, over the 4th of

1:25:57July weekend. So famously now this is where it's all coming together. We, you know, as I've

1:26:03pieced together, not that I've I'm like Sherlock Holmes, but you know, that by early 2005 at the

1:26:09highest levels, Apple had decided let's build our own phone and Scott forestall obviously was very,

1:26:15very much, uh, aware of that at the time you had no idea, like, so you're, you're meeting with

1:26:20Scott forestall, uh, and talking about, you know, the three month old promotion you would like to

1:26:28un-promote yourself and do something else. But meanwhile, you know, he's trying to,

1:26:33he recognizes he, you know, you know, he'd like to keep you as a productive, you know, that you're,

1:26:38you're a good team member to have somewhere. Uh, but meanwhile, in his head is the entire iPhone

1:26:46OS project, which was still at like the, this sort of germ, germ stage, like webkit was when it's you

1:26:55and Don Melton and, uh, uh, Williamson, uh, you know, and just like, I don't know, could it be

1:27:02cage TML? Should we build our own thing from scratch? You know, it's, you know, everything is possible, right?

1:27:08And so then, then you get, you get a knock on the door, right? Yeah. So then, uh, the, uh,

1:27:17so then, uh, Henri Lamoureux, who was reporting to Scott said, uh, Ken, come, come over here,

1:27:25come into my office, close the door. And he said, sign this paper. Um, it's like, uh, uh, okay.

1:27:32So it's like for a new project, you sign the paper, I'll tell you what it is.

1:27:34And it's like, uh, okay. So I signed the paper to some paper was an NDA, a non-disclosure agreement,

1:27:42you know, that of course, everybody at Apple is already under an, uh, a non-disclosure agreement,

1:27:48blanket non-disclosure. So this is the super double secret non-disclosure agreement specifically

1:27:54about this project, uh, that he was going to tell me about if I signed. So I sign and I hand the

1:28:01paper back to him and he says, yep, we're going to make a cell phone. And that was it. And so then I

1:28:07was on the team and, and it turns out there was about like maybe six or eight other, um, intrepid

1:28:13engineers, you know, none of us had any experience making cell phones. Now we eventually brought in

1:28:21another team member who did, but of the people who made the iOS, the first version, none of us

1:28:28said ever worked on a cell phone before, uh, at that point is, has the bake-off been completed

1:28:36or is the bake-off, you know, with, Hey, what if we just build our own OS from scratch based on

1:28:42Linux and it's not cut down from Mac OS X is that still going on coincident in July? Yeah. So to be

1:28:48yeah. So to be clear about that, what I, what project I signed up for was the effort to shrink

1:28:56down Mac OS X, right? To take the desktop OS and to shrink it down so we could run it on this phone.

1:29:04Right. And, uh, then that project was being run by Scott and Scott had deputized, you know,

1:29:09on read to be the day-to-day manager since Scott had lots of other software responsibilities and

1:29:15design responsibilities as well. So, um, so that was part of the effort. So I got to see

1:29:23what became UI kit from a very, very early point. Uh, and you know, just one of the little,

1:29:29you know, sort of isms that is, you know, fixed in my memory about the, uh, about the Apple

1:29:34software development culture is that, uh, we used, uh, the precursor to Xcode today,

1:29:40which was called project builder, which actually came from next. So that was the, the, the

1:29:47development environment, the IDE for, uh, the development that we were using. And the way that

1:29:54software works is that whenever you created a new file, it had added this header at the top,

1:29:59which the name of the file and the person who created it and the date. So I remember that UI

1:30:06view dot M and object to see file for the basic fundamental view abstraction in UI kit was made

1:30:16in may of 2005. Uh, so it's not, you know, around two months later I joined, but you know, UI kit

1:30:24was already underway and, but not really much more than two months of work had been done to, to,

1:30:32to make this shrink down Mac OS 10 version of the phone operating system. So that's when I joined,

1:30:43that's when I can give you my, my best at it at a station that this is the, you know, the state of

1:30:50things in, you know, at that moment, July of 2005. And, and at that point, is your team committed

1:30:58to knowing that it's going to be an entirely touchscreen UI and it's not going to, yeah.

1:31:04Oh yeah. Yeah. There was, there was, um, uh, we had prototypes, uh, and I think you, you linked to

1:31:12one of the tweets that I, uh, that, that I, I made of a photograph of one of these prototypes,

1:31:18you know, these little plastic touchscreens that we, uh, you know, everything at Apple has a code

1:31:24name. And so the code name for these things were wallabies. So these little wallaby prototypes that

1:31:30are like, like, um, you know, kind of like a, a, a, a chunky, uh, three and a half inch diagonal

1:31:37screen with a kind of a big thick plastic bezel on it. And it was just a touch screen. It didn't

1:31:44have any compute on board. So we had to take these, these wallabies and tether them to a Mac.

1:31:51And, you know, there was this whole USB thing and there was this bare circuit board. I had a

1:31:56bare circuit board on my desk for a year and a half, uh, to interface between the Mac to the

1:32:03wallaby to get everything, you know, get that, that touchscreen hardware up and running. And

1:32:10this wallaby then showed up on your, uh, on my Mac as an external display. So I could be running

1:32:18a prototype version of an iOS app on my Mac and then moved, dragged that window over, uh,

1:32:29the, to the external display and then pick up the display and start interacting with it using touch.

1:32:37But, you know, things were so, uh, provisional things were so, you know, we were trying to

1:32:43scrambling so much that there was not even any touch recognition software. We were just using

1:32:50mouse events, right? So it was just like, you know, mouse down on that button, you know, the

1:32:55mouse up. And, uh, it was months later by time we, we actually started, uh, uh, addressing the,

1:33:04the multi-touch capabilities of the, uh, of the screen in, in, you know, in the iOS software.

1:33:10And so that was the state of play. It was going to be a, uh, uh, you know, this,

1:33:16this full touchscreen was going to be the basis of the whole system.

1:33:20Uh, and so that means you're there, you're on the team, you've signed the extra super

1:33:27double secret, uh, NDA. The team is very small. It is very secret. It is obviously got the

1:33:35attend. You must know at this point, that's got the attention of Steve jobs, literally the,

1:33:39you know, highest levels in the company. Um, and yet the Motorola rocker hasn't even been announced

1:33:46yet that gets announced in September. So I don't want to spend time on a rocker, which you didn't

1:33:51work on and which was a dud, but what was that like knowing that you're already on this team

1:33:56and it's, you know, starting to pick up steam and it's getting, it's gone from, you know, in months,

1:34:02it's gone from one empty UI view dot M file to, Hey, we've got some stuff running and we've got

1:34:10some ideas here. And meanwhile, then in September, there's the, you know, the phone and, and the thing

1:34:17watching the video again this week that I always forget is that when Steve jobs introduced it on

1:34:22stage before he called it the rocker and said it was from Motorola, he said, I want to show you the

1:34:28iTunes phone and, you know, and to his credit, he was trying to sell it, you know, I mean, and what

1:34:36better way, you know, certainly saying we we've partnered, you know, if the first words out of his

1:34:40mouth were we've partnered with, with Motorola on their new phone, the rocker to have iTunes running

1:34:46on it sounds way less exciting than Steve jobs in a big keynote in Moscone hall saying, I want to

1:34:52show you the iTunes phone because outside Apple by that time, again, it was a perennial idea that,

1:35:01Ooh, everybody hates their cell phone. Wouldn't it be great if Apple made a cell phone? Well,

1:35:07honestly that, that it sounds simplistic, but that's honestly an inside Apple. That's the

1:35:11same thing. Everybody at Apple hated their cell phones too. Everybody did. They were all terrible.

1:35:15Yeah, we did. Yeah, we, we, we did. I mean, I can reach on the shelf behind me here. I have a, a,

1:35:23a, a handspring phone with a flip up display there and a nice little chicklet keyboard. Yeah. We,

1:35:31you know, that was the phone that I had at the time. It's got, you know, the little knobby

1:35:34antenna coming out of the top, you know, and, you know, it, it just was, wasn't good enough.

1:35:40So what's, what's your, what's your team's take when, when the rocker comes out?

1:35:45Well, look, I, you know, it was, um,

1:35:48we always had a sense that, you know, and really thinking of two minds, I mean, I look,

1:35:55I'll speak for myself and I, I wouldn't be surprised if other people felt the same way,

1:36:00but I can't be sure. So I'll just, you know, speak for myself and saying that, you know,

1:36:05we really were of two minds in that it's like, yeah, we want a better phone and we think that

1:36:10we're going to make it, but gosh, we're really far from it. And, um, you know, we, we, we might fail.

1:36:17So that's the, really the two minds is we want something better, but we might fail. And so it

1:36:24just kind of seemed, and, you know, we're not going to be ready anytime soon. So it just sort

1:36:28of seemed, you know, prudent that someone like Steve is trying to run a big company and he's,

1:36:33he's kind of in some ways hedging his bets. I mean, and, and hedging them in a couple of

1:36:37different ways in that, you know, ours isn't going to be ready. We need something now.

1:36:42We might fail. You know, what's going to be the best mix, you know, how are we,

1:36:49how is he going to preserve the, the best possible future outcomes from Apple, given what he knows

1:36:55right now and some hopeful speculation about what we're going to be able to do. But, you know,

1:37:02it really also does speak to the reality that we had no idea how successful the iPhone was going

1:37:10to turn out to be. We weren't even going to be sure that it was going to be successful at all,

1:37:16that, um, we might go and look, this was, you know, at, uh, you know, at that point,

1:37:22uh, a couple of months later, we were hiring, we were maybe up to, you know, 10 to 15 software

1:37:28engineers and maybe, you know, eight to 10 designers. And that was the iOS effort. You know,

1:37:36a couple of executives, a program manager, and that was it. So it was a small handful of people.

1:37:41And so it was a bad and the rocker was another bad. But a real bet is a bet you can lose, right?

1:37:49If you know, you're not going to lose, you're not actually wagering. Like if you, you know,

1:37:53I don't know, this might be a terrible analogy, but if you know that a horse race is fixed and you

1:37:58place a bet on horse seven and you know that horse seven is supposed to win, you're not really

1:38:02gambling. I guess there's a bit of a gamble of, well, is the horse going to go along with it or

1:38:07whatever, or like, you know, like pulp fiction, like a fixed prize fight. What if the guy who's

1:38:12supposed to, you know, take a dive actually knocks the other guy out because he bet against it the

1:38:18other way. I mean, so it's a small bet, but it's a different kind of bet, but the real bets, I know

1:38:23this sounds highfalutin like I'm giving people life advice, but if you guys only set out to build

1:38:29a phone that you knew you could make, it's July, 2005, you've just joined the team and you're

1:38:35whiteboarding the whole idea. And you're saying, and if every single step of the way was, well,

1:38:40let's only put things on this idea that we know we can do. A hundred percent sure we can definitely

1:38:47build this. You don't get the iPhone, right? Like the only way you get the iPhone is to have things,

1:38:53and again, to bring it to your story, you're committed at that point to a complete touchscreen

1:38:59display and nobody has any idea how you're going to enter text yet. And it's basically,

1:39:03we'll have to figure, we'll bet that we can figure that out. Yes. Right. It was, it was a total bet.

1:39:10There were, there were some early ideas and the fellow who made the company called Fingerworks

1:39:20that Apple acquired that brought over the multi-touch technology, he had a huge number

1:39:26of responsibilities on his plate to make that part of the system work. But Fingerworks previously also

1:39:33had made a hardware keyboard of their own based on multi-touch software, you know, kind of a full

1:39:41desktop form factor external keyboard. So the fellow's name is Wayne Westerman,

1:39:49an absolute genius. He was also sort of planning on making the software version of the keyboard,

1:39:57but it was just too much. And that keyboard wasn't coming together fast enough. And it's kind of one

1:40:06of the, again, I mentioned before one of the real secrets of how Apple has made, you know,

1:40:14made products in the past and the culture of making products that has continued over the

1:40:20longterm software frameworks was, was one of those keys. One of the other keys is

1:40:27tracking progress and being very, very realistic about how fast the progress is going.

1:40:37Being honest, honest with yourselves. Yes. And, and if progress begins to lag,

1:40:45it doesn't need to lag very long before something is done, you know? And, and I think this is,

1:40:53you know, I, you know, I I've heard, and I have no inside knowledge about it. But I've heard,

1:40:59you know, the same thing happened at Pixar and has happened over with Pixar movies over the years

1:41:05that, you know, a director was changed midstream that like Ratatouille didn't start with Brad

1:41:10Bird directing it. He was brought in later because the director who was on there was just not making

1:41:15quick enough progress. And at that point, they knew well enough what progress on one of these crazy,

1:41:22you know, difficult, you know, creative technical projects should look like there's a certain amount

1:41:29of messiness that goes on and a certain amount of we're going to figure it out as we go. But beyond

1:41:36a certain point, there's a recognition that this has gone off track. Right. But then, and with like

1:41:41with the Pixar movie, there's also like, there's like a window, like, Hey, this is our Thanksgiving,

1:41:46you know, whatever year, you know, Disney needs a big family movie at Thanksgiving in this year.

1:41:52You know, 18 months from now. This is it, you know, there is no plan B. Yeah. Yeah. And, and,

1:41:59and so at Apple, there was always a, you know, it was always a schedule that we were moving toward.

1:42:04And of course, at that point, you know, Mac world was a, was a big event. And, and so there was

1:42:10always kind of like in this back of our mind, I don't know that I ever could really say for sure

1:42:14that I knew it was going to be January of 2007, way back in the summer or fall of 2005. But that,

1:42:24you know, it was always a feeling that, well, somebody has some date in mind and that they're

1:42:30using that date as a, um, as a measuring stick, right. Counting back from that date, are we going

1:42:39to make it? And everybody's asking every, every day, are we going to make, are we on track? Are

1:42:43we going to make it? Are we going to make that next milestone and so forth. And so the, you know,

1:42:48in the fall of 2005, there was just a termination that the software keyboard project was not

1:42:54on track and we needed to do something. And so it's really a unique experience in my,

1:43:00my whole Apple career is that just one fine day on re called everybody out into the hallway and

1:43:05said, stop what you're doing. And, and, and to be clear, calling all of the software engineers and

1:43:10designers working on iOS and said, okay, stop what you're doing. Everybody's starting from now

1:43:15as a keyboard engineer. We need to figure this out. We need something different and better than

1:43:21what we have now. And so all of us then it's like, well, no. Okay. It's like, uh, go get a

1:43:28cup of coffee, go back in your office and sort of close all of the windows that you had open in

1:43:34project builder. And it is, I do whatever you want, get your whiteboard out, get a notebook,

1:43:39you know, open up a new file and start figuring out what, uh, what keyboards, um, uh, we, we might

1:43:47be able to make. And, you know, it was just absolutely extraordinary is that the team was,

1:43:52was a bunch of generalists. I mean, if you could just imagine that there were instead a team

1:43:58stocked with people who either came from Nokia or Motorola or, you know, some other company that

1:44:03their cell phone engineers, they might not have been so able to, you know, so easy to pivot, you

1:44:09know, onto some brand new projects, some new areas that they've never thought about, uh, just on a

1:44:16moment's notice, but we were all just generalists. So it's like, okay. Um, we all had different

1:44:22backgrounds and things, but we were not, we, we didn't have a particular area of focus other than

1:44:29trying to make the best software possible. And so people just did. And, and in very,

1:44:34very short order, uh, there was a stream of new demos. We were inviting each other to, uh,

1:44:40to, uh, teach other's offices, come on in, have a look at this one. What do you think?

1:44:44Uh, and it was just this, this gurgling cauldron of new ideas for how to enter, uh,

1:44:52text using a touch screen. All right. Let me take a break. Let me, I don't want to interrupt you.

1:44:57Well, I do actually, cause I want people to come back after the break cause it's such a good,

1:45:01it's the high point of the story, but let me tell everybody about our third and final sponsor. We

1:45:05had remote retool and alas, we lose out on the third cherry of another sponsor with a,

1:45:12a re in front of their name. It's Squarespace. I'm going to call them up and I'm going to suggest

1:45:18they rename the company. Resquare space just to, just to make this episode perfect. But in the

1:45:24meantime, there's still Squarespace and you've probably heard of them. They are the all in one

1:45:28platform for building your brand and growing your business online. Stand out with your own

1:45:33beautiful website, engage with your audience and sell anything, your products, the content you

1:45:38create, even your time. Uh, they've got some great features. They've got member areas where you can

1:45:45unlock a new revenue stream for your business and free up time by accessing, selling access to gated

1:45:51material like videos or courses or newsletters for paying members. It all goes through Squarespace

1:45:59analytics. They have analytics built in with one of the best designed analytics dashboards I've

1:46:05ever seen. It is so clear and instead of looking like an airplane cockpit, like most analytics

1:46:10things do, it's like looking at a really nice cars dashboard with just what you really want to know.

1:46:16It's so good. Online stores, anything you want to sell, they handle everything from

1:46:23stuff like inventory to the actual commerce and processing of the payments. It's also,

1:46:31it's all so easy to use. They've got custom templates, best in class, professionally

1:46:35designed templates that you can just use as is with almost as many styles as you can imagine

1:46:43to choose from that look great on everything from phones to big desktops. And you can customize them

1:46:49a little, customize them a lot or build your own template for scratch. If that's what you want to

1:46:53do, everything is easy to use and you can get started so quickly. So what you do is you go to

1:47:01squarespace.com/talk show squarespace.com/talk show. You get a free trial, you get 30 days,

1:47:08you can do whatever you want for 30 days. There's no watermarks on the website. It isn't marked as a

1:47:13free trial. It's a real Squarespace website for 30 days free. And when that time's up and it's time

1:47:18to pay, use that offer code talk show, and you will save 10% on your first purchase.

1:47:25So effectively there's, there's a bake-off on keyboards. It is sort of an intramural kind of

1:47:32like a science fair contest. Yeah. One of it's one of my, I don't want to spoil. I don't want to,

1:47:36I don't know. I want people to, who haven't read your book to read the book. I don't want to spoil

1:47:39so much and we can talk about things that aren't in the book, but I love this part of the story

1:47:45where it basically, you guys were supposed, everybody on the team was supposed to implement

1:47:52their keyboard is like part of a, like a framework again, to use the framework where it could be

1:47:59plugged in and within the same demo on the same device, everybody's keyboards could just, you know,

1:48:04if there's 10 keyboards to demo and you're presenting them to Scott Forstall, you could

1:48:09just go through on the same device, one, two, three, four, and you know, whoever's number four

1:48:14is can introduce it and say, look, it's like a wheel. And you do go out from the middle and your,

1:48:19yours didn't fit in the framework. No, no, because, yeah, so I, I was a bad student and I didn't

1:48:28complete the assignment. But because, well, you know, you know, I, I wound up, rewriting from

1:48:36scratch, like three or four times, by that point. And, it's, it's, it was like, well, you know, I,

1:48:46I think maybe if I rewrite it once more, I could, I could maybe get something that really works.

1:48:52Either the dictionary was too slow or the, you know, the touch handling was no good. And I figure

1:48:56I really need this one more rewrite. And I could either take my current version and, and figure out

1:49:03how to get it integrated into that framework that you mentioned, or I could do this rewrite.

1:49:08And it decided to do the rewrite. And I think the keyboard came out pretty good,

1:49:13but what then just happened is that there was going to need to be a step where I was going

1:49:18to need to get, you know, take the, the prototype out of Scott Forstall's hands, you know, to go

1:49:24over to the Mac and, you know, run a new command and then hand the thing back to him. So it was

1:49:28just with the, you know, the, the, the, you know, the people organizing the demo wanted to,

1:49:32to avoid that. And so I went last and, you know, it kind of got down to the end of the demo and,

1:49:40you know, Kim Vorath who was running the, the, the, the project said, well, Scott, that's it,

1:49:46that's all the keyboards in the demo. And I was like, wait, wait, no, no, no, I still have mine

1:49:51to go. And you know, it was, you know, it's so funny how, you know, history kind of turns on,

1:49:58well, if Scott had gotten a phone call right at that moment, or he decided, no, I've seen enough,

1:50:03he could have just left the room and I never would have gotten a chance to show my demo, but I did.

1:50:07And he liked it right away. And you know, he, you know, the, the Forstall is just, you know,

1:50:14is so smart and just is so quick to get down to the to what question should he ask that would

1:50:27tell him the most information. And so I talked to him years later and he said, Ken, he wanted to

1:50:36know, he can't even see it. Like ask me what is, what is going on in the software here? And I said,

1:50:42Oh, well, I'm looking at your touches and I'm trying to figure out what you wanted. He says,

1:50:46like from that moment was sold. He said, you had figured out how to make software a part of the

1:50:55text entry experience because of course, for the most part, you know, there's some low level

1:51:00software going on, say in the, you know, the MacBook pro keyboard sitting in front of me to

1:51:06marry up the keys to the software that processes them. But it's, it's not sophisticated software

1:51:13in terms of what it's doing. It's just they're processing events from the hardware. Whereas the,

1:51:19you know, the breakthrough that, that I came up with on that earliest keyboard was to say,

1:51:24no, I'm actually going to look at what you might mean, look at what you did and try to match those

1:51:30things up to give the desired result. And that was enough for him. So I got the job. I became the DRI.

1:51:37But as you've mentioned in the book, part of the scary part about going last in any sort of like,

1:51:44Hey, we've got an hour to demo projects to, to Scott Forstall. If you're going last, the risk is,

1:51:49well, what if Scott was late because of something else he had to do? You know, as you said, he was,

1:51:54he was at least a little busy as I, as I inserted into my timeline, which I think is fascinating in

1:52:01hindsight, 2005 was also when Apple announced the move from power PC to Intel processors for the

1:52:07Mac, which guess what was a big deal. Yeah, there's lots going on. So Scott could be late,

1:52:13but he still has to leave at the end of the scheduled time for the next meeting because

1:52:17he's got something else or Scott could leave early. Cause maybe his phone goes off and somebody

1:52:21says, Hey, is Steve wants you. And you know, when Steve would, Steve would call, no, Steve would just

1:52:26call him directly and just say, Hey, come here. I got to talk to you about something. And guess what?

1:52:30When Steve jobs call Scott Forstall and says, I need to talk to you about something. Scott

1:52:33Forstall goes and talks to Steve jobs. Right. So you, and I, again, it's, you know, like I said,

1:52:40maybe, you know, you don't hire Williamson, maybe web kits, not based on cage TML, you know, maybe

1:52:46Steve jobs call Scott Forstall. Maybe we have a different keyboard. I mean, and again, it's not

1:52:51like, Oh, you were just a rando off the street who this was your own, you know, your, your only

1:52:57screen test. You were an employee on a small team. You might've had a chance to show him the keyboard

1:53:02subsequently. Sure. But it's still, it makes these things just, yeah, it really does. It just,

1:53:09I just remember in that, that moment of, of, you know, you never really, you know, you want to

1:53:18make a scene in a demo with Scott or, you know, never with Steve, but not even with Scott,

1:53:25you know, it's, it's, it's a high stakes, it's a high stakes moment. And so, you know, sort of

1:53:30pressing and pushing to say, no, no, no, I have this other demo to show felt like it was a little

1:53:35bit of a risk, but it was a risk that paid off. You tell the story of demoing it for Phil Schiller

1:53:41the first time. And at the time your, your, your keyboard had, instead of having a discreet

1:53:47onscreen key for all 26 letters of the alphabet, there were groups. So like, K W E was one key.

1:53:55I think that's what it was. Cause you know, Q W E of course the first three. And then you would

1:54:01press that key for any word that with a Q W or E and press, you know, other keys that either had

1:54:09two or three letters on them. So they were bigger touch targets. And then the dictionary would figure

1:54:13out, well, out of all these possibilities, the first letter is either a Q W or an E the second

1:54:19letter is either a J K or L or whatever. What's what's the most likely possibility, but it looked

1:54:26weird. And I think that basically your demo for Phil Schiller with the first keyboard was like two

1:54:31minutes. Like you're braced for like, Oh my God, it's Phil Schiller. He's, you know, he's got this

1:54:35reputation. He's got strong opinions, you know, good taste. This could be a night, you know,

1:54:41maybe not even a nightmare, but this could be like an hour long slog of arguing over details or

1:54:46defending my actions. And instead it's two minutes. And he was like, man, but, but, but what comes

1:54:54away from me in the book and it's what I love about your attitude and what I think made you so

1:55:01successful and maybe typical for the Apple mentality is rather than take it personally,

1:55:07like, huh, huh, how about that? I've been slaving over this for so long, laboring over this for so

1:55:15long. And he just took two minutes and walked away, but you took it and thought, huh, something

1:55:20didn't impress him. And it's like, well, he's Phil Schiller. He cares about how things look,

1:55:24how it's going to look on stage when it's demoed. And if it looks weird,

1:55:27that's, that's off, right? It's off for Apple for something to look weird. Right. And it,

1:55:33it started sort of this, not a bump demo, but like, like a surprise demo, like this,

1:55:40I can't believe it was only two minutes. This is so important. And instead it spurs you to think,

1:55:45huh, and it gets your gears turning to, and then I think you said it was Greg Christie,

1:55:50who's just like, how about you just make each letter a key? You know, I'm not going to

1:55:54do a great. No, it's, you know, Greg Christie is, I love the guy to death, but he had met him a few

1:56:00times. He's just, he, he is, you know, he is a wonderful, you know, the warm supportive person

1:56:11to, to work for once you get to know him, but he is very, very gruff on the exterior. And, and,

1:56:18you know, he's from New York and he's very, very direct in his communication style. So we were

1:56:23sitting in a meeting one time and he's just, oh, come on, Ken K, you just put, make one key for

1:56:27every letter. And that's it. And so, you know, you, do you went and described, you know, how

1:56:37that earlier software worked, whereas it's done with this group, you know, this, this key that

1:56:42had this group of letters on them. And that when you press that key, so it was a nice big touch

1:56:47target. So you could, you could, you could hit the key reliably. You're going to get, you were going to

1:56:52get one of those three letters. And so look, all I did was I chopped up the graphics so that it looked

1:57:02like you were getting, you were tapping only one of those keys, but underneath the software was

1:57:07doing the same game. And as a matter of fact, it even did more because when each letter was on,

1:57:13you know, when three letters was on one key, you were only going to get that letter because the,

1:57:18the keys were large enough targets to hit. And once I made the key smaller, I started taking

1:57:23into account keys that were letters that were above and below. And so I made, you know, the kind

1:57:29of these dynamic sets of keys, but creating the illusion that you were only tapping one key. And

1:57:35that was enough. That was enough to, you know, give people an impression that it, the, the

1:57:42keyboard was something that they could understand the first time that they approached it.

1:57:46I love the story of the keyboard. I think it makes such a great example. And again, the book is,

1:57:53as you said, 80,000 words. It goes into much detail, but sometimes you need a smaller example

1:58:00or a concrete example to exemplify a principle. And I have always thought, again, not saying this

1:58:06just because, you know, you and I are pals and you're on my show here, but I do think that the

1:58:12iPhone keyboard exemplifies everything Steve Jobs said on stage about why make the whole phone a

1:58:19touchscreen, which is look, you know, once you put hardware buttons on it, the hardware is there

1:58:25forever or until you make a new device. Whereas we know how to make something that changes with

1:58:32new ideas that we haven't even had yet. It's called software. Right. And the keyboard itself

1:58:37exemplifies that. But the other thing I really love about the iPhone keyboard in hindsight

1:58:42is that it, it looks at first like the most obvious idea in the world, starting in a world

1:58:50where Blackberries and Blackberry type phones were at that point, the, the, the best-selling

1:58:57smartphones, right? If you wanted to do a phone that did like email and messaging, you were getting

1:59:02a Blackberry or a phone that looked like a Blackberry, which had an actual 26 keys for all

1:59:07letters of the alphabet and punctuation and a space bar. And you actually click them with your

1:59:12thumb. And at first glance, that's what the iPhone keyboard looks like. It just looks like a

1:59:17touchscreen version of that, which is like the most obvious thing to do. It doesn't look clever

1:59:22at first. It looks like the most obvious thing possible. And all of the other differences,

1:59:29the affordances, the well, but we don't get, you know, with a Blackberry keyboard,

1:59:33you actually do get to engage one of your senses touch, right? So your thumbs are covering the keys,

1:59:40which is, you know, not, not what you want, but it's what has to happen with thumb typing.

1:59:45But because you can feel as you move from the S to the A that you're on the next button to the left,

1:59:51you know, to press, whereas you're never going to get that touch. You have no sense.

1:59:55Never going to get that right. Yeah. And it really is way down in your nervous system. When you,

2:00:02you're feeling the edge of something on your finger. I'm not even sure that like your cerebral

2:00:08cortex is getting involved. Right. I mean, it's like, pull your hand off the hot stove.

2:00:13What they always say. They say that that takes place, that takes place faster than,

2:00:16you know, you've burned yourself. Your hands already yanked back.

2:00:20That's right. And, and that, that deep tactile sense is so baked in so much of our nervous system

2:00:27is given over to the sense of touch on our, on our hands and on our fingertips. And so taking that

2:00:33away on the, on the glass needed something to replace it. And that turned out to be auto

2:00:40correction software, but we didn't know that there was, it was, it was something that we needed to

2:00:45discover through this, you know, sort of arduous seeming, I mean, it wasn't that long. It wasn't

2:00:50like it was a years long research project, but I'll tell you in the day to day going through it

2:00:55and the stress of having to, you know, sort of, you know, save your project, you know,

2:01:00we didn't want to get canceled. We wanted this phone. And so it seemed like it was a lot of

2:01:06pressure. It wasn't like you were working on an obscure part of the, of the OS, right? I mean,

2:01:13everybody, no matter, no matter what you were going to use the iPhone for, you were going to

2:01:18encounter this keyboard. And there was a state of the art, which was the Blackberry style hardware

2:01:23keyboard, which is obviously what it was going to be compared against. And the other factor that

2:01:28complicates that is that the, you know, crack berries or whatever you'd call the, the, the

2:01:32addicted, the people who are addicted to their Blackberries develop the ability to type very fast

2:01:38on their Blackberries, right? So, you know, it's not just, oh, everybody has hardware keyboards.

2:01:44It's everybody has these hardware keyboards that people can learn to type fast on. And so it sets

2:01:50the bar, right? And then we get back to like Internet Explorer on Windows rendering speed

2:01:59versus Safari. Well, there's the bar because here it is. It's on, it's on your desk. I have a PC set

2:02:04up running the latest version of Windows with IE and here's how fast they rendered the New York

2:02:09Times homepage. And here's Blackberry. Here's how fast some people can type on it. What can we do?

2:02:15And then you come up with these ideas that, that are impossible on a physical keyboard, like

2:02:21when you press the S key on the iPhone keyboard and a popover appears above your thumb or finger,

2:02:28however you choose to type. I shouldn't say thumb because my wife is a, is a finger typer.

2:02:34It, there, there's no way to do that in hardware to, to confirm, hey, you, you know, I, you know,

2:02:39the keyboard thinks you just hit an S, you know, and there it is S I mean, right. How many,

2:02:44at this point, honestly, I, you get up past billions and it's hard to know how many trillions,

2:02:51possibly whatever comes after trillions of key presses on iPhone keyboards and Android keyboards

2:03:00that use that same design of when you, you know, it looks like a QWERTY keyboard and your finger

2:03:05or thumb hits the letter and a popover shows up above. So you actually can see what it thinks you

2:03:10hit. How many key presses have been made at this point? It's, or how many have been made while

2:03:15we're recording this show around the world? Yeah. Oh, a lot. You know, that's, it's one of the

2:03:21danger aspects for me of this show is that people are going to have a better idea that, that it's me

2:03:28to blame for all of that. I wanted, I got to bring this home soon, but I want to, I want to tell you

2:03:36a story that I heard from somebody at Apple who would know. But I can't say who, but years ago,

2:03:42basically part of the drama of you guys putting a stripped down version of OS X on a cell phone

2:03:51in 2006, 2007 is that at that time, Mac OS X wasn't that fast on PC hardware, right? And

2:04:02especially go back to 2002 when Mac OS X first shipped to the public, it was dreadfully slow

2:04:11compared to 2001 or 2001. Well, 2002, 2002, I mean, I would say it was at least 2004.

2:04:16Oh yeah, it wasn't fast yet.

2:04:18Yeah. I talked to somebody who said they knew all along that the way that, you know,

2:04:24and it was slow because Aqua was so ambitious with the drop shadows and all the text anti-alias and

2:04:31the transparency and everything that made it quote unquote lickable and made it look, wow,

2:04:37made it slow to like hit the file menu in an app and watch the menu drop down. And what I was told

2:04:45was that Apple starting even before Mac OS X had shipped, had a lab where they had a bunch of tests,

2:04:53like drop down menus and applications, dragging, you know, the latency between dragging an icon

2:04:59and, you know, does it track the mouse one to one and measuring it down to like the hundredth of a

2:05:04second and comparing it against Windows XP. And I think a lot like the early days of Safari getting

2:05:12blown away by IE on Windows, Mac OS X, the difference is Mac OS X actually shipped like that.

2:05:18And for years, and every major version of Mac OS X got faster and faster, but they still had this

2:05:23benchmark of, is it as snappy as Windows XP? And the answer was no. So there was this bar, which

2:05:30to me is not just for Apple, but anybody, when you have a bar above you, you know, it's such a better

2:05:36motivator than once you're the bar, you know? But what I was told, here's what I was told though, is

2:05:43when Windows Vista shipped, and I forget what year that was, but 2006 or seven or something like

2:05:51that, the people who, you know, who were aware of this benchmark for testing the speed of the OS

2:05:58didn't know what to do because Vista got slower than XP and it was less snappy. And the decision

2:06:06was made, well, we're going to keep testing against XP. That's our benchmark. And I think it

2:06:12speaks a lot because it was sort of like being able to cheat and say, well, now we're not as slow as

2:06:17we used to be because we'll run against this new version of Windows, which is slower. But one of

2:06:22the big, this is where I'm going with it, is to me, a big difference between the original iPhone

2:06:28and the first version of Mac OS X is that the first version of Mac OS X, like if you dragged

2:06:34a window around, it dragged the whole window without an outline. Like, and for people who

2:06:41are younger or never used classic Mac OS, when you dragged a window in Mac, in a classic Mac OS,

2:06:46what you dragged was just an outline of the window to show where it would go. And then when you let

2:06:51go, the window would redraw in the new spot. And so it didn't actually, you weren't seeing the

2:06:58actual window move around. And when Mac OS X shipped, and it did, that's a cool idea,

2:07:03but you saw this shearing, you know, it, the video couldn't, the performance couldn't keep up with

2:07:09it. And when you scrolled, it scrolled live, but the contents of a complex document or a webpage

2:07:16couldn't keep up. It scrolled slow, even though it scrolled with visual fidelity. It looked cool,

2:07:24but felt slow. iPhone did something very, very, to me, that was so clever, was like,

2:07:32and you'd noticed it most in Safari, is like when you would scroll in Safari, the scroll view would

2:07:37always track your finger, no matter how fast you scrolled. And if it couldn't keep up,

2:07:41it would just render a checkerboard. Yeah, that's my idea. Was it really? Was that in the book?

2:07:47Did I miss that? I don't know. I don't think that didn't make it in the book. I don't think it was

2:07:51my idea. Well, then I'm asking the right person because it was sacri, instead of making, putting

2:08:00that as the top priority, visual fidelity and making, make it as fast as possible. The second

2:08:05priority, the top priority was always keep up with the finger. Is that right? Yeah, absolutely. And,

2:08:11and this, uh, uh, I did write this in, in the book, um, that directive came from, um, uh,

2:08:21and, and was best exemplified by, uh, the demo that Imran Chaudhry would give. Uh, and, and you

2:08:29have to kind of understand a little bit about the way the team was organized, how design and

2:08:35engineering collaborated with each other is that there was this software engineering team working

2:08:40on iOS. So the iOS software team, and then there was the human interface team, the HI team who had

2:08:48broad responsibilities for iOS and Mac OS, and, you know, the, uh, a whole lot of projects.

2:08:56And so, uh, and at the time, uh, the, there was a, uh, a clear mandate that if HI asked for

2:09:06something, it was the, the duty of the engineering team to do their best to deliver it. And it just

2:09:14was no question as to, you know, the, the engineers want X, the HI team wants Y, and now there's going

2:09:22to be some sort of, uh, reconciliation, whether we do X or Y or both. It's like, no, no, no, no, no.

2:09:28What the HI team asks for, they get to the extent possible within the bounds of physics. Right? And

2:09:38so this demo that Imran would give is that he would take a, just a blank sheet of paper on an,

2:09:45uh, on a clear table. And he would put the piece of paper down and then put his finger in the middle

2:09:51of the piece of paper. And he would move the piece of paper around, glide the piece of paper around

2:09:57on the, on the tabletop. And he would say, piece of paper is not jumping. It's not skipping. It's

2:10:04tracking my finger. Exactly. That's what the pixels need to be like on the iPhone. It needs

2:10:13to feel like those pixels have a physicality to them that they're just pinned under your finger

2:10:20and that you can control them. If there's ever any lag or skip or judder, it breaks the illusion.

2:10:28And we don't want that. It's, it just is not part of the design that we're aiming for. And so we

2:10:35couldn't deliver that in the, in the web browser with, you know, with full fidelity, scrolling the

2:10:40content. And so I just came up with this idea. It's like, okay, well, there's going to be this

2:10:46under under layer underneath the web content that if we can't draw there, you're just going to see

2:10:53this checkerboard. And I actually have to pretty, you know, pretty sure that, you know, that, that

2:10:58even at that time Photoshop had a similar sort of idea. It says, I'm just going to do that. I'm just

2:11:05going to do that for the web browser. So yeah. Yeah. I'm glad you appreciate that. But it was,

2:11:11it was to meet that design goal of that where, where we don't break the illusion.

2:11:17Well, the Photoshop idea to me was always, and I know, I don't know, maybe, you know, again,

2:11:23I think for most of us, we, we never read the manuals. Maybe they explained it somewhere,

2:11:28but I never read the Photoshop manual. I was self-taught, but to me, it was always,

2:11:32and as a budding UI designer and lover and fast, somebody fascinated by it, it was like,

2:11:39how do you render nothing? Right? And it's like, what, what color, what color is water?

2:11:45And I remember one time in school, like a science teacher asked that once and the kid and the kid he

2:11:49picked was the, he, I think he purposefully picked a kid who he thought would give the,

2:11:54the answer he wanted, which was that the kid said white. And he said, no, it's not white. And he put

2:11:59something colored behind the glass of water, you know, and if it was red, then you could see red

2:12:04through there. You know, it's clear, but how do you render clear? You can't render clear on a

2:12:09screen. And so Photoshop came up with this checkerboard. If you delete everything,

2:12:13you can't just show white because white might be the actual background you want. So the checkerboard

2:12:18was the sort of nothing. Right. And I love that. It's kind of right. I mean, it's, it's like,

2:12:23you know, of course you can, none of these little hacks are ever perfect because what if the webpage

2:12:28is a checkerboard? So, I mean, you know, there's, there's always, there's always one, you know,

2:12:34you know, one ideal case, I mean, you know, where, where it could frustrated, it could,

2:12:40it could ruin the illusion, but it is just an illusion. It's just like, you're, you're saying,

2:12:45you know, this is, this is, you know, it's, it's, it's, it's a trick and, you know, trying to figure

2:12:52out what the right set of tricks are, what the right trade-offs are. You know, you mentioned

2:13:01that there is this, this decision which, which I'm glad that you, that, that, I guess I'm not

2:13:06surprised that communicated to you that, you know, the iOS, it just keeps up with your finger the

2:13:12whole time. It's like, that's something that we didn't want to get, give up on. And so we

2:13:18came up with a hack. It's, it's a good hack, but, but it's some, some bit of, of, of where, where

2:13:25the, the, you know, one part of the illusion breaks in order to keep another one stood up.

2:13:31And, you know, trying to design and, and trying to figure out what, what the right set, set of

2:13:38trade-offs is, I think is a big part of what has made, you know, Apple products so joyful to use

2:13:46over such a long period of time is because there's people there who care about it and have been

2:13:51caring about it for a long, long time.

2:13:53Recognizing that trade-offs are often not just between good and better, but sometimes between a

2:14:00thing that's good and a thing that's bad, right? So with the Mac OS X style, where nothing was ever

2:14:06checkerboarded and everything was always WYSIWYG, it looked cool and at the time was revolutionary

2:14:14for a computer, but it felt slow. Whereas you'd never wanted to see the checkerboard, the

2:14:21checkerboard itself. I'm talking about how cool I thought it was. You're saying it was a clever

2:14:25idea you had, but you certainly, you never wanted to see it, right? And Apple worked hard year after

2:14:30year to get it to the point where I forget at what point the checkerboard never stopped showing

2:14:35up in Safari. And it was always capable of rendering everything in real speed. It was only

2:14:39a handful of years. Surely there's a lot of people out here listening who don't even remember having

2:14:46an iPhone. Because it was just a few years, because you couldn't wait to get rid of it.

2:14:51You hated it. But if you had to make the choice between a thing that was like, "Ah, we give up

2:14:55on painting in real time," but that checkerboard is going to track your index finger one-to-one

2:15:02as fast as you move your index finger.

2:15:04Yeah. It was just, and I think part of the trade-off was we need to sell people on this

2:15:16notion of a touchscreen operating system. And so, we decided to make the guarantee that it's going

2:15:24to feel like a physical object to you. And that was just going to be part of what made people feel

2:15:33comfortable about it. I mean, when you're making systems, so often I've felt over the years that

2:15:41if I don't do a good enough job, people are going to take that product and they're going to want to

2:15:46throw it out the window. Certainly felt that with the keyboard. And it says, "What can I do to avoid

2:15:52that?" And so, throughout the development of projects, things aren't good. The funny thing

2:16:00is that if the project was good at any time, the executives and the marketers and the operations

2:16:06people would figure out how to ship the thing early if you were done ahead of time. And so,

2:16:12it never really is that. It's like during the middle of a development cycle, things aren't good.

2:16:19A lot of stuff is broken, features aren't implemented. Some of them are and some of

2:16:26them aren't. But it's like A is implemented, B isn't. And so, that also means that C is broken

2:16:32because it depends on B, even though the rest of it is there and waiting for B to be finished.

2:16:38And you just wind up with this whole set of Gantt charts that if you were to model it that way,

2:16:48where there's all of these dependencies and the system just doesn't work. It doesn't feel like

2:16:54it's come together until you start to get closer and more things get done. And so, there's always

2:17:01this game that you play as you're going and saying, "Well, what am I going to be able to

2:17:07get done in time? Can I do something like the checkerboard that maybe is a stopgap?"

2:17:13And we wind up saying, "Well, it's a good enough stopgap. We're going to be able to ship now."

2:17:17And so, it's this whole multi-dimensional game that you're trying to play to figure out, "Well,

2:17:28where is this sweet spot in this huge set of intersecting features and capabilities?"

2:17:38So, it certainly isn't science. It's an art.

2:17:43So, how big of a mess is everything at Humain right now?

2:17:48I'm not going to give you an answer to that.

2:17:56Stop stammering. Stop stammering. You were already kind enough at the beginning of the show.

2:18:01Before I could even ask you the obligatory question, you already said,

2:18:05"We're not talking about whatever it is that you and your colleagues are working on."

2:18:10Here's something that I will say about Humain is that we're hiring.

2:18:15So, if you're interested, I'll give you a link for the show notes.

2:18:23And yeah, we've got a lot of interesting work. And it's interesting and fascinating enough that

2:18:32I'm enjoying it very, very much.

2:18:36You took a meeting on a Saturday. So, it's engaging. But that is good. You have something

2:18:42to promote for Humain. They're hiring. We will put a link, I promise, in the show notes.

2:18:46The other thing we can talk about, which people can enjoy right now, current work,

2:18:51is your game UpSpell, which is sort of the—

2:18:57It was my pandemic project.

2:18:59It's your pandemic project. It's a word game for the iPhone. Surprise. It's very enjoyable.

2:19:05It is sort of the anti-wordle because wordle has no clock. And the whole point of UpSpell is you

2:19:13get like, like the—

2:19:15Two minutes.

2:19:15You get two minutes, you get a tile of letters like Scrabble, and you make words out of the

2:19:20letters. And then when you think you have a good word, you push it up. That's the up. And then

2:19:25those tiles get replaced by other tiles, and you try to make another word, and you push it up,

2:19:29and you try to make as many words as you can in two minutes with every time you use a word,

2:19:33the tiles get reloaded. It is very fun to play. If you like word games, I will also

2:19:38put a link to it in the show notes, but that's—

2:19:40Well, thank you.

2:19:41But, you know, it's good to have something else to pimp, for lack of a better word.

2:19:48And last but not least, your book, Creative Selection, is—we've only scratched the surface,

2:19:56thank God. I don't know what in the world made me think that a two-plus hour podcast

2:20:00would spoil the whole book. It's nowhere even close to it. But if you thought this conversation

2:20:04was interesting and you haven't read Creative Selection, my God, go run, don't walk, or just

2:20:12go to your Kindle or your iBook store and get it. But the website for it is creativeselection.io.

2:20:19That's probably the best place to send people, with links there that you can buy.

2:20:24Cannot recommend this book highly enough, and I deeply, deeply thank you for your time here, Ken.

2:20:30I gotta have you back on the show. We've got too many other stories to tell.

2:20:33I had a great time.

2:20:34It's easier—the second—it's easier for me to get you on the second time, or—because I had—now

2:20:40I know—I know—you know, I've—

2:20:42Well, you can always find me on the watch channel.

2:20:45So I just—

2:20:47We didn't even begin to talk about our shared love.

2:20:50Our shared love of watches.

2:20:53And close listeners to the talk show will—may remember that a couple of episodes ago,

2:20:59Jon mentioned that he had this crazy signal channel that was the only thing he was using

2:21:04the app for because he had a couple of friends. Well, it was the watch channel that we have,

2:21:10and with me and a couple of other pals. And we've actually moved it to iMessage now.

2:21:16What do you think of that? Is that a good change?

2:21:18No, I don't think so.

2:21:20I don't think so either. I think we should go back.

2:21:23Yeah, I think we should go back to signal. Here's why. Because the watch channel—here's why.

2:21:27And me piping up about it here secretly before, or in joke-wise before, got it to move to iMessage.

2:21:36But now let's just be explicit that I think we should move it back. Because it's not the sort

2:21:40of thing any of us on it need to stay up to date on. I don't need instant alerts. It's like, "Hey,

2:21:46let me check what's up with the guys on the watch channel." And so I think it's better segregated,

2:21:52whereas everything else I have on iMessage is generally stuff I do want to see right away.

2:21:57So it's sort of spoiling my iMessage. And then the other thing, selfishly, is that we're busy

2:22:02enough on our little watch channel that it gets me looking at signal, and I publish my signal number

2:22:08for readers of Daring Fireball to contact me securely and privately, which is great for that.

2:22:15But I don't—people don't—it turns out to be not—it doesn't get used that frequently.

2:22:21But now I don't check signal at all. And I—even this past week, I had—

2:22:25So it's a great way to get it.

2:22:26Right. I had a message pending from somebody, and I wish I had seen it sooner. It didn't

2:22:32ruin—you know, I didn't lose, you know, a sponsor or anything, you know, along those lines. It

2:22:36wasn't like I lost business. But it's like, "Oh, I would have answered that 48 hours ago,

2:22:40but I stopped looking at signal because the watch group isn't on it."

2:22:42Yeah, so we're gonna have to go back to—

2:22:45We could do a whole show on watches if you want.

2:22:48Yeah. I was—yeah.

2:22:52Thank you, Ken. This was absolutely a blast. And I do look forward to having you on again.

2:22:59Let me just say, before we go, my thanks to our sponsors, Squarespace, aka ReSquarespace,

2:23:04and Remote, where you can use them to hire workers in countries around the world, and Retool,

2:23:13the visual prototyping, build your own actual—from prototype to actual shipping—usable

2:23:21web apps for your teams. Great, great, great sponsors, one and all. Thanks, Ken.