The AMP Project Roadmap
Re-factor and re-launch a new version of amp-carousel to address a number of user & developer needs, including dynamic & responsive content, UX updates, and using amp-carousel outside of the context of valid AMP
AMP has a default loader for most content that depends on an external server call for content. Currently it's an animated ellipsis for most cases, and a more polished design for ads. This feature is to create a more polished design across all components that need it, and to possibly differentiate designs based on the context.
Implement a common image-slider pattern for publications comparing two different but related images: celebrities then and now; maps of geographic regions before and after a significant change; documents before and after editing.
Developers sometimes link device title to the background position of images, so that the content shifts on the screen in different directions and at different speeds based on the direction and degree of tilt. Ideally we can link this to an intuitive natural metaphor, so it feels predictable and natural. Phase one will be a low-level API along the lines of amp-position-observer, that allows such animations at a basic level.
Bring the feature described in #13716 into amp-story.
amp-position-observer makes it possible to create complex scroll-bound & scroll-triggered animations. However, we want to make some of the most common animations trivially simple to implement. This feature covers the case where arbitrary HTML elements translate slightly across the page in as the user scrolls them into view—both the scroll-bound case and scroll-triggered, time-based case. Developers will be able to configure aspects of the animation like trigger points, timing, and animation curve.
<amp-consent>component that enables publisher to get consents from readers and manage their consents.