As the AMP project grows, we want to ensure that the community has a clear understanding of the features the team is working on and the status of each. Starting today, you can head over to the AMP roadmap and see an updated view of feature development across the project. We hope this is easy to understand and offers better insight about what each feature means. As a developer, you can also continue to look at the release logs on a per release basis.

Each feature can be in the “Next Up”, “In Development” or “Shipped” categories.

If you are interested in more detail, you can click on the heading of the issue and navigate directly to the GitHub issue to learn about associated issues or pull requests.

Here are some features we specifically wanted to call your attention to:

AMP stories

  • Monetization Support — Publishers can now use DoubleClick for publishers to serve direct-sold, premium advertising to AMP stories. Next up, we are looking at supporting HTML5 story ads over this quarter.
  • Learn about other stories related features in the blog post here.

New UI features

  • amp-date-picker — this is a full-featured date-picker for e-commerce use cases
  • amp-next-page — this feature, which supports the “infinite scroll” of page-level content like new articles or blog posts, is now available as an experiment on particular documents.
  • amp-date-countdown — this component, generously contributed by community members, supports a dynamic countdown to a specified date & time, primarily for e-commerce use cases like limited-time sales.

Upcoming Features

  • 1-line PWA — A large area of effort for the team is to figure out how to make it trivially easy for developers to create a PWA, given an AMP document. This includes smart caching and prefetching, as well as a way to ensure seamless page transitions associated with single-page apps directly in AMP.
  • amp-consent — We are continuing to enhance amp-consent functionality by providing publishers with the ability to fold their existing consent flows into AMP pages and manage consent status across AMP and non-AMP pages. We are also looking at supporting the IAB framework for user consent management.
  • AMPHTML ads — Over the next quarter, we will continue to work at improving the performance of AMPHTML ads, especially when served to non-AMP pages. In addition, we will also work on supporting AMPHTML ads in mobile app environments.
  • ID Link Decoration — We’re making page measurements easier by introducing ID Forwarding on AMP pages. The updates will help you see accurate metrics of your users and their journeys on your properties.

As always, if you have questions or suggestions, please share your feedback.

Posted by Vamsee Jasti, Product Manager, AMP Project