As we bid adieu to Q2, we made some updates on the AMP Roadmap to make sure the status of projects listed there reflects where these efforts stand today.
Here is a summary across the focus areas:
In the past three months we launched elements like <amp-sidebar>, <amp-accordion>, and <amp-social-share> to bring some highly requested functionality to AMP pages like site navigation menus and share bars. We introduced <amp-live-list> to enable live-updating content, and look forward to pushing it across the line from experimental to stable in Q3.
There are several additional priorities this quarter, such as support for forms, that haven’t landed just yet, which we expect to continue focusing on into Q3. Over the next few months, we are looking at adding features that make it easier to build immersive and interactive AMP pages as well as introduce methods to lazily load content that must be up to date—and do so in a way that’s compatible with AMP’s user experience and performance goals.
This quarter we shipped further ways to customize the <amp-analytics> “visible” trigger to provide viewability-based analytics data. We’re in the early phases of building support for A/B testing and share tracking, and development on those will continue into Q3.
In the coming quarter, we plan to add further support for video analytics and to deepen AMP’s analytics support to ensure it supports a wide variety of content verticals, such as ecommerce.
This quarter we continued our twin focus of making the existing ads better as well as laying the groundwork for even faster ads experiences with AMP. For the former, we developed two new ad formats in compliance with AMP’s philosophy: the AMP sticky ads and the AMP flying carpet ad format. Since existing ad demand can fill in these ad formats, publishers will be able to further monetize their AMP pages with good-looking ads. For the latter, we submitted infrastructure changes for AMP Ads For AMP Pages (“A4A”) which will allow AMP ads to be loaded as fast as content on AMP pages.
In Q3, we are working on adding ad server support to A4A ads, enabling buyside support for A4A, and better AMP signals for programmatic buyers and much more.
AMP now has multiple publishers such as the New York Times, Wall Street Journal, Financial Times, New Yorker, Folha, Les Echos, and Espresso live with paywalls globally. We are in the final stages of development of server-side paywall support for AMP, which will be in beta soon.
Extending AMP functionality to help publishers with conversion via simple, seamless user experiences is an important focus area for us. We are in early stages of prototyping simplified user sign-in to AMP pages, and development on this and associated features will continue into Q3.
* * *
We hope these roadmap updates are helpful. Thanks for taking the time to come up to speed on AMP. We invite you to come to our GitHub repository to collaborate with us on building AMP, and please let us know if you have any feedback.
Posted by Ashwin Limaye, Product Manager, AMP Project