HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ampproject
amphtml
JavaScript2015–2023
ampproject / amphtml

amphtml

The AMP web component framework.

Web Development
Explore on GitHubRead Hacker News discussions
96Distinct people
146Mentions
0Explicit recommenders
14.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The AMP web component framework.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:23:53 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year146 dated mentions

Observed mentions: 2015-10-07 14:41:30 UTC to 2023-02-21 19:56:36 UTC.

01020302015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 14 mentions; 4 submissions, 10 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 28 mentions; 2 submissions, 26 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 27 mentions; 1 submissions, 26 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 30 mentions; 5 submissions, 25 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 17 mentions; 0 submissions, 17 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 17 mentions; 0 submissions, 17 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC14410
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC28226
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC27126
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC30525
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC17017
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC17017
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC909
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
AMP ⚡ ⚡⚡⚡ Tooling AMP is a web component framework for easily creating user-first websites, stories, ads, emails and more. AMP is an open source project, and we'd love your help making it better! Want to know more about AMP? amp.dev is the best place to learn more about AMP--and of course the site is made using AMP! For developers using AMP, amp.dev includes guides and tutorials examples reference docs example templates tools to make using AMP easier Having a problem using AMP? The amp.dev Support page has resources for getting help. Use Stack Overflow to ask questions about using AMP and find answers to questions others have asked. Let us know about bugs, and file feature requests to suggest improvements. AMP accepts responsible security disclosures through the Google Application Security program. Want to help make AMP better? docs/contributing.md has information on how you can help improve AMP, including ongoing participation through Slack, weekly design reviews, etc. We strongly encourage code contributions! We enthusiastically welcome new contributors to AMP even if you have no experience being part of an open source project. We've made it easy to get started contributing. Consider joining one of AMP's Working Groups, where most of the day-to-day work in AMP gets done. Other useful information AMP's release documentation provides details on how and when AMP releases new versions, including how to know when a change is live in a release. AMP's roadmap provides details on some of the significant projects we are working on. The AMP meta repository has information about the AMP open source project, including AMP's governance. AMP's code of conduct documents how all members, committers and volunteers in the community are required to act. AMP strives for a positive and growing project community that provides a safe environment for everyone.
Read the full README on GitHub

What Hacker News says

17 sources
gregable·Dec 6, 2019
Reasonable question. Until the javascript has loaded (a single cacheable javascript file: https://cdn.ampproject.org/v0.js ), the browser can't lay out the resources on the page (images for example). If the browser rendered the page before layout, it would likely look pretty bad. Then when the javascript arrived, the document would layout again moving elements around. This is typically referred to as the "Flash of Unstyled Content" (https://en.wikipedia.org/wiki/Flash_of_unstyled_content) and is considered by some to be a negative user experience. Many web pages outside AMP take a similar approach to hiding the content until the layout has completed. The 8 second CSS animation is only present as an "escape hatch" in case the javascript never loads. The specific value was chosen as a time that probably indicates the javascript will never l
Read the rest
oad. Note that if javascript is disabled entirely, the page is rendered immediately via the <noscript> tag. There has been a discussion around changing the 8 second time to something shorter ( https://github.com/ampproject/amphtml/issues/22543 ), though it could probably be renewed.
In How to fight back against Google AMP as a web user and a web developer
aloknnikhil·Oct 14, 2019
AMP will never truly be "Open". Google, infamously, shot down a request for transparency into the decision making process for the project > "Our project our rules" https://github.com/ampproject/amphtml/issues/13597 To be fair, they did retract their messaging in a later comment > I first want to acknowledge that we are learning how to run such a big open source project and so many things are being figured out. E.g. we are currently rewriting our Governance guidelines to answer many of your questions more directly.
In AMP is joining the OpenJS Foundation incubation program
HALtheWise·May 11, 2019
Basically, because it isn't actually possible to make a website that loads in under 100ms on poor connections any other way. For reference, on the fast university wifi I am currently connected to, news.ycombinator.com loads in 499ms. When I switch to my phone's hotspot, that rises to 2.38 seconds, and on a simulated slow 3G network, that rises to 6.51 seconds. I haven't tested a 2G connection in India, but wouldn't be surprised if it exceeds 10 seconds. Hacker News is not a heavy webpage, in fact, it is probably about as lightweight a webpage as is reasonably possible to create. The key technique that AMP promises will beat the limits of network latency is precaching. Unfortunately, users have a strong privacy expectation that random websites will not be notified that you are interested in them until you actually click the link in search
Read the rest
results (or news, or whatever). For precaching to work without violating user privacy, the data needs to be loaded from some server that already knows that the link was shown to you, so there is no privacy violation from giving it that information. AMP's solution is for the host company of the results page to fill that role. The AMP lightning bolt is intended to mean "this page is already downloaded offline on your device, and so will load instantly", not just "this page is well-designed and fast". The difference is minor for blazing fast connections, but that isn't true for developing world users with weak connections and devices. Google has said that when open web standards like Web Packaging finally show up which enable the same safe preloading behavior, those sites will be included in AMP carousels. We'll see whether they follow through with that. [1] [2] * All experiments conducted with cache disabled, times are until Load event fires. [1] https://blog.amp.dev/2018/03/08/standardizing-lessons-learne... [2] https://github.com/ampproject/amphtml/blob/master/contributi...
In Google Creates 'Dedicated Placement' in Search Results for AMP Stories
lukestevens·May 1, 2019
My tweet about this, for what it's worth: On the same day Googlers protest retaliation by their own management, a Googler posts about how AMP, the astroturfed, Google-developed and mandated format is the cuddly "open" choice for those who want the "web" (i.e. Google) to win. Give the web to Google? What could go wrong? === And for context, here's what the AMP dev rel says in TFA: "The second reason is that many compare AMP to RSS, and the media positioned it as competitor to certain other big companies’ walled garden media formats. That narrative certainly didn’t help, and for what it’s worth, we, the AMP team, have never told the story that way..." And here's the origin story from one of the AMP Project's cofounders and former technical lead, Malte Ubl [0]: "We were worried about the web not existing anymore due to native apps and walled
Read the rest
gardens killing it off. We wanted to make the web competitive. We saw a sense of urgency and thus we decided to build on the extensible web to build AMP instead of waiting for standard and browsers and websites to catch up. I stand behind this process. I'm a practical guy." Honestly... [0] https://github.com/ampproject/amphtml/issues/13597#issuecomm...
In AMP as Your Web Framework
pdkl95·Apr 17, 2019
That is patently not true. From mmastrac's [1]: > Resources such as images, videos, audio files or ads must be included into an AMP HTML file through custom elements such as <amp-img> From: https://github.com/ampproject/amphtml/blob/master/spec/amp-t... Amp Specific Tags <amp-img> <amp-video> <amp-ad> <amp-fit-text> <amp-font> <amp-carousel> <amp-anim> <amp-youtube> <amp-twitter> <amp-vine> <amp-instagram> <amp-iframe> <amp-pixel> <amp-audio> <amp-lightbox> <amp-image-lightbox> None of that is "100% valid HTML".
In Announcing AMP Real URL

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.