The AMP Project Roadmap
The fact that the amp-story desktop UI shows up to three
amp-story-pageelements in view at once can be problematic for designing responsively, because the size of the amp-story-page differs from the size of the viewport, so common responsive practices that are based on the viewport dimensions won't work (e.g. media queries, and the viewport units
- Add an analytics trigger for when the user education overlay is shown (#15420)
- Add an analytics trigger for when the video spinner is shown
- Create a prototype of a new desktop experience
- Test the prototype
- Integrate feedback
- Design a launch/rollout plan
- Roll out the new desktop experience
Stories should support paywalls, similar to how standard AMP documents support paywalls through the usage of the
We should allow publishers to specify arbitrary custom content to be shown in a sidebar. The API and documentation should make it clear that every platform has the ability to display or not display this content. The sidebar can contain both runtime-specified content (configurable by viewer) and publisher-specified content.
Sponsored Story Ads could be entirely inlined within the organic story instead of having to load the sponsored story in a new tab or with a redirect. Full design in the works.
For any clickable element outside of amp-story-cta-layer, we should show a tooltip that defers the action until after the user has clicked on the tooltip.
Right now it is unclear which story pages have audio and which do not. We should improve the audio experience by only showing the audio icon when it makes sense (#13652) and adding callouts as necessary.
Right now, everything is designed as LTR. This is a cover bug for enabling RTL support. We should consider the story to be RTL if:
Bring the feature described in #13716 into amp-story.