 Hi. I'm Chris. I've worked at Google for actually about nine years. That's the funny thing about this. It's really more like, this is sort of a story I've been telling lately about the meaning of Android and where it came from. A lot of people, they have all these assumptions about the origin of Android. But like the movie Wolverine Origins, it's not the truth. It's not good. So I wanted to tell the actual story of how Android got started as part of the story of where we are now in the mere 20 minutes, which I usually take just introducing myself. Yeah, so let's get started. So this is like, oh, look who I am. But if you don't know, I'm sure you can use your favorite search engine, whichever one it might be, to find out. Although on one of them, there's a scrapbooker who is more popular than me with the last name of Dubona. So that's something I'm conflicted about. But yeah, hi. So I'm Chris. I look after license compliance for Google. That's my primary job. I do these speeches from time to time, but my main job is making sure Google does not screw up compliance. And actually, most of that work is done by Daniel Berlin, who's over here in the second row. So he's like the true hero that allows me to go and do ridiculous trips like New Orleans and have a beignet in theory. And we run summer code and a bunch of other programs. So the only thing I'm going to say about the summer of code during this is that if you have a college age friend or child or girlfriend or boyfriend, tell them about the summer of code. It's a great way to get introduced to open source software development. On average, for the last five or six years, although we've been running them for nine years, we've generated about 3 million lines of code for open source projects via this program every single year. And it pays. So it's like a little internship where they do it wherever they are. And we have a high school flavor of this, too. So any of you who might have high school students in your lives, tell them about the Google code and so that they can become one of us in this world of open source software. And I just saw a person in a penguin suit walk by in the conference hall back there. That was a little freaky. Because it's like, anyway. So 2005, late 2004, I was asked to take part in a study about how people get to their information and what they do with it when they get it at Google, where it was a nuclear at the time. I was brand new to the company. And we mapped out everything. We mapped out how mobile worked, how codecs worked, how people got to the internet via browsers and all the rest. Because we had this idea in our head that there was this platonic ideal going on on the internet where people could go basically to any website they wanted to go to from any sort of platform they were on. And that was an ideal. And it was an ideal that gave birth to Google in this sort of very fair and yet very, very competitive environment. And how did that happen? How did the internet happen? And we all know the story of the internet and servers and all the rest. And if you look at it now and if you look at it through the history, what was happening was you had multiple open source options competing with actually multiple commercial offerings to satisfy their end user or the developers who might use a tool like say Apache, which was competing at IIS and other options, or Sendmail, competing with Qmail, competing with Alwa, competing with Lotus Notes I guess at the time, which I know you're all huge fans of. So I don't want to forget about it. And that was a joke. Not because it was bad. It was very innovative for 1992. But let me continue. But if you looked at the way people were competing for users, it was when you had this platonic ideal of multiple open source projects competing with each other and commercial options competing too, that ended up resulting in a great environment for us to exist in, for Google to exist in. And so we're like, OK, what does 2005 look like to the smartphone user? At the time, smartphone honestly meant Symbian and maybe a bit of RIM, and a little bit of Windows CE slash Windows Mobile at the time. At that time, Symbian was around 84%, 87% of the market, and the rest was RIM and Windows Mobile. And we'd gotten wind about the iPhone and what people were thinking about that, and we knew it would be a very powerful competitor in the space. But I know that none of you have seen an iPhone. It's made by a company called Apple. And that was also kind of a joke. Just keeping you rolling here. But we also knew that to get Google onto these phones at the time was pretty grim. You had to use WAP, you had to use WHTML. And often, to get your website into these browsers, you would have to cut a deal with a carrier, a handset manufacturer, and it was bad. And basically, we knew. You didn't have to be brilliant. And a lot of people were like, it's the year of mobile, man. And it's like, wow, welcome to 1994. You didn't have to be a genius to figure out this is where we were going, that people are going to be carrying around mobile phones. They're going to be accessing the internet on them. Who knew? Well, everyone knew this. This wasn't brain's rocket surgery. So we wanted to make sure that they could have the same sort of experience they had on the desktop with multiple browsers competing to access multiple servers on the internet on their phones. But there was no real open source option that we felt would engage the user. And there were a couple of open source projects out there trying to do it. But nothing that we were convinced would actually do well. So we came up with Android. And we're like, OK, what would a good open source option in the mobile operating system space look like? Well, we knew it would have to be able to access the internet and get web pages just like a normal browser would. It wouldn't have that kind of gatekeeping mechanism where it would only go to those websites that were approved by the carrier. And we went a little further because when we were thinking about licensing and why we picked the Apache License as the bulk of Android, we knew that it would have to have a good patent grant attached to it. So that people would not be worried that Google would come and rent and seek against them as they implemented their Android phones. And so we came up with Android. This was the G1. That wasn't the one I gave away four years ago. I gave away the one right after this. And you didn't get one. So thanks, Jim. That makes people love the person talking. So they're like, you could do it really, no kind of. And so this is what we launched. We wanted to basically provide in some ways a new minimum that people would expect from cell phones. That no one would ever again think, you know what we need to do? We need to make sure that WebsiteX pays us before we allow you to access them. We were anticipating problems with net neutrality even this early on the mobile experience. So we basically wanted to make it really hard for people to compete in a marketplace of restriction. And so now where are we? So we're in this place now where we have multiple open source competitors, although most of them are Android forks, frankly, and multiple commercial operating systems all competing for user desire. And what that means is since the user really, really wants to get to their websites, they really want to get to applications too, that the cell phone operating system vendors can't basically compete by restriction. And we can't do it. Apple can't do it. And the rest, we have to provide a minimum level of freedom that allows companies like Google to continue to exist and yours to. So where are we today? For Android devices, we passed the billion devices shipped mark. And those are just the ones that have activated with Google. That doesn't include the many, many, many millions of devices from alternatives like Amazon, solid alternatives like Amazon's Kindle line, and others. And it's more than a million plus devices activated every day. And those are all running Linux. And Jim's talked about it, but the reality is that Android success has been very good for Linux. I think it would be very, very hard, for instance, for the Raspberry Pi to be as successful as it had without the system on chip device support that Android brought. So we work really, really hard to ensure that that continues. So for instance, just in the last month alone, we've released three different versions of Jelly Bean into the Android OpenSource project. We have KitKat on deck. I'm not going to say coming soon because I don't know the exact date of the KitKat launch for the Android Open Source project. But we keep on releasing software. And while it's more of the punctuated equilibrium model, it gets better every year. And four years ago, when I talked with people, they were still accusing us of operating a fork and wake locks from Satan and all of these things. But we stuck to it, and we kept working with the mainstream kernel community to make sure that all of our changes were frankly cohesive of what they were doing because we knew what shipping at the time, hundreds of thousands of devices in a week, would turn into. And we knew that if we could just keep as close to the main line as possible, it would be good for us and good for Linux. And that's where we are today, which is it's a pretty good place to be. So how do you know it's actually open source? Now this is a really important thing because we see people talking about open platforms all the time. And it personally bothers me. So let me just give you a little bit of a shorthand. So how you can tell something's really open source, something's really made from free software. Is somebody other than the company who made it shipping it? In competition with that original shipment. So for instance, in Android, you have Android phones coming out of actually, I have this on the next slide. Oh, did I go forward like 12 slides? It's like, anyway. So you have phones right now from Android, not a phone. You have the tablets from Amazon. You've got phones from Facebook. You've got phones from Yandex, Baidu, and a bunch of other shippers. You have what I call fractional phones, which is when a Chinese manufacturing organization will say, you know what, we have an overnight shift, and maybe they ship Windows Mobile in the day, and they're going to ship Android at night. I mean, you see these things all over the place. And oftentimes, a number of these platforms, they never say word Boo to Google. They ship their own app stores. There's many, many flourishing app stores out there. They ship their own everything. And so this is one way you know that Android is actually released under a real open source license. And you'll also notice that we're not out there suing them for doing it, because we used a patent granting license that would preclude that. And it's also not in our nature. But the reality is, if we're optimizing for even an evil Google, which doesn't exist currently, you would know it. So when somebody says that they're shipping something open source, you should ask yourself, how are they actually doing it? You know, we even went so far as the robot up there in the upper right-hand corner. I'm sure you all have seen this all over the place. That was released under the Creative Commons by attribution license from the very, very beginning. And it doesn't have a cute name like Andy or Larry or something like that. It's just called the bug droid, because we weren't super creative about our naming. But even that was released. So when I bought a phone case from my recent phone, it actually came in a box. And the box actually had the licensing information for the bug droid, which I'd never seen people comply with, frankly. It's very rare to see that, because they're like, hey, I've got a dancing robot figure in my commercial. And they're not going to say anything. And sometimes you can track it down. But yeah, it's funny, because my job is licensed compliance. So sometimes I'll email a manufacturer and say, you know, it'd be great if you put this bug droid licensed under the hello, hello. So yeah, it's kind of interesting. But we did something a little different, too, in the creation of Android that a lot of people don't think about. How many of you are familiar with the intense system? And Android, just raise your hand. Yeah, so about an eighth of you, maybe a 16th or a 24th. Anyway, so what it does is basically when you have an application that's going to send an email, it tells the operating system I'm going to send an email. And that persistent comes back and says, well, here's how you're going to do it. And then you say, you know what, I'm going to install K9 Mail on my phone. So you install K9 Mail. The next time you go to send an email, the operating system is going to give you that screen. Which program do you want to run to send your email? And you can pick just once, or forever, whatever your choice is. Suppose you want to switch over to K9 from, say, Gmail. So you click that. That's the intense system in action. And if you add another email program, or if you reset it, it'll ask you again. And it's not just for things like email or going to a browser, right? Oh, by the way, we're the only platform that allows you to swap out the browser, too, which is nice. You can do it with lock screens. You can do it with home screens. You can do it with the SMS application, the dialer, contacts, anything. You can create your own intents. So suppose you have some app, like WhatsApp or whatever, that has a new kind of intent that it also wants to do. Well, you can do that. And we did this because we also knew that one of the ways that people would express themselves is by not allowing you to replace competitive offerings, right, like a browser, like a map system. So in fact, a lot of people don't know this. But when you use Chrome on an iOS, you're really using a wrapped Safari rendering engine with some Chrome bits around it, because we are not allowed to ship our own browser on that platform. Same thing is true with Windows Surface and a bunch of other platforms. So we didn't want to be that company, right? And so we built that in from the very beginning in Android. So yeah. Android's been ported in a bunch of places. It's funny, with the drama that's gone on with RIM, for instance, we've seen them say, well, we're going to ship a phone that can run Android applications. And the way they did that is they took the Android open source project and they just put the frameworks on top of their operating system. And they've recently said they're thinking about shipping RIM on top of Android as a home screen type replacement, I guess. I'm not privy to their plans because they don't talk to us. Why would they? They don't have to. Similarly, you've seen people take things like the old web OS operating system and port it to run on top of Android. And if you look at a lot of, frankly, some of the very exciting work that's being done with Firefox OS and a bunch of Edge and the rest, you can usually find some Android there, whether it's the driver layer or the service flinger layer or something else. And that's pretty great, honestly. And when I look at like, so I finally got to handle a Firefox OS phone when I was in Brussels recently. Not because it's the only place you can get it. I ran into a guy. And it was really pretty cool. And I was like, oh, you know, it's great to see your software get out there. And Android has been created so that that works. And it's been ported to non-arm platforms rather natively. So it runs natively on MIPS, ARM, x86, and a bunch of other platforms. And if you're creating a new platform, it's actually pretty easy to do. So often, usually the biggest trouble people have is getting video to work right and the other sensors, because of the vagaries of those businesses. So yeah, so that's where we are today. We have a place worth over a million apps, over 50 billion of them downloaded as of July of this year. And we're shipping the Moto X phone out of Motorola. But there's lots of great phones out there, the Galaxy S4 and all the rest. And they're all running open source software. Either software that we've released as open source, or frankly, your code that we've brought into the operating system in the form of the kernel and elsewhere. So that's sort of an update. And that's five years. And I said nine years because we did that study back in 2005. But you know what it comes down to is that the Android today is actually a really powerful thing. And I want people to understand what that power is. And it's really been informed by really what Apache did and what Sendmail and Qmail and all the rest did. And because of that understanding and because of what open source brought to us, and because of frankly the head start that using an open source kernel and the open source tools brought with it, we were able to make Android work for Google, but also for all these people who don't like Google. So it's a pretty great thing. And that's where we are today.