I’ve seen a decent amount of open questions and controversy around the recently announced AMP project, a joint-effort by many publishers and platforms to improve the user experience of news and media sites. It all mostly boils down to how early we are in the lifecycle of AMP: There simply isn’t enough public documentation up yet, and third-party support and integrations are still lacking.

I was curious myself, so I’ve spent some quality time with the team behind AMP, and took a deep look at what’s going on behind the scenes. If you know me, you know I care greatly about the web and its open nature, so naturally I wanted to get a feel about AMP’s long term goals.

Turns out AMP’s goals overlap with mine: AMP is a means to an end to make the open web wicked fast and user friendly.

AMP is a means to an end to make the open web wicked fast and user friendly.

I’m really impressed by their execution and vision so I decided to get involved by lending my voice to the AMP project. Last week’s SFHTML5 meetup was a great start: Together with Paul Irish, Malte Ubl (AMP engineering lead) and Jordan Adler (AMP partner engineering lead), we gave an overview of why AMP exists, how it ties in with web performance and RAIL and how AMP works behind the scenes.

We then continued with a Q&A panel, where we’ve answered every burning question the audience had. If you you’re interested in AMP and find the current FAQ on the AMP homepage lacking, you’ll want to watch this:

I’m just getting started (while I’m at it, check out Malte’s excellent blog posts) and if you think I should come to a particular event, clarify our position or write a post, let me know. Now that I’ve become an AMPhibian (see what I did there?), send any questions, concerns or suggestions my way.