The Google AMP project will join the incubation program of the OpenJS Foundation, which is part of the Linux Foundation.
AMP, which originally represented accelerated mobile pages, although no more, was launched in 2015, apparently to accelerate page load on smartphones. The technology includes AMP HTML, which is a set of web components with optimized performance, and AMP Cache, which serves validated AMP pages. Most AMP pages are served by the Google AMP cache.
AMP looks like something like a land grab from Google and has been controversial. While better performance is welcome, having to support AMP HTML is also a burden for publishers and a restriction for web design, especially since Google’s guidelines state that “users should be able to experience the same content and complete the same actions on the AMP pages than on the corresponding canonical pages, where possible. "AMP support is optional, although if Google search prioritizes the AMP pages, publishers have few options.
In September 2018 , the AMP project announced an "open government model" in which decisions are made by the steering committee and a "wider variety of voices" have something to say in the direction of the project. The announcement included "exploring the transfer of AMP to a base. "
That move will now take place. Google's chief engineer, Malte Ubl, co-founder of the AMP project, announced last week that" AMP is joining l OpenJS Foundation incubation program ". This means that the project will join the foundation once several incorporation tasks have been completed. Ubl adds that Google will continue to finance the project, through the foundation, and that "the team of Google employees who contribute full-time to the AMP open source project will also continue to do so."
Google hits the brand slam stamping AMP with more crypto glam
In the frequently asked questions here it is said that the movement is a response to the "concerns of communities around [the project’s] ties with Google, as well as concerns about scaling the project."
There are good words about the commitment of "a strong website opened for the first time by the user forever", but frequently asked questions also indicate that "AMP runtime is currently hosted on the same infrastructure as the AMP cache of Google "and that" currently, only former or current Google employees have commitment rights. "
Frequently asked questions are answered by saying that "the ultimate goal is to separate the AMP runtime from the Google AMP cache" and that "more than one inclusive or base contributor" is anticipated in the future.
It is also worth noting that Google is a platinum member of the OpenJS Foundation and its parent The Linux Foundation, which means it provides significant financial support, so you can still expect the advertising giant to have something of influence on the governance of MPA.
Some of the fears about AMP dissipated in January 2018 when it was announced that publisher URLs, instead of Google URLs, would be displayed for AMP pages loaded from the cache.
By placing Technology in the hands of a foundation is a positive move, it does not change the way Google can prioritize AMP pages in search results and therefore ensures that publishers have to support the standard. ®
Beyond the data frontier