❌

Reading view

There are new articles available, click to refresh the page.

#235 – Rob Pugh and Tony Arcangelini on Bringing Podcasting to Jetpack

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, bringing podcasting to Jetpack.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there.

So on the podcast today we have Rob Pugh and Tony Arcangelini. Rob and Tony are longstanding members of the Automattic team with extensive backgrounds in marketing, product, and software development. They’ve spent years building tools for creators, writers, podcasters, and everyone in between, and now they’re fully immersed in WordPress’s evolving podcasting capabilities.

If you’ve been looking for ways to run your podcast from your own WordPress site, this conversation is for you. Rob and Tony dive into the new Jetpack podcasting features, and why they made the leap from WordPress.com’s basic audio offerings, to a more robust, integrated solution, within Jetpack.

They talk about what makes WordPress and Jetpack such a powerful home for creators. The ability to bring your newsletter, blog, podcast, and all your content and communication under one roof, all while keeping ownership of your data.

We talk through the advantages of keeping your content out of walled gardens like Substack and Patreon, and the value of flexibility, whether that’s adding WooCommerce to sell merch or customising your site’s look.

Rob and Tony breakdown just how easy it is to start your show. Drop audio into a post, set your category, and let Jetpack handle the rest. From distributing your RSS feed to major podcast apps, to sending out newsletters, and automated social posts. They also get into how integrations with PocketCasts and Jetpack AI make content creation, transcription, and distribution smoother than ever before. Plus how WordPress is open Foundation promises you’ll never be locked in.

If you are a creator wondering how the next generation of podcasting fits into the WordPress ecosystem, or just want an easier way to launch and grow your show, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well.

And so without further delay, I bring you Rob Pugh and Tony Arcangelini.

I am joined on the podcast by Rob Pugh and Tony Arcangelini. Hello, both.

[00:03:23] Rob Pugh: Hey, how’s it going, Nathan?

[00:03:24] Tony: Hello, Nathan.

[00:03:25] Nathan Wrigley: Nice to have you both with us.

Today we’re going to be talking about something which is actually genuinely dear to my heart because we’re going on about podcasts. Yay!

I’ve been in the podcasting space for decades, and WordPress has been the place where I’ve done it every single episode. I’m entirely indebted to WordPress for the capacity to do all of the podcasting I’ve done. But I’ve never done it inside of Jetpack, because until recently, I don’t think that was possible. So that’s what we’re going to talk about today.

First of all, I’ll just go round the houses. I’ll start with Rob. Would you mind giving us just a quick potted bio of what it is that you do over at Automattic, Jetpack, whatever it is that you want to mention.

[00:04:04] Rob Pugh: Yeah, so I’ve worked at Automattic for seven years. I’ve been in marketing and now focused more on product, but I like to do a bit of everything. And I work mostly with tools for people that create stuff. So podcasts fit right in there, and we are excited to build out this feature.

[00:04:19] Nathan Wrigley: Nice. Thank you. Tony.

[00:04:21] Tony: Yeah. I’ve also worked for Automattic for about eight years now. I do software development, and so I have had firsthand in building everything that we’re talking about today.

[00:04:31] Nathan Wrigley: Okay, thank you very much.

Now, just before we started recording, I was on the call with Tony before Rob joined in and you labored the point, not labored, but you mentioned that you were in the sort of creator side of Automattic. I didn’t know that existed, but that to me is about the most interesting bit of any organization. You know, the bit where the musicians come, and the poets come and the writers come and the podcasters, and the videos and the YouTubers, and all of that come. I think that’s really interesting, and I didn’t realise there was a wing of the business entirely aligned to that. But I guess I’ve been schooled, and now I know. So podcasting definitely comes under that banner.

Okay so I didn’t know this existed, and I think it didn’t exist, but maybe Tony can redirect me a little bit here. Podcasting in the WordPress space, I think you could do more or less everything that we’re about to talk about inside of wordpress.com until recently, but now it’s shipped inside of Jetpack. First of all, I’ll just send that one to Tony. Is that true? Is this all like a port of things into Jetpack from .com?

[00:05:32] Tony: I’d say it’s a little bit more than a port. So we built a very basic feature of podcasting in WordPress.com to offer WordPress.com users. It was very basic. It was just the feed. Basically what you see in the free offerings right now. The ability to drag an audio into a post and for that post to then become a podcast episode. And then we had a curated RSS feed that was available. And then very basic, the core basic iTunes tags that are needed to be able to be picked up by these apps.

That existed there. It was a bit outdated. It hadn’t been touched in a long time, and so we felt like it would be a great tool to leverage for creators. Giving them a better product, something that would be useful with stats and the ability to manage your episodes and all of that. And we figured if we were going to put all this effort into it, that we should probably make it more widely available. And so Jetpack was, I think, the natural fit for us.

[00:06:26] Nathan Wrigley: Yeah, I’m kind of curious how it’s ended up in Jetpack and not just its own plugin. Is it because you’re leveraging the other things that Jetpack can do? Are there sort of dependencies, if you know what I mean, where, okay, it just makes sense because Jetpack already does that piece of the puzzle, and we can just build over the top of that?

Or is it just the brand recognition, the fact that you’ve got an email list that you don’t need to convert and they can just toggle a switch and automatically have got podcasts? What was the reasoning on putting it inside of Jetpack and not just its own thing?

[00:06:54] Tony: I would say, at least from an engineering perspective, there’s stuff that’s in it that is exclusively within Jetpack. So, the ability to do stats, that’s a hard thing to do when you’re having a self-hosted site, to be able to watch and see what apps are actually touching those download files, and then be able to aggregate them all in one place and then give them back to you in a way that’s easy.

So, at least from an architectural perspective, Jetpack was the easiest because it allows us to leverage some of the endpoints that are already there, and use a lot of those tools.

But then secondly, I think it’s also from an overall product perspective, being able to put it alongside other features like newsletters. Where you can have a newsletter, you can be able to take it into the reader. Have this one episode that now spans across multiple different avenues to be consumed, is I think, also another big benefit in putting it into Jetpack. As opposed to just dropping another, because there’s already a lot of plugins out there, a few big plugins that you can grab for free that do podcasting.

[00:07:56] Nathan Wrigley: I think one of the big bits that I realised early on in my podcasting journey was that you’re not really just trying to create an audio feed. It’s more useful as a podcast if you’ve got this kind of wrap around thing. So like you say, you’ve got a home which is yours, AKA your WordPress website. But also things like the capacity to send out an email if people are interested in subscribing, and they don’t necessarily have a podcast player that they use all the time, but they do want to consume your content.

The fact that they can subscribe to a newsletter, you click publish, that newsletter automatically drops in their inbox. It just makes sense that all the jigsaw pieces that a podcaster needs, it feels like WordPress has had forever.

And there is some part of me which is curious that it’s taken this long to come into the, let’s say, .org side of WordPress. Because all of the different parts, the newsletter, the RSS feed, the blog posting, all of that stuff has been available. It just kind of never got joined up. It strikes me as odd because people have moved over to Patreon, Substack has become this whole thing over the last decade. And really it felt like WordPress had that audience a decade ago.

Maybe it’ll claw it back. I certainly hope it does, but it feels like a lot of people have left the WordPress ecosystem for their podcasting because that stuff wasn’t available. Rob, maybe you want to take that one? It’s not really a question, more of an observation.

[00:09:16] Rob Pugh: Yeah, there’s a lot to unpack there. I agree. I think we were a little late in bringing some of these tools to wordpress.org. But I think we’re seeing the renewed focus across the technology space on ownership.

WordPress has remained the best way to do that. And for us to be able to offer these tools to users. It shows everyone that you can, as you said, own your blog your newsletter, your podcast, together. And it does make sense for us to offer all of these tools in one space.

I like to think of it going back to the origins of WordPress, and we started as blogging, everyone getting your thoughts out there and sharing them. Meeting new people, engaging and creating communities. And podcast is just another medium. We provide that for the written word, so of course we should try and provide that for the spoken word as well. So I do hope that we can show people the benefits, and the ease of having it all together and come back and give us a try.

[00:10:11] Nathan Wrigley: Yeah. I think for me at least anyway, that argument is embedded in my soul. The idea of owning your own content on the web is really important. It’d be interesting to see in the year 2026, 2027 and going forward how much that stuff really matters. I’m just curious, in the age of AI whether people still want to own anything at all. But it’ll be certainly interesting to see.

[00:10:30] Rob Pugh: Sorry, yeah, weigh in on that. I think we’ve seen it over decades and comes in waves. When social media started it was really exciting, and people ran and then saw some of the pitfalls, and they start coming back.

And then recently you mentioned Substack, and I loved Substack when it started. It was a space for some serious dialogue, and a place for writers engage. And then over time, well, we need that VC money, and now it’s basically another social media site. And you realise, oh I don’t really own my data, I just own a Substack, and how valuable is that? And it’s coming back.

And I think AI, it’s becoming even, the cycles are quicker now. AI’s incredible, I use it all the time. I use it to help come up with prototypes for how to best display this podcast product. But, you’ll see quickly that you don’t own anything, and you need to have a home like WordPress. And you retain ownership of your audience, and your data and your posts and your podcasts, and that’s, I think, never going to go away, and AI’s only going to reinforce that for people.

[00:11:23] Nathan Wrigley: Yeah, I think one of the curious things as well is if you want to do anything outside of the normal that the platform will allow, so let’s take the example of Substack. There’s a limited subset of things that it can do. The bedrock of what it does I’m sure is excellent. I confess I’ve never used it, but I’ve seen many people deploy it for their own podcast, so you know, it must work.

But the minute you want to stray outside of those boundaries, and you want to do something a little bit different, I don’t know, you might want to sell some merchandise or something like that. Well just pop WooCommerce on top of your website and you’re off to the races.

Or, I don’t know, you want to have a different flavor in the way it looks at Christmas or something, well you just adapt the theme. And I’m, imagining good luck doing that over on these proprietary platforms. I don’t know if that’s possible, but it certainly would be a lot harder than it would be on the WordPress side I would have thought.

[00:12:08] Rob Pugh: For sure the customisation expanding is all very important, but to me even more important is just that it feels like Substack is just another platform that’s changing the rules on their people midstream, and if you don’t like the direction of. Like tried it before and it was nice to have a non-social media site to have serious writing and reading of other serious authors, and now I’m getting short form reel videos on my homepage, and I didn’t sign up for this.

And if you’re a creator over there, you might be stuck. How do you port your audience over? It’s technically possible, so they say they’re open, but it’s a pain, and people don’t want to leave. And if you’re actually successful, they take 10%, which is great when you’re zero paid subscribers. But, there’s people paying $10,000 a month to Substack.

[00:12:48] Nathan Wrigley: They take 10%?

[00:12:49] Rob Pugh: 10% no matter what, which is great if you’re free, but if you have 100 paid subscribers paying you $10 a month, suddenly it’s insane. Like it’s a terrible deal and people feel stuck. Like WordPress even, wordpress.com, jetpack, if don’t like those rules, we can’t change them too much. You can go to any of the other great podcast hosts, or plugins.

[00:13:09] Nathan Wrigley: Yeah, I guess that’s a curious thing. And then you can embed those on your WordPress website and just carry right on as if nothing had happened. Yeah, that’s a really interesting point.

[00:13:15] Rob Pugh: Exactly.

[00:13:16] Nathan Wrigley: So from what I’ve seen, it looks like a really simple solution to implement. What I mean by that is, as a user of your product, it seems like you’re basically doing a bunch of stuff which as a WordPress user you would be simply doing anyway.

Like, you create a post. I don’t know if there’s a requirement to have a special custom post type for a podcast, or if you can just use regular posts. You go in, drop some audio in, and kind of you’re off to the races. Type some text and what have you.

Is it really as simple as that? Is it simply a case of make a post, drop some audio in? Or is there some stuff that you need to do in advance to prepare your podcast? So I’m leading you up the garden path with that question. Tell us how it works. What do you need to do in order to get started? How much work is involved?

[00:13:59] Tony: Yeah, I think that’s it. There are a few settings that are naturally required for starting a show. So you have your typical art for your show. You’ve got to set your categories and things like that in a setting. But then once that’s all set up, all you do is you create a new post, drop in the audio. We actually have an audio block as well, like a podcast episode block that will pull in a lot of the newer, fancier, podcasting 2.0 markup as well for you to do like chapters and things like that. And then that’s it.

As long as it’s within the category, it’s not a custom post type, it’s just a regular post. And then we are able to differentiate between an episode and just a post by two things. One, is it in the designated category that you set? And two, does it have the audio or video? We also have a few video files that we allow as well, and that’s it.

[00:14:46] Nathan Wrigley: Okay, that’s really neat. So you can use a regular WordPress post, but if you don’t assign it the category, let’s say in this case I’ve named it podcast, let’s go with that. If you don’t assign that category, it’s a regular post. Nothing off that tries to smuggle its way into your RSS feed, which would be attempted to be consumed by a podcast player. It just doesn’t go in there.

The minute I assign the category of podcast, drop in some audio, then it’s in that separate RSS feed. Dear listener, if you’re not familiar with that, basically a podcast is an RSS feed. That is literally what it is. Your podcast player is just consuming a bunch of text, which is an RSS feed, and interpreting that in a certain way with images and the audio and what have you.

And so that’s it. That’s all you have to do. Configure the settings, put a piece of audio in, assign the category, click publish. You’re done.

[00:15:35] Tony: Yep, that’s all. That’s all it is. I think the harder part is trying to come up with the titles and filling out the show notes. And, I have a friend who I got to start a podcast when we were working on this product, and he was using it, giving us feedback. But then, it’s like I looked at his podcast, and it was literally just like episode one, and it just, he’s like, “That’s the hard part, is coming up with all of the other stuff.”

[00:15:53] Nathan Wrigley: But you have Jetpack AI as well, don’t you? So there is an opportunity, I would presume, to lean into that. If you were to write a corpus of text that went alongside the, I don’t know, the audio, it could be a transcript or what have you. Presumably then Jetpack can go sift through all of that, and suggest some sensible titles if you really can’t be bothered to work out a title for the podcast episode. But then again, does it have the capacity to do things like trawl through the audio and transcribe and things like that? Or is that a bit roadmap-y still?

[00:16:20] Tony: Yeah. So that was one of the things that we wanted to work on was the ability to transcribe. And, because we have the privilege of working closely with Pocket Casts, we have, a lot of fancy tools that they have built already for their podcasting platform that we were going to try and leverage for the podcast show.

[00:16:39] Nathan Wrigley: Pocket Casts is an Android, iOS, and, it’s a web player as well. It’s a place where you go download onto your phone or what have you and play them. I have it, I use it every single week, and I’ve noticed that whether a transcript is made or not, Pocket Casts actually makes one.

[00:16:54] Tony: Yep.

[00:16:54] Nathan Wrigley: So if I ship a podcast without a transcript, Pocket Casts magically has a transcript. So I don’t know where that voodoo is happening. But that technology, you can then do double duty on that. You can take the technology they’ve built, use it in the Jetpack side of things, and do the transcription. Okay, that’s neat. Sorry, I interrupted. Apologies.

[00:17:11] Tony: You’re good. Yeah, that’s all of it. That’s, it right there.

[00:17:13] Rob Pugh: I think that’s a great segue into Pocket Casts, which in our opinion is the best app to listen to podcasts. The best platform. And one of the really cool things we were able to do with, because we work closely with Pocket Casts, is when you are distributing your podcast. We pick, just to start, the six biggest ones and hold your hand on submitting to them. But Pocket Casts is actually Automattic. Automattic, you can spell it with one or two Ts. And, if you click the button, it just is uploaded to their network It takes minutes, and it’s, some of the other ones, we hold your hand, but it’s a little annoying, and some of them can take a couple days, like Apple, to approve things. But, Pocket Casts just works. I don’t know if you want to add anything on that magic, Tony.

[00:17:52] Tony: Yeah, it’s very simple. It’s like right off the bat. If you already had an episode recorded, you could start a new website, upload your first episode, set your settings, and be on Pocket Casts, I would say, in less than an hour, honestly.

[00:18:06] Nathan Wrigley: Yeah, because you’ve got that tight integration.

[00:18:08] Tony: Yeah. It doesn’t say anything for the website configurations, which I’m sure would take more time, but at the very least, if you wanted to get your show out there, it’s a pretty instant approval.

[00:18:17] Nathan Wrigley: I think podcast players. If you’ve never run a podcast, there’s this whole dance that you have to do. The first time you ever try to release an episode, and that is to get it set up with the distribution channels that are popular. So I’m thinking of things like Apple Podcasts, and YouTube Music, and Amazon, and the list goes on and on. There’s, dozens of them, some more important than others. I think probably Apple is probably the biggest one, and maybe Spotify and some others come in second and third place.

But you have to do this thing where in some cases you have to go and get an account, and there’s really no way around that. Do you do some of that heavy lifting though? Do you make it easy for people to understand how to do it? When I did it, like 10 years ago for the first, and thankfully, only time I really ever had to do it, it was a case of going out and Googling it and reading things. But do you have that information in the UI to make that journey a little bit easier, reduce hours to minutes perhaps?

[00:19:07] Tony: Yep, we have a button.

[00:19:08] Rob Pugh: So there’s a distribution tab which lists the, all six like you mentioned, Amazon, Spotify, Apple, Pocket Casts, Podcast Index, which covers a whole bunch of minor networks. And I’d love to one day have it be fully automatic like it is with Pocket Casts. But some of them you need actual partnerships with these, Apple or Spotify to make that happen, and we haven’t prioritized putting a business person to go start a relationship and that.

So we will organize them for you and try and give clear instructions in our documentation to how to do it. But there is just a button then when you’re looking and it shows you the status of it, if it’s in or not.

[00:19:42] Nathan Wrigley: Okay. So you click the button, do the necessary thing, and then it will report back to you whether or not that has been successful. It’s a bit of a strange vestige really of the internet from way back when. It feels like in this day and age of everybody using APIs to connect to this, that, and the other thing.

But companies like Apple seem to be very unwilling to let that bit of their system be wide open. You’ve got to sign up for an Apple Creators account. I forget exactly what it’s called, but you log in and then you submit your RSS feed. It really doesn’t take that long, but you still have to do it.

[00:20:12] Rob Pugh: Yeah.

[00:20:13] Nathan Wrigley: And I think they’re doing it because they get to see from the inside out, how popular your podcast is. And I don’t know, maybe they can monetize things from their end. I’m not really sure how that works.

[00:20:23] Rob Pugh: It’s really another example of the closed internet.

[00:20:26] Nathan Wrigley: Yeah.

[00:20:26] Rob Pugh: Which is terrible. Why does Apple and Spotify need to be closed? So I think with having your podcast on WordPress with Jetpack, wordpress.com, and being in Pocket Casts, great. Then you’re, in the more of the open garden which is a better place to be.

And the cool thing with our stats, you can see who’s coming, like how many people are listening to your show on Apple versus Spotify versus Pocket Casts. So you know if you’re not getting any from Spotify, then you don’t even need to be there. Of course though, it helps with findability to be everywhere, so we want to give you that option.

[00:20:56] Nathan Wrigley: Yeah, at the end of the day, it all boils down to an RSS feed, which if it’s on your WordPress website presumably contains your domain name, forward slash, I don’t know, feed forward slash something maybe. So your RSS feed is going to be fairly short, probably very on message.

Does it work that way or does it have some sort of Jetpack or, I don’t know, WordPress.com thing in it? Because when you go to these other platforms, it’s typically platformname.com/randomstringof12characters or something like that, which is very hard to read out in your podcast. But the way you’ve got it built, it sounds like the sort of thing that would trip off the tongue. So you know, wptavern.com/podcast. Put that into your podcast player of choice and you’re done. I’m saying all of that like that’s true, but I don’t know if it is.

[00:21:40] Tony: Yeah, that’s it. Slash feed at the end.

[00:21:43] Nathan Wrigley: Okay.

[00:21:43] Tony: Because it is an RSS feed, yeah.

[00:21:45] Nathan Wrigley: That’s still fairly straightforward. But again, that’s a nice bit of branding, isn’t it? And, I think that’s really good.

Linking it back to the branding. We touched on this a minute ago, but if you haven’t started a podcast before, it may not be entirely obvious that you do want those other things like a newsletter, and like the ability to post to socials, and it feels like you’ve got the complete wraparound solution for that.

Because as your podcast grows, which let’s hope it does, then you will probably wish to have a relationship with your listeners via an email newsletter. You probably will wish to be posting on social media. You probably will wish to do all of these different things. So social posting, newsletter, RSS feed, WordPress as the sort of custodian of all the text and the images and the videos that I put in. Is there any other secret sauce that we’ve missed there? Is there any other sort of unique binding that Jetpack brings that we haven’t mentioned there?

[00:22:37] Rob Pugh: I’ll take it back first to like why we started this, and decided to build this, and I think you’re exactly right. First we found there are lots of WordPress.com and Jetpack users who have podcasts somewhere else. And that’s fine, but they were forced to because we didn’t offer it, and that really makes sense. Why would you need to go somewhere else?

So you say today, our goal in creating it was twofold for the people creating the platform. It should just be as easy as possible. Podcasting and writing is hard enough. You should focus on that. Let us handle all the difficult stuff.

Like you said, you need to, have a newsletter and a podcast and a blog and own all of it, and why can’t you do that with one publish event? And then from the consumer’s side of like consumer of content, some people want to listen to only podcasts, and some people want to read on a blog or, say, the WordPress.com reader. Shout out, go check that out if you haven’t in a while.

And like me, I prefer to actually read stuff in my email inbox, like a old weirdo. It shouldn’t be, you should let people consume however they want to, and it shouldn’t be a lot of extra work for you, the host, the creator, to manage all of these things on different platforms. Just have it be as simple as possible, and that was really our goal. And then, yes, exactly what you said with all the other Jetpack stuff. Social media is a great one. Gosh, you could go on and on. Performance, security, basics.

[00:23:46] Nathan Wrigley: Yeah. And it binds to, you said it just then, and it binds to the one publish event. So when I began my podcasting journey you end up with, like all these Zapier connections and different ways that, I don’t know, a webhook which goes off here and does a particular thing because you want it to be posted to this social network. With this, once you’ve got all of the bits and pieces configured, you click publish.

So you know, you do your audio, you write your text, you do all of that in a draft state, upload the audio. But the moment you click publish, the newsletter goes out, the social media posts go out, and all of that just happens automatically. And you don’t have to think about it. And they’re already there in your website.

It’s not like you have to do much. You just toggle, actually we should talk about that. You have to toggle the Jetpack podcast setting on, and presumably the newsletter setting, and yada yada, all those other things. But once you’ve toggled all those things on and got them set up, every time you click publish, all of those dominoes fall, and everything just happens on autopilot, which is really nice.

What do we need to toggle on? How do we set it up? How expensive is it? Let’s start there.

[00:24:50] Rob Pugh: I’ll talk about the pricing and then Tony can talk about the, the toggles.

[00:24:54] Nathan Wrigley: Excellent. Yeah.

[00:24:55] Rob Pugh: Yeah, we talked a bit about the pricing. I think that Automattic has always had a really generous free tier across its products, and it made sense for us to continue that. So you can today go to WordPress.com and start a blog for free.

It’s going to have some ads on it, but it’s free. You can have your newsletter sent out unlimited sends for free with unlimited subscribers, and unlimited podcasts for free. That’s like, amazing deal. We don’t get enough credit for that, but cool.

But we did build some compelling things to make you hopefully want to upgrade, or as you grow your podcast, you’ll find valuable. I think the stats are really cool. To me, all of the essential stats and none of the unessential stats, which if you’re an advanced podcaster might not be as good as you’re looking for. But, for most novice users, you just want to know the basics.

Anything beyond that starts to feel like Google Analytics, like, I’m lost. So just give me the basic. Are they coming on Apple? Where, how many listeners to which episodes, and where in the world are they coming from? Which refers, like which sites are they coming from? That’s a great starting place for me.

Help with distribution, the episode list, having a clear place for all your podcast episodes, the podcast block, really cool. And on WordPress.com too, we include the audio hosting once you upgrade. It’s not on Jetpack yet, so we’re waiting to see if, because we offer a similar thing for VideoPress, shout out best video hosting for WordPress.

[00:26:09] Nathan Wrigley: Yeah, there’s VideoPress will handle the video side of things. That’s becoming the thing, by the way. I’m sure you know that. But in the podcasting space, I went to The Podcast Show in London, about four months ago or something like that. Everybody’s talking about video.

[00:26:22] Rob Pugh: Yeah.

[00:26:23] Nathan Wrigley: And so that being bound into Jetpack as well is just another string to your bow. I’m just going to segue slightly. I think Pocket Cast does a pretty good job of doing things like HLS video. I could be wrong about that, but I’ve got a feeling it does.

[00:26:35] Rob Pugh: They even hook up with your Apple TV now, so you can watch and listen and yeah.

[00:26:40] Nathan Wrigley: Oh, so this is really clever and completely out of the realms of possibility just a year ago. So you could be listening on your headphones whilst you’re out walking the dog on your podcast player, so you’re only listening to audio. And you come back in, put your Apple TV on, turn on the Pocket Cast player, and it will seamlessly drop you right in the video at the exact moment where you finished the dog walk. It’s so clever and so neat. I love all that stuff.

[00:27:08] Rob Pugh: The future is so cool.

[00:27:09] Nathan Wrigley: Yeah.

[00:27:10] Rob Pugh: I love it.

[00:27:10] Nathan Wrigley: Okay. So Tony, how do we switch it on? Is it genuinely one toggle in the Jetpack settings, or is there a little bit more to be set up?

[00:27:17] Tony: Yeah, more or less. There is one toggle to turn the module on. And then once it’s on, you go to Jetpack and click on the podcast option, and then from there, there should just be one button that is to set up your show.

And all it really requires is you either creating a new category or selecting a category. And this is, as we were talking about before, the category feed that is going to be taken over from there. And then you technically are done. But it’s advised that you fill out all of the other base settings, and we walk you through all of the ones that are required by the podcast show apps, to make sure that you don’t get blocked by Apple or Spotify for not having the necessary settings.

[00:27:57] Nathan Wrigley: If I’ve been a podcaster for a number of years and I’ve got, I don’t know, a back catalog of 100 episodes or something like that. How do we handle that? How do we bring in previous episodes? And is there like an automated way of doing that or do I have to go and refigure 100 brand new pages on my WordPress website?

Is there any heavy lifting done there? Let’s just deal with the audio first, just the RSS feed and the audio. Is it a simple case of dropping the old podcast RSS feed in and you’ll capture all that audio and it’ll be on the Jetpack side of things? Let’s do that first.

[00:28:28] Tony: That’s a great question. I am not super familiar with the Core WordPress importer, but I believe that if there is a valid RSS feed with the normal RSS style tags, like enclosure and things like that, you should be able to import your RSS feed. Depending on how it’s configured on your current host, directly into WordPress. I’m not too sure what that would result in exactly. Especially because there’s a lot of different hosts out there, and it’s not like there’s one standard format for exporting your content. But yeah, that should get you part of the way there.

Then I think in the future, we’re really looking to start targeting some of the major current podcast hosts to be able to configure a migration flow to be able to come from those places to ours, in a more seamless way, albeit whatever sort of export they can give you or, whatnot. But I think that’s still on the horizon.

[00:29:27] Nathan Wrigley: Yeah, it’d be really nice to, let’s say I have 100 episodes and I’ve got, it’s over on whatever, hosting platform X over there, for my podcast audio feed. It’d be nice to be able to just suck in all the descriptions, and all the titles and have them be created as WordPress posts with the category assigned. So that essentially my WordPress site with the click of a button and the wait of an hour has suddenly got 100 posts of the podcast type all ready to go. And then, that’ll sit inside my SEO sitemap and all of that kind of stuff. That would be really interesting to be able to do, I think.

[00:29:58] Rob Pugh: Yeah, I think we will try and have that in the future. We usually do try and make importing, especially from closed platforms, super easy. An example, another Substack. We have an amazing Substack importer. They’re not a big podcaster yet, but they, do have some, and we can look at adding that. But if you have all of your newsletter on Substack, you click a button and we bring over your whole, build you a website, bring over all your posts, all your subscribers, even paid subscribers. We seamlessly transfer it to the Stripe account. Everything we’re building, we’re just trying to make it super easy for people to own your data, go wherever you want. We encourage movement in and out, wherever you want to go, it’s up to you.

[00:30:31] Nathan Wrigley: I suppose that then leads me to this question, which is, and you’ve probably just answered it. You’re not holding people behind some sort of paywall here. If people try Jetpack Podcasts out and they decide, “You know what? I really want to go the other direction. I want to maybe go back to where I was, or just move to a new host,” or what have you. You’re not holding any of that hostage, are you? You can take it and run with it and put it somewhere else?

[00:30:52] Rob Pugh: Yeah. Yeah, absolutely not. Like that’s the, I think, one of the fundamentals of WordPress. You should be able to move within WordPress and out as much as you want. I will say that this is a new feature that me and Tony have built. Just because something doesn’t exist in a super streamlined way, doesn’t mean it’s our intention to lock you in. So please reach out and we’ll happily help you migrate off if that’s your wish.

[00:31:15] Nathan Wrigley: So I’ll just let you know, dear listener, that there’s several URLs which rather than read them, because in many cases they can be quite long. But one of them, which is really easy for me to say, I might as well do that one, is wordpress.com/podcast. That’s probably the easiest one. Oh, and maybe this one as well, jetpack.com/support/jetpack-podcast. There’s several more.

[00:31:38] Rob Pugh: Let me jump in. Let me sorry, Because as of two days ago, we now have jetpack.com/podcast.

[00:31:45] Nathan Wrigley: Oh, okay. That’s way better.

[00:31:46] Rob Pugh: We just relaunched the entire jetpack.com site, which is cool. You should go check it out. Yeah, so.

[00:31:51] Nathan Wrigley: Again though, that, so what was that? Jetpack.com/podcast is kind of the home for all of those bits and pieces.

[00:31:56] Rob Pugh: Yep, exactly.

[00:31:57] Nathan Wrigley: In which case, go there. That’s where you’re going to find all of the bits and pieces and I presume, when things are, adapted and modified.

[00:32:03] Rob Pugh: Yeah, the way to think about it’s still for some people confusing about Jetpack. So if you would like a website, the best WordPress hosting, then go to wordpress.com/podcast, and we’ll host your podcast for you. And if you want to host somewhere else, that’s great. Go host your WordPress site somewhere else, then go to jetpack.com/podcast and we’ll get you all set up as well.

[00:32:23] Nathan Wrigley: In which case, I will say thank you Rob, and thank you, Tony. Thanks so much for chatting to me, both of you.

[00:32:28] Rob Pugh: Yeah. Thank you Nathan.

[00:32:28] Tony: Yep, thank you.

On the podcast today we have Rob Pugh and Tony Arcangelini.

Rob and Tony are longstanding members of the Automattic team, with extensive backgrounds in marketing, product, and software development. They’ve spent years building tools for creators, writers, podcasters, and everyone in between, and are now fully immersed in WordPress’s evolving podcasting capabilities.

If you’ve been looking for ways to run your podcast from your own WordPress site, this conversation is for you. Rob and Tony dive into the new Jetpack podcasting features and why they made the leap from WordPress.com’s basic audio offerings to a more robust, integrated solution within Jetpack. They talk about what makes WordPress and Jetpack such a powerful home for creators: the ability to bring your newsletter, blog, podcast, and all your content and communication under one roof, all while keeping ownership of your data.

We talk through the advantages of keeping your content out of walled gardens like Substack and Patreon, and the value of flexibility, whether that’s adding WooCommerce to sell merch or customising your site’s look. Rob and Tony break down just how easy it is to start your show, drop audio into a post, set your category, and let Jetpack handle the rest, from distributing your RSS feed to major podcast apps, to sending out newsletters and automated social posts.

They also get into how integrations with Pocket Casts and Jetpack AI make content creation, transcription, and distribution smoother than ever, plus how WordPress’ open foundation promises you’ll never be locked in.

If you’re a creator wondering how the next generation of podcasting fits into the WordPress ecosystem, or just want an easier way to launch and grow your show, this episode is for you.

Useful links

Pocket Casts

VideoPress

The Podcast Show London

Podcasts on wordpress.com

Podcasts on jetpack.com

💾

#194 – Devin Walker on Leading Jetpack: Challenges, Vision, and the Future

Transcript

[00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley.

Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, leading Jetpack, the past, the challenges, the vision, and the future.

If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players.

If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox and use the form there.

So on the podcast today we have Devin Walker. Devin’s journey in the WordPress ecosystem spans many years, with experience in development, design, marketing, and customer support. He is best known as the co-founder of GiveWP, which he built and scaled before it was acquired. During his time there, he touched a variety of prominent WordPress brands, including iThemes, Kadence, LearnDash, and The Events Calendar.

Today Devon is starting a new role leading the Jetpack suite of services at Automattic. It’s a position with hefty responsibilities as Jetpack powers millions of WordPress sites, and integrates deeply across

I talk with Devon about why he took on this challenge. The divisiveness and complexity surrounding Jetpack, and his vision for refocusing the plugin and simplifying its user experience.

We start by hearing about Devon’s extensive WordPress background, and the choices he weighed up when deciding to join Automattic.

The conversation quickly moves to the scope of Jetpack, its evolution, the struggle to be a jack of all trades master of none, and the recent efforts to bring greater focus and polish to key features like forms and SEO

Devin gets into the organizational changes at Automattic. How Jetpack’s development teams now collaborate more fluidly with other product teams, such as WooCommerce, and the balancing act of shipping improvements to a 4 million strong user base without breaking things.

AI emerges as a massive new frontier, and Devin shares behind the scenes insights into Jetpack’s current, and future, aI capabilities, giving us a glimpse at content creation, block building, and how AI might reshape user and developer expectations in WordPress.

Throughout we hear about Devin’s approach to product marketing, and the need for more of it, the importance of listening to user feedback, and his plans for a more coherent and compelling Jetpack experience.

If you’re a WordPress user wondering where Jetpack is headed, what’s working, or how AI fits into the future of site building, this episode is for you.

If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you can find all the other episodes as well.

And so without further delay, I bring you Devin Walker.

I am joined on the podcast by Devin Walker. Hello, Devin.

[00:03:34] Devin Walker: Hello.

[00:03:35] Nathan Wrigley: Very nice to have you with us. Devin has a shiny new job. Up until a few weeks ago, Devin was not an Automattician, or at least I don’t think you were maybe at any point in your past. But you are now an Automattition, and you are doing what?

[00:03:47] Devin Walker: My official title is Artistic Director of Jetpack, but basically product owner, or head of Jetpack. Whatever you want to call it.

[00:03:55] Nathan Wrigley: So when it comes to Jetpack, the buck stops with you. I guess that’s a pretty important role in the WordPress space over at Automattic. And if anybody hasn’t heard of you, I suppose it would be important to just lay the groundwork, who you are, what you’ve done in the past.

I know you’ve got a long and storied history, but just maybe a one minute little short bio telling us who you are and what you’ve done.

[00:04:14] Devin Walker: Yeah, sure. I’ve been using WordPress for all sorts of things, development, design, blogging for 16 years now. Really made my name known, I guess you would say, with Matt Cromwell. We co-founded GiveWP together, and we grew it for seven years, from late 2014, all the way through 2021, which then we were acquired by Liquid Web and was there for a little more than four years, and touched a lot of brands from there, from the iThemes rebrand to SolidWP, to Kadence, to LearnDash, Events Calendar, and of course GiveWP as well.

And left there in early August of this year, 2025. I also built WP Rollback throughout the years, that has quite a few active installs. So yeah, that’s a bit about me. Developer, design background, definitely well-rounded with marketing and supporting customer success.

[00:05:05] Nathan Wrigley: So you’ve had a lot of experience working with WordPress products, which I guess is what you are doing over at Automattic, because let’s just call it head of Jetpack, just to make it easy. It’s a curious title, by the way. Artistic Director is kind of a really.

[00:05:17] Devin Walker: You know Automattic loves that title.

[00:05:18] Nathan Wrigley: Yeah, they love that, don’t they? But head of Jetpack, and obviously you’ve got a long and storied history kind of growing products and making sure that they succeed and customer support and all of that kind of thing.

And I feel like Jetpack, no matter what time you dropped in on Jetpack in the last, let’s say decade, I feel that half of the community felt like it needed a lot of love.

And I’m just wondering when you were interviewing for this position or when this position was offered to you, I don’t know how that process went, but what the kind of broad brush strokes are in what you’re hoping to do over there?

We’ll get into the weeds very much, but roughly speaking, what’s the scope of the new job? What is it that you are hoping to do in the next three, six months, years, something like that?

[00:05:57] Devin Walker: Yeah, so when I left Liquid Web, I wrote a long, well, not long, but wrote a blog post about closing that chapter of my career and really being open to what’s coming next for me. I knew that I wanted to stay in WordPress and I was having fun building on just my own products at the time, and having full control of everything, the whole lifecycle of a product.

And I did some work with Matt in the past on some of his nonprofit sites with Give and the VIP team and the concierge at Automattic. And so Matt called me up one day, you know, we stayed loosely in contact over the years, and said, we have some interesting opportunities here at Automattic, and one of them that I think you’d be great at is Jetpack. And in my mind I’m like, Jetpack, this is a doozy.

But, you know, he said, give it some thought, work on your own pace and give me a call back whenever. And so I thought about it for a week and, maybe two weeks, talked to my wife about it. And really it comes down to, I was either going to start my own business again, and try to grind again and strike lightning twice, like GiveWP, and see if I could grow something and eventually sell it in five to seven years, which takes a lot of hard effort, sacrifice, money. A lot of your own money, and almost no guarantee. And the WordPress marketplace has changed so much that it’s not immediate impact right away, and you’re really out on your own.

It worked well once, but I was in my early thirties, just turning 30, and now I’m 40. So life’s changed quite a bit for me. And Jetpack, it is a very divisive product, we can get more into that in the future, but really it came down to having that impact. Being at Automattic, a company that I’ve respected since I came into WordPress, and always wanted to go behind the scenes and work as an Automattician, so going full circle from where my career began to the opportunity and the challenge.

If I succeed at this, it can really open some other doors at Automattic. I’m head of this product, which touches almost everything on Automattic as far as the WordPress business goes. I just thought about it long and hard, talked to Matt about it, and made sure I would have the levers for success also. And that’s what made me choose to say yes and come aboard.

[00:08:08] Nathan Wrigley: It is kind of curious because if you just discount all of the stuff you just said about, you know, wanting to fight and build your own product up, I can well imagine how grinding that can be, and there’s no guarantee of success. It could be a real failure.

But stepping into a huge product, I’m going to put my neck out on the line a little bit here and say, I actually can’t think of a product or a plugin, let’s go with that, in the WordPress space that tries to cover as many bases. Covered by any organisation, whether that’s a third party development team or what have you, I can’t think of one named product that tries to cover as many bases.

And the fact that it’s divisive and I’m sure you’ll get into this, but there’s lots of room for improvement, I’m sure you’ll agree. You are walking into something exactly as you say, where there is a chance of great success here. If you pull this off, and you pull the right levers, and in six months time, a year’s time, two years time, the arc is going in the right direction, there’ll be measurable success. So really interesting.

So what was the bit, when you had that, oh, moment, what was the bit about Jetpack which made you think long and hard about it over two weeks, as opposed to immediately saying, yeah, I’ll do it? There must have bits about the project, Jetpack as a plugin, whatever it may be. What were the bits that concerned you?

[00:09:18] Devin Walker: Well, I’ve used it over the years on and off. I wouldn’t call myself a power user at all, but I come from the community, 15 years of being in the community. I’ve gone to, I don’t even know how many WordCamps and always kept tabs on it, especially when, I don’t know when it was. I think it was pre 2020, when they did like a bit of marketing push that Jetpack does donations now, accept donations with Jetpack. And it was through Jetpack forms. I didn’t know that at the time, so I installed Jetpack. I was like, where’s donations? You’ve got to find your way through this tangled web. Oh, it’s part of forms. Okay, let’s go into forms. Oh, it’s like a template now and you have to, the connect flow was terrible. The whole flow was not a great experience.

And the donation form itself, I was like, oh, we have a pretty serious competitor now with Give, we’ve got to like step our game up. But then I left that, I was like, okay, don’t worry about it guys, we’ll be fine now, nobody’s going to use this. That’s where that, oh, moment comes from where like, jack of all trades, master of none type of thing.

[00:10:15] Nathan Wrigley: Yeah, I think probably encapsulates it perfectly. It’s kind of jack of all trades and master of none. So I’m just going to rattle off some of the things that I know it does. I’m probably missing quite a lot here. So for example, you know, it does stats, think something like Google Analytics, it will offer that for you. Backups. It will do protection. It will do speed and optimisation things on your website. Social sharing. It will do forms. There’s VideoPress thrown in there as well. There’s a whole bunch of stuff that I’ve missed out there, but it really is encapsulating a lot.

And the jack of all trades, master of none, bit kind of fits because when Jetpack came out, I’m imagining it was a really, it was probably at the forefront of many of those things. The things that it did, it probably did as well as everybody else. But now, 10, 15, whatever years later, there’s now been real amazing products delivered by third party developers that have become the standard of forms, of backups, of speed and optimisation services and what have you. And so Jetpack now has to kind of compare itself to the very, very best. And I think that’s hard. You know, for one plugin to try and be the best at everything. Nigh on impossible, I would imagine.

[00:11:16] Devin Walker: You’re right. Like, we can’t compete. I’ve been preaching focus for the last, since 2016 when our mentors said, what the heck are you doing all these other plugins? Sell them off or sunset them and only focus on Give. And that’s when our business started taking off. Now, what I’m trying to do is bring focus back into Jetpack.

We do some things very well, and we need to make sure that, I’m not going to say we’re going to compete on the level of a Gravity Forms for our form solution. It’s going to come very close. And for 98% of the users out there that need forms on their website, I think it’ll fulfill that need.

For that special 2% that need like calculation fields, they need super customised form capabilities, then it might not get to that level. But we really want Jetpack to be your go-to solution so that you can have these products work well together as well.

It’s very generous too, the free version. You get a free CDN, you get VideoPress for free, and bringing people in the door and showing them that. Some folks are seeing the light of that, of what it can actually do and do pretty well. But for instance, like SEO. Yeah, Jetpack does SEO, but it’s the most rudimentary, basic version. I want to make that a bit better there. But also things that it doesn’t do well. Either get rid of those, if they’re just going to sit on a shelf and grow with age, what’s the point of it?

So yeah, a lot of realignment with that and understanding that teams that are fully focused on one specific part of what Jetpack does, it’s really hard for us to compete with that.

[00:12:46] Nathan Wrigley: Do you envisage a future for Jetpack now that you are at the helm, if you like ? And I don’t know how the structure of the people that are working on Jetpack works. In other words, do you have a forms dedicated crew where you’ve got, I don’t know, a bunch of people who just work on forms? You’ve got a bunch of people working on VideoPress and VaultPress and all of these different bits and pieces. Or is it, you work with Jetpack and you kind of move from team to team? I’m just curious as to what it looks like inside of Automattic and the different bits that make up Jetpack.

[00:13:14] Devin Walker: Yeah, so this is really an interesting time at Automattic, where they’re going from that functional organisation where it’s product focus. Where Jetpack did, a year ago, have a dedicated development team, designer team, and the person that was in my role before, it was just like a classic company structure in a way, within Automattic.

Now it’s shifting to more of a matrix organisation where there’s one architecture team. They handle .com, they handle Jetpack, they handle a bunch of other products like WooCommerce within that. And the designers as a product are outside of that.

And so what that means is we, as the product team, we have a shared roadmap where, if you ever use .com, a lot of what brings that special sauce to it, what makes it unique outside of the self installed WordPress is Jetpack. So for instance, forms is getting a massive upgrade. And the 15.2 that just came out, it has quite a big upgrade. 15.3, we’re going to have even more. So there’s a dedicated team right now that’s, some of the best engineers, I’ve been really blown away with the level of engineering at Automattic, are working on bringing forms up. And I’m leading that initiative, putting myself into that place where I can then shape forms in the future.

But that does mean that some other elements of Jetpack aren’t getting taken care of right now. AI’s going to become a big thing. We have to pick and choose based on our resources, what are the most important things for our shared initiative? But what that means is they work better together. I think you’re going to see in the future a lot more benefit of running WooCommerce and Jetpack together.

Now, we’re not going to force you to log into wordpress.com to use WooCommerce, but to get some of that benefit, you will need to OAuth in to using Jetpack. And that is a requirement, because a lot of the Jetpack, what you get for free and the secret sauce is based on our cloud servers. You basically are starting to use our infrastructure for free. And Automattic is huge on privacy. And so I don’t quite understand that whole conflict of folks that don’t like that. There’s just some people out there that will never really like Automattic and they will not OAuth in or double sign in to use Jetpack, you know what I mean?

[00:15:29] Nathan Wrigley: Yeah, it’s kind of curious. So if I’m parsing it right, it sounds like what you were saying was that in a recent restructuring of Automattic and over the last 18 months or so, I think there’s been a lot of that. It sounds like Jetpack is more of an amorphous thing. It’s not like these particular people are dedicated to Jetpack Forms and these ones are for VaultPress or whatever it may be. It’s more liquid than that. We’re going to do a dedicated sprint on Forms, for example. It sounds like that’s getting an update. So probably has had people on the seats having a look at that.

And then once that’s put away and tidied up, then move to something else. But also, I guess an interesting thing that you mentioned there is that because it’s in this wider organisation of which WooCommerce, it’s pretty big, that you can also communicate with those folks. So there may be some overlap between what Forms can do in Jetpack and something that you might wish to do with WooCommerce, those kind of things.

So have I got that right? It’s not like dedicated people doing dedicated products within Jetpack, it’s much more liquid and amorphous than that.

[00:16:23] Devin Walker: Absolutely. Rather than having silos we have one large organisation that works better together. And our vision is really that all the WordPress products should be very similar to Apple and how when you’re using iOS or MacOS, there’s a lot of similar fields and they work well together and they tag team off of each other.

And prior to this reorg, that wasn’t happening so much. And we experienced this at Stellar as well. They purchased a bunch of plugins, brought them all in, the vision was for them to all work well together. We went from functional organisation to this matrix type of organisation. And so this isn’t my first rodeo doing it, I know it can work. But it does take a concerted effort, and it’s still ongoing right now. It hasn’t been 18 months, it’s been like six months. And we’re still trying to figure things out. So me stepping in at this time, I’m really trying to figure it out.

I have a blog post called, or a P2 post called Connecting the Dots, where I’m just trying to find which experts and which products on Jetpack they know better. I’ve been having so many one-on-ones just to try to get to know these folks, understand their history with Jetpack and put it in this kind of glossary of what I have here, and keep that updated as my time progresses here.

[00:17:35] Nathan Wrigley: It is kind of hard to get a grip on what Jetpack is. Because it’s trying to do all these different things, I think it is quite hard for people to understand what they’re installing. So they install Jetpack, okay, I’ve heard that Jetpack’s a thing, I’ll go and install it. There’s loads of free stuff available. And then all of a sudden there’s bits which do work, there are bits which you can extend and upgrade and, you know, you might have to log in with .com to make that bit combine with this bit.

And then there are bits where, you know, it feels like the classic themes work well in some areas, and then if you’ve got a block-based theme, other things don’t work quite so well. I’m thinking like social sharing and things like that. And it’s bit of a, mess is the wrong word, but it’s incredibly confusing, I think, to a novice user. And so I’m, I’m going to put words into your mouth, I’m guessing this is one of the challenges that you are going to try and tackle to take that confusion away. Because, I don’t know, it doesn’t matter how many times I log into Jetpack, there’s always a bit of a surprise. Oh, okay, it works that way. That’s curious. I wasn’t expecting it to do that. And I’ve been doing this for absolutely ages, and I’m still surprised by the way things work.

[00:18:33] Devin Walker: You’re not alone. So one of the things that Matt’s been saying since I’ve come on board is we don’t really need to build much more new things. We need to focus and improve what’s already there, especially in Jetpack and .com. And simplifying it and making it make more sense to the end users. And Jetpack is a prime candidate for a really fresh look at how that can happen.

We’ve been doing exercises as the product team for a framework called Jobs to Be Done. You put yourself in the shoes of that customer and you experience it through fresh eyes, based on what they are looking to get out of it.

For instance, the classic, I guess, analogy is, folks don’t, they don’t want a quarter inch drill bit, they want a quarter inch hole, and that’s just the tool they use to get that quarter inch.

And it’s the same thing with Jetpack or any other software product, and it’s a reforming in thinking. It’s only my fifth week here, but it’s been really a refreshing way to think about how we build product, and how I can then work with the designers to then smooth out those wrinkles of which there are many.

[00:19:40] Nathan Wrigley: Yeah, it’s kind of interesting that you say that, because pretty much everything that Jetpack has, well, there’s one notable exception, which is of course AI, which we’ll come to in a minute. But more or less everything that’s in Jetpack has been available in some form or other for a decade or more. You know, forms is, it’s not a new thing. There’s some interesting ideas that people have come up with that maybe we’d want to integrate, but backups, it’s not a new thing.

So the idea of not having new, well, features is probably the wrong word, but not having a new product and just finessing what you’ve already got, I think that would be music to any subscriber to Jetpack. One of the paid plans that you got, I think they would absolutely love that. Just finesse what you’ve already got. We’ve already got this thing, we know what we’ve got, we know how it works, but finesse it, give us a few more features here and there in the bit, like for example, forms or what have you. That seems like music to my ears.

But I’ve said it. The cat is out the bag in this episode now, AI. AI is smuggled into Jetpack in the most, it’s kind of hidden. It’s almost entirely hidden, and yet incredibly profound. I don’t know if, dear listener, you’ve experienced Jetpack and it’s AI features, but if you switch it on and you just go, I don’t know, make a blog post or something like that, when you go to publish, it will just helpfully write your excerpt and your featured image, it will create that for you on the fly. It all happens in the background. It’s really incredible. How did that get under the radar? And is that going to be a big feature?

[00:21:02] Devin Walker: That is going to be a huge feature. I just came back from New York with our AI engineering team led by James LaPage, who’s one of the brightest, young stars, I want to say, in WordPress. And he’s one of the reasons that I’m so excited for what AI can become with Jetpack, and where it’s going to go from here. It’s really great that you are already like what’s there? But that’s just scratching the surface from what we’re going to be doing in the near future.

We’ve got quite a large team working on this. This is a 50 plus engineering team. It’s a huge focus of Automattic. And Jetpack’s the way we’re going to bring a lot of what we’re bringing to .com to self-hosted users. And it’s not going to cost you really much at all and it’s gonna be done in the WordPress way.

Right now it tries to be your content companion, is kind of how I call it, but it’s going to do that a lot better, and it’s going to reach outside of the post editor and do a lot more helpful items for you in the WP admin. And not only in the WP admin, also provide some tools for you in the future for your visitors and how you can convert them, how you can get them to sign up on your newsletter, or you can get them to ask presales questions, or fill out forms or what have you. It’ll be very moldable and shapeable.

So I delightfully was at several demo presentations at this meetup where I was just blown away. Sat down with Matias, James, a lot of the key stakeholders and players here at .com on how and when we can start bringing this into Jetpack.

And what’s there right now is good. It’s almost going to be entirely rewritten and thrown away for what the foundation now is going to become. And so that’s one of the more exciting, more immediate, roadmap items that I’ll be really working on the next 8 to 12 months. You’ll see a huge change.

[00:22:54] Nathan Wrigley: I feel like at the moment the AI implementation in Jetpack is about content, the content that you’re creating right at this moment. We’re creating, I don’t know, SEO fields and we’re creating excerpts and things like that and featured images and what have you. But if you haven’t had a play, again, I’ll link this in the show notes, Automattic’s Telex, which is the capability to, you write a simple prompt and it will create a block for you. I feel that something like Jetpack with something like Telex, just hidden in the sidebar of a WordPress blog post would be really kind of interesting. You know, the idea that, I need a block for this.

[00:23:26] Devin Walker: Are you reading my DMs? Because, exactly. You’ve already sort of got a crystal ball right there. And with Telex, that’s a huge opportunity for site building, for imagining anything that WordPress could be, and having it created there.

Right now it’s great. It creates separate plugins, you can download and install them, you can’t sync them per site. It’s kind of annoying how there’s all these plugins there. There’s not much management updating over time. Jetpack can be that bridge for you, and that’s really an exciting future where it needs to go.

[00:23:57] Nathan Wrigley: Yeah, because at the moment, if you are an inexperienced WordPress user, if you’re not technical, let’s put it that way, then you are constrained entirely by what’s there or what the developer has built for you or the range of plugins that you’ve installed. And I feel like in the near future, you reach that point of frustration and you suddenly realise that, oh, there is no block that does that thing. Well, why don’t I just make one?

And you’ll write a small prompt, I don’t know, I need a real estate block, or I don’t know, I need a block because it’s coming up to Christmas. I need a block which is going to show snowflakes falling on this particular post. Please don’t do this by the way, but you get the point. I’m just going to go ahead and make it, and it’ll be this entirely disposable thing. And when I’m finished with it, I’ll probably just throw it in the trash or maybe keep it until next year.

But the point is, your WordPress becomes like this, how to describe it, it’s almost like the scaffolding for an infinite arrangement of possibilities. Whereas before, WordPress felt a bit like a box. If it wasn’t in the box, it couldn’t be done. But now the box got opened and there’s all this scaffolding everywhere and it can do a million more things. And as Matt Mullenweg said, you know, it’s becoming like the OS for the web or something like that.

And the fact that AI is binding to the abilities inside of WordPress, so with the Abilities API and things like that, it knows everything that your WordPress website can do. You know, create users, create posts, delete posts, all of these kind of things. And Jetpack seems really aligned to doing that. I don’t know how it would fit into the bigger Jetpack picture, but, yeah, interesting.

[00:25:27] Devin Walker: Yeah, well, I think AI can be the glue that binds a lot of these individual products together and really paint the picture on how they work well together, and work within your WordPress Core to make it the Jetpack that is supercharged, right? I mean the WordPress that has a Jetpack strapped to it.

There is a great number of, kind of mission statements and taglines over the years for Jetpack. None of which I think have been fully fulfilled. So I really want to revisit that, revise that, and you’ll see a lot of updates coming to the website soon, soon-ish. Telling and bringing people along this journey.

If you look at the website and a lot of the marketing right now, it’s kind of on idle. So that’s another big part of what I’m being focused on, and that will help change the perception in the community and outside of it, of what Jetpack is and what it can do for you is, pulling up the curtain, if you will, on all the cool stuff we’re doing here.

You could read P2s all day here and many of them are so impressive and I feel like a lot of them should be public. There’s so much good content here that is really impressive. For somebody like me who’s been in the community for 15 years, like, oh my gosh, we have the best engineers, the best designers, and it’s all in this P2. Like, let’s get some of this published.

[00:26:42] Nathan Wrigley: Yeah, well, that’s curious. So I was reading your mind a minute ago, you’ve just read my mind, because the next little bit was going to be all about marketing. Because it doesn’t matter, with the best will in the world, the best product in the world will probably fail, if not marketed correctly.

And it feels as if, when Jetpack began, because it was kind of the thing, a long, long time ago it was the thing, it had that success kind of built into it. You know, it was an Automattic thing, it was a WordPress thing, it became popular because it did so many things that nothing else could do.

Fast forward till today, it feels like the wheels have come off the marketing a little bit, or the train has completely pulled into the station and not moving at all. You know, I can’t remember the last time I saw something engaging, like a YouTube video or somebody experimenting on their YouTube channel with a Jetpack thing.

Whereas with third party plugins, it’s happening all the time, you know? And so it feels like that’s going to be a very big part of where you are, you know, you’ll build hopefully some amazing things, but then trying to turn the tide and get people to be engaged and interested and see the utility of it. I’m guessing that’s going to be a part of the job which is separate to the technological part.

[00:27:46] Devin Walker: It will, absolutely. I think for quite some time it was almost build it and they will come here. And for many, many years they did come. And now it’s harder because the marketplace has expanded quite a bit. There’s a lot of other folks out there doing really cool things with WordPress and have a lot more focused marketing efforts behind them.

I mean, point and case was GiveWP, we were just, people weren’t turning to Woo or Gravity Forms because we made it that it was the number one solution you had to go do it. We just hammered that point through WordCamps, through videos, through podcasts, whatever it was, that was our mission.

And for Jetpack, we really need to refocus on that and do that a lot more. It’s very engineering led organisation. I think marketing to some point is built into their roles and they’re not doing that part as much as I would like.

And on another aspect, I think we definitely just need more marketers. I’m not going to say the exact numbers, but it was a surprisingly low number of marketers to the size of the organisation when I came in. I’m used to a much better ratio.

So I’m going to be hammering that point a little bit more home as I get through the door, but it’s something that I’ve mentioned a bit already in my 5 weeks here.

[00:29:02] Nathan Wrigley: I don’t know what the install base is specifically. It’s a lot, right? Jetpack has a lot of installs and so presumably you’ve.

[00:29:08] Devin Walker: The core is 4 million.

[00:29:09] Nathan Wrigley: 4 million. Okay, so, wow, gosh. So presumably that means anything that you do do, you’ve really got to tread carefully. So for a start, you can’t break things. You can’t just ship a brand new UI in let’s say the forms aspect of it overnight. And I presume that’s kind of like a bit of a noose around your neck in that, you know, you want to move fast and break things in some respects, but with 4 million installs, which is really right at the very top in the WordPress ecosystem, that’s big, big numbers. You are going to constrained in what you can do and how fast you can move things and how quickly you can break things.

[00:29:40] Devin Walker: Somewhat. Somewhat I agree with that. Right now we are on a monthly release cycle and there’s definitely a lot of caution around that. And Jetpack touches a lot of .com too, so there’s that extra added user base, which is humongous. So there is that bit of treading carefully.

But I want to balance that with being aggressive. We just shipped, prior to me coming on board, a new onboarding for getting connected. It’s just through the connection segment, getting connected to .com, and that really had positive results and saw an uptick in connected successful sites. I think we can take that to the next level and explain what Jetpack is, what they need it for, and really optimise it for the best use case based on what that particular site wants or needs.

Going beyond onboarding is then getting into the product UI itself, making the navigation much more clear and understandable.

You know, there’s three different areas in Jetpack right now where you can toggle on and off different modules or products.

[00:30:39] Nathan Wrigley: Oh, I’ve discovered many them.

[00:30:41] Devin Walker: Yeah. So I think we need to consolidate that at least. And there’s more Easter eggs. I don’t even want to call them Easter, I don’t know what you’d call that, but interesting quirks that we can clean up.

And for the most part I think we do have to be a bit careful because it’s such a massive user base. Breaking things, just look at some of the Jetpack reviews. Breaking them and lack of support. Those are the two main cause of one star reviews. And with that many, I really want to get that review base above 4.0 stars. But with 3000 or whatever reviews it is, it takes a long shift to get that. And we’re not going to do that by continually breaking things, so it’s a balance.

[00:31:19] Nathan Wrigley: It’s kind of interesting that me, a relatively inexperienced user of Jetpack, I was able to discover many of the quirks that you’ve just mentioned almost immediately. You know, just being curious. And I’m the kind of person that when I download anything, I go and look at every single menu item and kind of think, well, what does that do? How would that work? It really didn’t take me long to discover, well, hang on, that is somewhere else. If I engage that, does that mean it conflicts with this thing over here?

And I saw this over and over again. And so I think that, as you imagine, would be some of the very, very brilliant low hanging fruit. To just have a UI which does, you know, there’s one place for one thing, it works as expected that you don’t, I’m sure you know where I’m going with this, basically, just simplify things, make it elegant in the same way that we’ve seen with so many third party plugins.

Because at the moment it kind of feels like a whole range of different things that have been slammed together and forcefully told to get along with each other, as opposed to like a happy family that, just everything works and everybody’s happy and there’s bliss and rainbows everywhere. It feels a little bit like that, if you know what I mean?

[00:32:21] Devin Walker: Oh, I completely agree. I think we used in the pre-show and it’s a bit of a Frankenstein. We need to change it from that. If I had a nickel for every toggle in Jetpack, I don’t know if I’d need to work anymore. There are quite a few toggle on, toggle offs in just a row. You can imagine how this interface could be much more elegantly put together.

And we’re going to use user feedback for a lot of this and ask, hey, what do you guys think of this? Because we can’t do it successfully in a bubble.

[00:32:52] Nathan Wrigley: Well, and the other thing is, given the perfect UI, it does so much stuff. If you just had Jetpack, if you had a vanilla version of WordPress and you installed Jetpack and everything was easy to navigate and worked as expected first time and maybe there was no dependency on having a .com account or what have you. It does all the things. It would take you from like zero success to broadly speaking, okay, you’ve got a credible website. Maybe there’s going to be some interesting cases where you want a little bit more SEO finesse or something like that.

It would get you to the races, you know, it would get you to put your horse in the race and have a good go. And there’s not much like that out there. There really is nothing that I can think of in the WordPress space. But it’s a leviathan and it’s got many heads. We need it just to have the one head, I think.

[00:33:35] Devin Walker: Very much so, and that’s the challenge that I’m in here to work with this entire team and put a lot of thought behind it.

[00:33:44] Nathan Wrigley: Okay, so it’s all on you. So if Jetpack is a success in two years time, we know who to thank for that. And it does genuinely seem, for somebody with your obvious interest and capabilities, it does seem really, really enjoyable. I’m sure it’ll keep you awake, but an enjoyable challenge. Something that you get your teeth into. Something where the success can be measured fairly quickly. You know, does the discontent diminish? Does the UI improve? Tick, tick, tick. We did a good job.

And also, there’s loads of room for improvement. So you’ve entered on a, you’ve definitely got yourself into a position where you’ve taken on a project where the improvements are evident everywhere. I hope that you managed to grab hold of them and wrestle this to the ground.

[00:34:21] Devin Walker: Well, I really appreciate that, Nathan, and why don’t we have a check in in 12 months and see where we’re at on this journey. I think that would be a good way to keep us honest, follow along in this journey along the way, we’ll see how far we’ve gotten.

[00:34:35] Nathan Wrigley: Okay, well, for now then, go and install Jetpack. If you’re listening to this, we’ll be back in 12 months time, so go and have a play with Jetpack as it is now and see.

It sounds to me that Devin is like all ears. If you’ve got some quirks and you found something that’s curious or unexpected or dissatisfying or just downright annoying, where do we get in touch with you? Oh, also, I suspect Devin’s more than happy to receive positive commentary as well.

[00:35:01] Devin Walker: Yeah, I mean the positive stuff’s great too. Right now feedback@jetpack.com is a good place, but we’re going to make this a lot more public in the near future. You can also just tweet at me @innerwebs, I-N-N-E-R-W-E-B-S, or go to my website devin.org. But jetpack.com, jetpack.com/feedback is also a great place. So that’s a bit about me and where you can find the Jetpack information.

[00:35:27] Nathan Wrigley: Okay, thank you. So definitely a challenge out in the public for Devin to get his teeth into WordPress’ Jetpack, and see if he can figure it out and make it better. Let’s check back in 12 months time and see how we’re going. Devin Walker, thanks for chatting to me today.

[00:35:38] Devin Walker: Thank you.

On the podcast today we have Devin Walker.

Devin’s journey in the WordPress ecosystem spans many years, with experience in development, design, marketing, and customer support. He’s best known as the co-founder of GiveWP, which he built and scaled before it was acquired. During his time there, he touched a variety of prominent WordPress brands including iThemes, Kadence, LearnDash, and The Events Calendar.

Today, Devin is starting a new role leading the Jetpack suite of services at Automattic. It’s a position with hefty responsibilities as Jetpack powers millions of WordPress sites, and integrates deeply across Automattic’s product portfolio.

I talk with Devin about why he took on this challenge, the divisiveness and complexity surrounding Jetpack, and his vision for refocusing the plugin and simplifying its user experience.

We start by hearing about Devin’s extensive WordPress background and the choices he weighed up when deciding to join Automattic. The conversation quickly moves to the scope of Jetpack, its evolution, the struggle to be a “jack of all trades, master of none”, and the recent efforts to bring greater focus and polish to key features like forms and SEO.

Devin gets into the organisational changes at Automattic, how Jetpack’s development teams now collaborate more fluidly with other product teams (such as WooCommerce), and the balancing act of shipping improvements to a 4 million strong user base without breaking things.

AI emerges as a massive new frontier, and Devin shares behind-the-scenes insights into Jetpack’s current and future AI capabilities, giving us a glimpse at content creation, block-building, and how AI might reshape user and developer expectations in WordPress.

Throughout, we hear about Devin’s approach to product marketing (and the need for more of it), the importance of listening to user feedback, and his plans for a more coherent and compelling Jetpack experience.

If you’re a WordPress user wondering where Jetpack is headed, what’s working, or how AI fits into the future of site building, this episode is for you.

Useful links

Jetpack

Jetpack feedback form

GiveWP

 WP Rollback

Automattic AI team announcement post

Telex

Devin’s website

❌