With Google I/O 2026 underway this week, Andrew sits down with Matthew McCullough, VP of Android Development Experiences at Google, to talk about the AI evolution happening across the Android ecosystem. Matthew shares his insights on why developers are rapidly transitioning into agent orchestrators, why CLIs are cool again, and how tools like AI Studio have rolled out a massive welcome banner for anyone to actively participate in the creation process. Finally, the two explore the future of mobile user interfaces and how the latest Android 17 developments are stripping away legacy friction to seamlessly get users straight to the good part.
Show Notes
- Events:Catch up on the latest announcements from theGoogle I/O 2026 Keynotes.
- Tools & Platforms:ExploreAndroid Bench,Google AI Studio, and the new features coming toAndroid 17.
- Developer Hub:The central hub for guides, updates, and resources:developer.android.com.
- News:Read more updates and insights directly from theAndroid Developers Blog.
- Follow:Matthew onLinkedIn
Transcript
(Disclaimer: may contain unintentionally confusing, inaccurate and/or amusing transcription errors)
[00:00:00] Andrew Zigler: Today we have a very special guest joining us, Matthew McCullough, the VP of Android Development Experiences at Google. And Matthew leads the engineering teams responsible for the foundational tools and platforms and architecture that millions of mobile developers and honestly, millions of just people across the world rely on every day to bring order to their lives, to get information when they're not at home, when they are at home, and everywhere in between.
[00:00:26] Andrew Zigler: And today we're gonna dive into the massive evolution that's happening right now in the Android ecosystem. You know, it's Google I/O, and we're gonna be getting an exclusive look at what is coming down the pipe, but also understanding the shifting engineering strategy from a leader at Google, how they're thinking about aligning to these new challenges, because as we all know, the device is the frontier. The more that we can bring models and technology and AI into the-- exactly, into the, the, the hands and the wristwatches and the [00:01:00] ears of everyone around us, the, uh, easier and better that all of our ships are going to rise. So this is a really high-stakes kind of environment to be building for. Matthew, we're so excited to dive into this chat.
[00:01:11] Andrew Zigler: Welcome to the show.
[00:01:12] Matthew McCullough: Well, thank you very much, Andrew, and I'm so excited too when, as I said, um, even in our prep for this, that any time somebody says, "Would you like to talk about development, and specifically Android development?" They don't usually get to finish their sentence before I've said yes. So, uh, I'm really passionate about this space, and I happen to also have a job in it, which is just kind of like a second part of the luck.
[00:01:33] Andrew Zigler: Yeah, that's just the bonus on top. You know, that's-- I, I would be obsessed with the things I talk about even if I didn't have my job, but then getting paid to do it is just like, "Oh, this is amazing." So I'm glad all your planets are aligned. And I, I wanna start by talking about the current landscape and how you're seeing things change in the development pipeline and what your team was-- really had front of mind, top priority.
[00:01:55] Andrew Zigler: What did you need to address and to make possible to bring to the stage at Google I/O, [00:02:00] uh, to make AI-powered development easier for Android devs?
[00:02:03] Matthew McCullough: It's a great question, and it requires us to just do a very quick look back at history. I always like to point to how we got here and then where we're going as a contrast. I think three to four years ago, pick your line on this, if we said, "Hey, we need to be thinking about tools that, uh, don't just serve humans," you'd, you'd get the most quizzical, confused possible look from an Android dev.
[00:02:26] Matthew McCullough: And now, if you don't bring that into the conversation, you get a quizzical look like, "Do you even read Reddit, Hacker News, or the like. And so this is a huge change in three or four years. Some of you might even argue that's like a year and a half, so even more compressed. So I think the top-line thing that we should think about most, Andrew, is that anything that we're building this year, the thematic change that we're telling our devs is if you still want to do this in a hands-on UI button inside the IDE way, we have you.
[00:02:55] Matthew McCullough: If you are on your journey because companies are at different stages of this adoption and [00:03:00] evolution, if you are working towards an agentic ecosystem, whether it's in a chat window to just get answers or whether it's in actual, in a, uh, short-term agentic flow to get some code recommendations or it's long-running tasks, we are building everything for a dual mode, both the humans as well as the agentic flows this year.
[00:03:18] Matthew McCullough: So you can expect all the announcements to cover both of those two modalities.
[00:03:22] Andrew Zigler: So you're delivering it for anyone in the way that they want to work. Because the idea is that your ecosystem is so big that you have to provide all of these entry points that are, seamless and easy, but also intuitive and interchangeable across a huge ecosystem. Like, that's a really big challenge to do that mental shift.
[00:03:41] Andrew Zigler: You said it happened in a compressed timeline. I think that speaks to, like, the rapid cycle that we're all in. And so I, I'm curious too, like, what do you-- when you say as somebody a- from a perspective at Google, like, that companies are in these different stages of adoption, like that couldn't be more true.
[00:03:58] Andrew Zigler: We cover that all the [00:04:00] time here. We see people at all ends of that. What are, do you think, those bounding ends that you're really building for? Like, what do you think are the most forward-thinking kinds of ways that people are using your technology right now? But then also, how are you making sure that the folks way back at the starting line are still getting started?
[00:04:15] Matthew McCullough: I'm gonna, I'm gonna answer in an upward kind of swing. So for your last part to your first part in reverse order here. I think I can do it. From the kind of entry point to this, there are definitely still some of our app devs that are, are basically using this as an answer engine. They're looking for help me look up documentation, how do I, kind of little tips over on the side.
[00:04:35] Matthew McCullough: And that's okay because that's, that's where they're comfortable, but they are including it. I do wanna note, yes, for bounding conditions, I think our-- of our respondents, of our advisory board, of our developer population, we really don't hear anybody saying, "Oh, I'm not using it at all." But there definitely is an entry tier, which is just more kind of the Q&A chat kind of approach, giving answers.
[00:04:55] Matthew McCullough: I think we've watched gravity move over the last six months, and I would really say the inflection point was [00:05:00] either November or January, if you wanted to give it a specific calendar month in where it flipped from, "Oh, I'm getting good answers. This is helping me go faster instead of pop over to the browser and look up stuff in forums or the like, or chat with my colleagues," to over to, " It's helping me get work done."
[00:05:15] Matthew McCullough: And that's a pretty big shift. Answers and tips are nice. We could get that at the, you know, coffee station at our offices. Actually moving work forward Is a radical change in a loop because it means that you're staying right inside here. That little circle of a loop got much tighter. And then I think at the frontier, you asked me to give you boundaries.
[00:05:34] Matthew McCullough: That's kind of where the, the middle of that bell curve is right now. But on the frontier end, uh, we are starting to get some of our developers for some leading applications saying that the vast majority of code they write is done in an agentic fashion, and they're changing the actual role in how they participate to be more one of orchestrate, make a plan, describe the product deeply, think more PRD, overview-- uh, give [00:06:00] oversight and overview to the output of the agent, but less that kind of like inspect the curly braces, angle brackets, and quoted strings kind of inside.
[00:06:09] Matthew McCullough: Um, that's kind of thin, heavy and thin in the three that we just covered.
[00:06:14] Andrew Zigler: Right. So really what you're seeing is, is, is something that, that definitely gets, I think, echoed a lot about the new skill set of engineers and the kinds of tasks that they are doing, because there was this dramatic shift. Um, I experienced it too, where, you know, you come back from like winter break and suddenly you feel like, " Oh, this stuff is actually kind of doing a lot of my job now," and it's interesting but also kind of scary, and you try to get closer to that and understand it.
[00:06:38] Andrew Zigler: And in doing so, you realize that you play such a pivotal role in preparing all of the stakes and the pins as they fall, that there are so many new skills to build and figure out to get more out of this, and it becomes like a new level of learning, uh, and building. So, uh, how are y'all thinking about, uh, the new generation of builders?
[00:06:57] Andrew Zigler: Like, what kind of skills do you think are gonna be [00:07:00] most important that people right now, since the top of the year, um, have been using to get, um, more work done?
[00:07:07] Matthew McCullough: There's a, there's a funny thing that you talk about, uh, kind of new and frontier, but at the same point in time, you know, I've, I've been in this, you know, coming on three decades. There's a humor to this too, that CLIs and text user interfaces are cool again. Uh, I have so many feelings about this. Like old me is proud of new me or new me is digging up skills from old me.
[00:07:30] Matthew McCullough: So there's lots of fun with that. But I think what it actually comes down to is that some of the fundamentals, this is the comforting piece in a very disruptive time, is that some of the classic foundational good practice approaches that we've had are still durable. This is-- For all the headlines, this is not necessarily throwing out everything and starting over.
[00:07:51] Matthew McCullough: It's If you ask me, it's kind of like coming back to core longstanding good principles. Code review is now more important than ever. There's a humor in [00:08:00] this. Like, you want to make sure what's going in is known, understood quality. You're adding to the quality of the code base, not diminishing it over time.
[00:08:07] Matthew McCullough: Second, you want highly composable tools. And one of the concrete examples, uh, that I, I wanted to mention to you is to point at Android CLI. You know, some of our audience is like, "Wait a minute, didn't, didn't you have that a ways back and then we went to IDEs?" But we actually brought this back in a new and, and an updated fashion so that you can manag-- uh, you can manage builds, you can create new projects, you can manage your SDK installs from this.
[00:08:31] Matthew McCullough: And CLIs are very usable, like from a, an efficiency typing perspective, but they're also very usable for agentic workflows as well. So really what I'm seeing from this from the beginning of the year is make sure that you have composable tools, make sure that there's a command line or API equivalent interface, MCP being all the rage, and that you're serving, uh, that kind of curve.
[00:08:52] Matthew McCullough: We have such a big developer community, three million devs that are active here, that we can't leave any part [00:09:00] of that curve out. We can't just say, "Oh, sorry, we're no longer serving." So we've got to make it user interface, um, viable for the folks that are still there. But we've definitely got to make sure that it's accessible for the people pushing the frontier, 'cause they're also the ones who tend to lead in innovation on the platform.
[00:09:15] Matthew McCullough: We've got to do something for the move fast, write it mostly in agentic loops, 'cause that's kind of where the most innovative applications are often built as well.
[00:09:23] Andrew Zigler: Yeah, we have to support those really tight loops that people find and they manage to get these like really huge gains that we can't even envision now. Because like as we get these
[00:09:32] Andrew Zigler: new things, we get new platforms to stand on that let us see new levels of innovation, and folks maybe underestimate the level of exponential kind of, learning and opportunity that's available if you do kind of unlock those things with like what you said.
[00:09:46] Andrew Zigler: It's an invitation to go back to, go back to basics, go to the primitives, uh, and find composable ways to, uh, work and like a com- a newly imagined way of like how maybe it was [00:10:00] done in the olden days. Because really what's happening is we're still,
[00:10:03] Matthew McCullough: it is.
[00:10:05] Andrew Zigler: In this painful place where, you know, the, the agent and the LLM can speak machine code and be in the machine world, and that's where, where they live in, but we have to live in user space, right?
[00:10:14] Andrew Zigler: So we need to get like as all the way down to the bottom of the tank in the user space. Like we spent all of these decades building up like E's, and then web UIs, and then apps, and then like all this level of abstraction. And then, and then you build all... We're working up there, we're constructing up there.
[00:10:32] Andrew Zigler: It's like, you know, a floating city. But like we have to go down and, and like find those bare metal basics for working with the technology while still being able to interface it in a natural language. And obviously, the terminal is on a resurgence. I'm back in the terminal now for all of my work, um, which I never thought would happen because while I've used the terminal plenty, I was never like, "Oh, I'm gonna be in Vim.
[00:10:54] Andrew Zigler: I'm gonna be like in Tmux." But now that's like exclusively where I spend my [00:11:00] time in it. Yeah, at the same time, that in- that was an invitation to strip away complexity that once I got rid of it, I realized wasn't helping me, and I could find new ways of working. And so while folks, I think, get tempted in an agentic era to add complexity, to add, um, newer things on top, I think that it's also like to go to your stack and rip things out and find a way to simplify so that you and it can have a lingua franca that's much more portable
[00:11:32] Matthew McCullough: Andrew, I've got three things you hit on, on such stuff that's, that's like so important to me. One, there was an element in there you almost hinted at it, which is like prove it, though. There's like a higher bar with so much coming at us. There's like marketing, meh, prove it. Is, is kind of like a new mantra to some degree, even if it's not said explicitly.
[00:11:50] Matthew McCullough: And one of the ways that we're trying to do this to say like, "Is this helpful? What can you strip away? What can you keep?" Is Android Bench. Just to, uh, give a little pointer at this. We kept hearing like, "Which [00:12:00] model is, is the best, you know, for Android development?" And everybody has an opinion on the internet and YouTube comments and Reddit and every other place.
[00:12:07] Matthew McCullough: But then let's, let's go to numbers. Let's measure. Let's let people repeat this themselves. So we came up with an open benchmark, uh, a couple months ago and released it, and you can actually see the evals. It's working on real code bases. You can see the change, and we provide those scores on a monthly basis.
[00:12:23] Matthew McCullough: So that hits two of the items you raised. One, give us hard numbers, let us measure. Two, let us verify it-- Maybe one A, let us verify ourselves, and two, strip away unnecessary complexity. Hey, pick the winner. Cut just to that. Use that for your loop. Get to the tool that works. You don't need, you know, seventeen.
[00:12:40] Matthew McCullough: There's one other element of this too that's, um, that's interesting as well because you talk about the complexity. We're shifting just even over the last six months from managing single long-running agentic tasks to now managing them in parallel. And you talked about the role change as well. We've got to adapt this inside our IDEs and our text user [00:13:00] interfaces because six months ago, spin it up, grab some coffee, come back, see if it did a good job, do the code review.
[00:13:06] Matthew McCullough: Insufficient for the current era. Now we need a queue of these. This one's working on a bug backlog, this one's working on a feature, this one's, you know, prototyping something forward-looking that we may not, you know, decide yet to land in the application. And those are all running on the side. So we've got user interface evolution that's also happening inside the IDE to be able to manage these type of things in, in parallel, uh, these long-running tasks as opposed to a one-to-one.
[00:13:32] Matthew McCullough: And that goes back to your other element about the role change of even an Android developer. They are effectively getting a promotion to a manager, even if that is a manager of agents, not necessarily a manager of people. And that pushes one last time to draw the full circle. If you're a newly promoted manager, even of agents, simplicity and stripping to the essence of is the only way you'll survive the change.
[00:13:55] Andrew Zigler: Exactly. Otherwise, you're just gonna get clobbered in all of the noise and the meta of everything [00:14:00] that's hanging around working with all those agents and all of these disparate systems and tools. You're back in this context switching hellscape that we were all trying to escape from. And so, um, it, it's
[00:14:10] Matthew McCullough: Y-
[00:14:12] Andrew Zigler: simplify.
[00:14:13] Andrew Zigler: And like you said, you-- it's everyone is now in a manager role. You know, you made a comment earlier about, like, you're no longer going in there and manicuring, like, the, the curly br- bra- braces and whatnot inside of the code. That's completely true. It's like we've talked about that extensively of how you now the responsibility is to get deeply aligned about what needs to happen and then have a system to enact it with these loops and, and levels of orchestration. I wanna get your mindset on that first part, you know, getting aligned to do stuff. I think that's the biggest challenge for biggest company- for, like, large companies right now that have a lot of resources, have a lot of people, have a lot of opinions about what they need to do in order to be successful in an agentic era.
[00:14:52] Andrew Zigler: How, uh, do y'all think about, uh, getting deeply aligned on something before you throw agents at it? Or do you just [00:15:00] throw agents at everything and then get aligned after you see what they do? Like, how do you think about it?
[00:15:04] Matthew McCullough: This is an interesting question, and we can speak about it from, like, the Google perspective. Then I can pull out a, a nameless large partner that works in the Android space and then kind of blend the two. So starting from the Google angle of this, I think at scale, it causes us to refocus back on being great at coordination.
[00:15:21] Matthew McCullough: Um, once again, you know, the ebbs and flows, but we're back on coordination. And I think about what are the highest fidelity vehicles, and this changes from company to company, but what are the, what are the assets? You can answer this for your-yourself, Andrew. Like, what artifacts, what forms give you highest information, highest quality signal for the lowest cost of actually reading?
[00:15:41] Matthew McCullough: Is a twenty-page PRD where you really get awesome understanding and efficient point in time? I don't know. Some of us are starting to question that. But have you ever had an opinion? I think most of us have, so I'm gonna presume here. When you play with the prototype, for some reason, all of us who worked in software have a lot of opinions really [00:16:00] quickly about playing with the prototype.
[00:16:01] Matthew McCullough: You should move this. This should be second in the flow. This is not performant enough. Don't reveal this too early. I need this to actually be pre-populated. So I, I suggest that as it's gotten cheaper, at least from a time, maybe not from a dollars perspective, but from a time perspective, to put together prototypes, there's a real push.
[00:16:19] Matthew McCullough: This is a bit of an insight into our customer advisory board and the like, but there's a real push for working touchable prototypes over that same amount of time or energy being invested in long documents that are pros. And I think that's super cool because in some ways that's the thing that our users, if we're thinking user-centric software, are going to have in their hands anyway.
[00:16:41] Matthew McCullough: So you, you talked about being grounded. This is grounding ourselves in what they're gonna have, what we're making for them much sooner in the cycle than we would've under the previous era. We're changing the IDE. I mean, the mapping for this then is Google. What are we doing? And then back to our partners.
[00:16:59] Matthew McCullough: We're [00:17:00] changing the IDE to make prototypes like this super easy. AI Studio, which people are like, "Wait a minute, I didn't think that's Android Studio. Did you misspeak?" No, I spoke correctly. AI Studio is gaining increasing capabilities to be a prototyping surface for applications. Stay tuned for more and more over there.
[00:17:18] Matthew McCullough: We're making it easy to take existing assets, web applications, React, Native, Flutter, iOS applications, and bring those over as starting points. So instead of, you know, if we're talking a platformer kind of game, you're not starting here anymore. We're just letting you, dare I say, Donkey Kong or Mario jump up to like platform seven.
[00:17:36] Matthew McCullough: That's your new, that's your new start to the game. You can just start at that point. And then what does this mean for our users? What-- Say again?
[00:17:43] Andrew Zigler: said earlier. That's the composability, going back to what you said earlier, 'cause you're letting people bring in what they need to work within the ecosystem.
[00:17:50] Matthew McCullough: just jumping to that layer. That's per-- That's exactly right. And then just to finish on that, I think what our, what our audience is seeing is, okay, as we bring these tools to bear, they're having to [00:18:00] rethink where do I have an asset? Where do I have a prototype? Where do I have a screenshot?
[00:18:04] Matthew McCullough: Where can I empower somebody who doesn't have software engineer or SWE in their title to help me get to platform seven? So now it's actually more inclusive software development because it's not just limited to a couple of letters in your particular title at your company as to whether or not you can participate.
[00:18:21] Matthew McCullough: And I gotta say, like, if that was the only thing we got to mention in this whole podcast, that's the most exciting piece. I love software development. I love people being in it. I love building stuff, and we may have just unlocked the biggest participatory welcome banner for people to come in and actively, actively participate in that act of creation.
[00:18:41] Matthew McCullough: We're trying to do it through our tools. Back to you.
[00:18:43] Andrew Zigler: I'm just excited about this as you are. I see the same opportunity for companies, and you're exactly right that the economics about, um, getting invested in your product and putting yourself in the perspective of your customer, your user, um, has never been simpler. You called out to obviously maybe it is simpler in a [00:19:00] q- in terms of time versus cost or, or whatever the case.
[00:19:02] Andrew Zigler: But the fact is that folks can get aligned around the same point and see the same thing and play with it and immediately develop those opinions. Those outside of this, a traditional s- software engineering role can develop those opinions. And now everybody, everybody in a
[00:19:18] Andrew Zigler: company can have a hand at building the product, at being customer obsessed, at understanding how people really, uh, use the output of their organization.
[00:19:28] Andrew Zigler: Because now the ability to collaborate is one bounded by natural language. It's one bounded by alignment and by cohesion, and by knowing where the North Star is, and that's all the stuff we, we should have been doing the whole time.
[00:19:41] Andrew Zigler: It's just that we were always distracted by having to deal with like, you know, a manicure and the curly braces.
[00:19:47] Andrew Zigler: And so, um, I completely agree that the companies that wake up and realize that it's about, um, bringing everybody into that, that builder conversation and, and then getting everybody, uh, in the same stakes, [00:20:00] those people are going to create, um, just like these cohesive builder-obsessed organizations. And the upskilling, I think, is gonna be amazing as folks are able to collaborate.
[00:20:10] Andrew Zigler: You'll get designers that will ship stuff. You'll get, uh, product managers that are in customer calls. You'll get engineers that are in customer calls, because now engineers need to be closer to the customers than ever, uh, before. So I'm really excited to see the kinds of things that come out of the announcements, how-- what people take from the developments and build with it. Uh, is there anything else burning in your mind about
[00:20:34] Matthew McCullough: Oh.
[00:20:35] Andrew Zigler: at Google I/O that you just have to squeeze in in our few more minutes left?
[00:20:38] Matthew McCullough: There's always a bunch, but one comes from something that you mentioned. So specifically, it's part sparked by something you just said before, which is around what are we building? Do we kinda get to rethink this from first principles? And then specifically the phrase natural language. And I think, you know, you were unpacking it with me a little bit around the, the developer side.
[00:20:56] Matthew McCullough: What are we prompting our agents? What are we telling them to build? But there's [00:21:00] an and to this that's pretty important too with Android 17 announcements, uh, having just come out of, uh, from the Android show and then more, more to come at IO. I think that consumers' expectations of how they use these devices are also rapidly evolving, which then dot, dot, back, dot, dot, back means that developers and product managers also need to be updating how they're thinking about what they're building as well, not just how they're building, which has been a lot of the focus of the show.
[00:21:29] Matthew McCullough: I think some of the rethinking that we should think about is like a couple of simple prompts just to get folks started. Number one, where is the input modality ripe for changing again? Design is a super easy one to at least get the conversation started, whereas before we'd, you know, do pixel drags and changes, and we'd point arrows to like color that needed to be changed.
[00:21:51] Matthew McCullough: What if you just had a mock and you're like less, less purple, more blue, slightly more, you know, modern sha- deeper shadows. I'm looking for [00:22:00] the aesthetic. That's usually pretty easy to get out of folks, but then when you ask them to mechanize that onto the screen, that's where the time takes. Maybe that's an input modality that can change inside a design application that somebody was building.
[00:22:12] Matthew McCullough: And then second, you have different modes. People are on the run. They're on a, uh, a moped. They're on a-- in a car. In those moments, input on a small keyboard typing characters is not optimal as well. Do you have like a simple choice menu that could be voice-activated A, B, C, D, E? Can you actually have full open prompt text input?
[00:22:32] Matthew McCullough: These are things. And then lastly, where is interface baggage? In wizards, you know, we've lived since the ' 90s with this of like step one, press next, step two, and so on. Where can you just kind of express all of the needs in your application? So as you're thinking about your application design in kind of a one-shot fashion, and Android 17, I think is a great example of this.
[00:22:56] Matthew McCullough: We put a lot of automation in that's kind of moved the [00:23:00] operating system and platform forward in this way, and I'm excited to see apps meet that moment too, where you're just like, can you just do the-- I, I know I'm aggrandizing, but, uh, a little bit like how excited I am about this. But can you just do this thing?
[00:23:11] Matthew McCullough: Just go figure out how, figure out which apps and tools, figure out which step in the flow I want this to transact, to buy, to purchase, to search for. Just get me to the result. Leave out all the middle part. Just get me to the really good part. Um, that's kind of the exciting future of software and mobile.
[00:23:29] Matthew McCullough: Just get me to the good part and leave out-- And you, you take all the digital laundry and chores
[00:23:34] Andrew Zigler: Exactly. It's like we have to remember as developers and as software leaders like that, you know, just as much as we have this huge opportunity to build with this new level of technology and to unlock all of these huge gains and do things we couldn't before, our customers and our users have the expectation and the knowledge and understanding of what this technology is and what it can do and what other peop- your competitors are doing with it.
[00:23:57] Andrew Zigler: And so there's an [00:24:00] expectation that is like, "Oh, just do it for me. What do you mean I have to do a manual wizard?" Any level of friction is going to alienate. In a world where your taste is an immediate action for things that you want and do, it's gonna completely change how people interact with software.
[00:24:15] Andrew Zigler: I think right now we're still thinking in like a, an old way of how people would onboard for stuff. So I'm, I'm excited to see what kinds of experiences people build with the technology, especially like you said, to make it work in all sorts of modality. And I know we're at time here, Matthew, but you know, I just wanted to ask where could folks go to learn more about what we talked about today and follow you and, and, and keep in touch with the stuff you're doing?
[00:24:38] Matthew McCullough: Well, I think the core part of this is developer.android.com. Uh, that's the best. Uh, DAC, as we friendly refer to it, um, here inside the Android community. We keep that refreshed. It's not just API guides, but this is opinions, blog posts about the latest releases, how-tos on somebody using these latest tools, and then even occasionally explainers as to why we're going in this direction.
[00:24:59] Matthew McCullough: 'Cause I'm a big, I'm a big fan of explaining, like, why things are changing and then giving you the how to make it possible is kind of a yin and yang to this. So that is the central place for it. Uh, and I would also just say, like, encouraging our audience is super exciting. If you wear a dev hat or a PM hat, if you identify as a SWE or a UXer or the like, um, this is actually a pretty exciting opportunity for you career-wise, because I think these things that even Andrew just unpacked here at the end give you the opportunity to change business outcomes, stickiness, user retention, higher user acquisition through the funnel, higher completion rates, uh, upsells and purchases.
[00:25:41] Matthew McCullough: Like, there's so much business goodness that, um, quite frankly, you just got, like, a free upgrade in your role for the leverage that you can have at your company. But Andrew, simply thank you. We covered from CLI to thirty years ago, transformation of the industry, curly braces, user impact, even [00:26:00] finished with a business hat.
[00:26:01] Matthew McCullough: I don't, I don't know that there's opportunity to pack anything more into these twenty-seven minutes.
[00:26:05] Andrew Zigler: I know. What a journey. It's been a great chat, and we're gonna get all of those links in the show notes as well for our listeners, so be sure to check out the Google I/O keynotes, and we'll be following along here at Dev Interrupted as well. Matthew, thanks again for coming on the show.
[00:26:18] Matthew McCullough: Thank you, Andrew.
