In this episode, I’m joined by Alberto Medina, Developer Advocate working with the Web Content Ecosystems Team at Google, and Weston Ruter, CTO of XWP. We have a candid conversation about Google’s AMP Project. We start by learning why the project was created, what its main goal is, and the technology behind it.
We also dive into some of the controversy surrounding the project by discussing whether or not AMP is a threat to the Open Web. Medina and Ruter provide insight into AMP’s transformation from focusing on the mobile web to providing a great user experience across the entire web. Last but not least, we learn about the relationship between Automattic, XWP, and the AMP team and how it’s helping to shape the future of the project.
Notable Links Mentioned:
AMP for WordPress Plugin
AMP for WordPress GitHub Repository
AMP GitHub Repository
Video presentation from AMP Conf 2018 showcasing the work that’s gone into the AMP for WordPress plugin
Official blog post outlining the future of the AMP Project
WPWeekly Meta:
Next Episode: Wednesday, March 28th 3:00 P.M. Eastern
Subscribe to WordPress Weekly via Itunes
Subscribe to WordPress Weekly via RSS
Subscribe to WordPress Weekly via Stitcher Radio
Subscribe to WordPress Weekly via Google Play
Listen To Episode #309:
Podcast: Play in new window | Download (Duration: 54:53 — 28.2MB) | Embed
Subscribe: Apple Podcasts | Android | RSS
Permalink
Hey, guys!
Great show. Really. I love it.
Just one note to Jeff. Man, it’s not 2017 anymore XD. Take a look to your intros and you’ll notice that you’re still saying “2017”.
Looking forward your future episodes.
Report
Permalink
This long-form post from Caspar Hübinger (glueckpress) is a great companion piece for this podcast episode: AMP and WordPress will scale performance on the web for millions of users, hate it or love it.
Report
Permalink
Really disappointed in the episode. Alberto’s contention that without AMP, the web would go away was ridiculous and required a challenge.
In fact, I heard nothing that would dissuade me from believing that AMP is short lived, proprietary technology that serves only Google interests.
Jeff’s example of a local new site was an apt one, because those sites are some of the worst examples of bloated content on mobile devices. They are also, entirely profit driven in a dying industry and in fact the LEAST likely to adopt AMP. A perfect counter example to the rosy picture of community involvement painted by Alberto.
Report