Paul Bakaus (@pbakaus) is the “Voice of Chrome DevTools, AMP and Open Web Games at Google”, was previously the Studio CTO at Zynga and is the creator of jQuery UI.
HE blogs at his “sea of ideas” at paulbakaus.com.
In this edition of Decoded Chats, Chris Heilmann took a whole 50 minutes to take Paul on a deep-dive of Accelerated Mobile Pages, or AMP – a new and rather creative way to deliver content on mobile devices in a very secure and fast manner. As with every format competing with HTML, this brings a lot of worries and confusion, many of which we discussed here.
If you prefer to have an audio version, you can download it here (MP3, 24MB)
Here are the questions we covered:
- What is AMP to you?
- The main focus of AMP seems to be mobile, is that fair to say?
- Was AMP an answer to Facebooks’ and Apple’s news formats? Does it rely on Google technology and – if so – will it be open to other providers?
- It seems that the cache infrastructure of AMP is big and expensive. How can we ensure it will not just go away as an open system as many other open APIs vanished?
- Do large corporations have a problem finding contributors to open source projects? Are they too intimidating?
- Is there a historical issue of large corporations re-inventing open source solutions to “production quality code”? Is this changing?
- AMP isn’t forgiving. One mistake in the markup and the page won’t show up. Isn’t that XHTML reinvented – which we agreed was a mistake.
- AMP seems to be RSS based on best practices in mobile performance. How do we prevent publishers to exclusively create AMP content instead of fixing their broken and slow main sites?
- It seems to me that AMP is a solution focused on CMS providers. Is that fair, and how do we reach those to allow people to create AMP without needing to code?
- A lot of “best practice” content shown at specialist events seems to be created for those. How can we tell others about this?
- AMP seems to be designed to be limiting. For example, images need a height and width, right?
- In terms of responsive design, does the AMP cache create differently sized versions of my images?
- Are most of the benefits of AMP limited to Chrome on Android or does it have benefits for other browsers, too?
- Do the polyfills needed for other browsers slow down AMP?
- How backwards compatible is AMP?
- One big worry about publishing in AMP is that people are afraid of being fully dependent on Google. Is that so?
- Are there any limitations to meta information in AMP pages? Can I add – for example – Twitter specific meta information?
- Do AMP compatible devices automatically load that version and – if not – can I force that?
- How can I invalidate the AMP cache? How can I quickly remove content that is wrong or dangerous?
- It seems AMP is catered to documents, while most people talk about making everything an App. Is this separation really needed?
- What’s the sandbox of AMP and how is this now extended to the larger web as a standard proposal?