We’ve just published updates to the AMP Roadmap.You can find it on the AMP Project website, and read a summary across the focus areas below.
Format
We recently launched form support with <amp-form>. With this feature you can now implement a product color picker on an e-commerce detail page, an email field to capture newsletter signups, or an interactive poll to engage readers within an article.
You can now also use <amp-app-banner> to drive installs of native apps from AMPs, as well as deep-link directly to native app content for users who have already installed your app.
In addition, we’ve launched a number of enhancements to advance first-class support of progressive web apps (PWAs) in AMP. These steps enable building PWA experiences using the AMP content format, and you can learn more about this in a recent talk at Chrome Dev Summit and by checking out a sample app built in React here.
We’re working on a number of enhancements to immersive media in AMP. First, we’ve rolled out support for an enhanced video experience, including muted autoplay support. We continued work on the improved <amp-lightbox> experience. We’re also implementing support for displaying images linked to a thumbnail carousel, which will help support e-commerce product pages.
Finally, we have two projects we hope will make it easier to implement AMP, and easier to extend its interactive capabilities. To help developers quickly create well-styled AMPs out of the box, we’re developing a collection of quick-start sample code. This will include copy-and-paste templates for common page elements like menus and hero images, as well as full page templates for basic use-cases. To extend AMPs interactive capabilities, we’re working on a mechanism to bind element behavior to user actions.
Analytics
So far in Q4 we have prioritized adding deeper analytics support for two AMP elements.
The “slides” version of <amp-carousel> now supports triggers and variables that enable tracking when the user navigates between slides in the carousel. and amp-form.
The recently launched amp-form feature is gaining analytics support as well. We are adding triggers that will allow tracking of when forms are successfully submitted or submitted in error, and this should launch and be available soon.
Implementation on a share tracking feature is underway and nearing completion. Our backlog also includes enhancements to support additional video analytics and e-commerce analytics.
Ads
Since our last update, we launched the flying carpet ad format (guarded by an experiment flag), and are making UX improvements to sticky ads.
We are continuing to work on UX improvements for all ads in AMP, which include features like consistent ad labeling while the ad is loading and default placeholders and fallbacks (in order to avoid “blank rectangles” on AMP pages).
The A4A (AMP4Ads) team is continuing to ramp up ad delivery of AMP format creatives by supported ad servers. Publishers like The Washington Post and Vox Media have begun testing these new creatives. A4A ads will be available for wider consumption in Q1 but we welcome your feedback in the meantime on GitHub.
Access
The work for server-side amp-access functionality has been completed and has entered an alpha testing phase.
Looking ahead, we’ve started implementing some support for a delegated sign-in experience, and further exploration and implementation will continue on this project.
* * *
Thanks to the AMP development community for your work and feedback. As always, please let us know if you have any issues or feature requests.
Posted by Rudy Galfi, Product Manager, AMP Project