I joined October SFHTML5 last night, topic was Accelerated Mobile Pages Project.
AMP Project Page:
https://www.ampproject.org/
Google's Blog Post:
Introducing the Accelerated Mobile Pages Project, for a faster, open mobile web
It's an open source project, GitHub Page is here:
https://github.com/ampproject
We talk a lot about performance... we all know performance matters. But what does "slow" mean? "Slowness" is contextual... but as Google's philosophy "Ten things we know to be true" says, we should "focus on user and all else will follow" - so developers should really think about "What does the user feel?" using the service you have built.
One thing we experience is this clash of "monetization and user acquisition" vs "user experience".
AMP is trying to solve that problem, building a win-win-win for users, publishers and advertisers.
Videos:
RAIL: Putting the User at the Center of Performance with Paul Irish
Perf audit: Loading performance
AMP: Accelerated Mobile Pages with Paul Bakaus
AMP Anatomy with Malte Ubl
Q&A with Paul Irish, Malte Ubl, Jordan Adler, and Paul Bakaus
Disclaimer: The opinions expressed here are my own, and do not reflect those of my employer. -Fumi Yamazaki
AMP Project Page:
https://www.ampproject.org/
Google's Blog Post:
Introducing the Accelerated Mobile Pages Project, for a faster, open mobile web
It's an open source project, GitHub Page is here:
https://github.com/ampproject
We talk a lot about performance... we all know performance matters. But what does "slow" mean? "Slowness" is contextual... but as Google's philosophy "Ten things we know to be true" says, we should "focus on user and all else will follow" - so developers should really think about "What does the user feel?" using the service you have built.
One thing we experience is this clash of "monetization and user acquisition" vs "user experience".
This slide got a big reaction! Very true - devs know ad cruft hurts users #sfhtml5 #webdev pic.twitter.com/6JuEw2okwy
— Alan Hogan (@AlanHogan) October 24, 2015
AMP is trying to solve that problem, building a win-win-win for users, publishers and advertisers.
This slide explains why AMP (Accelerated Mobile Pages) is a winning proposition #sfhtml5 @google #webdev pic.twitter.com/dGCb5io4bh
— b01dface (@b01dface) October 24, 2015
AMP project consists of AMP HTML, AMP JS and AMP CDN. No user-authored JS, subset of tags and selectors, but instead it consists of advanced components like amp-img tag, amp-ad tag which is a custom tag for ads, amp-twitter tag that shows embedded tweet, etc.
It's still an early stage project, and the team welcomes you all to join the project, try it out, give feedback and contribute to the project.
Videos:
RAIL: Putting the User at the Center of Performance with Paul Irish
Perf audit: Loading performance
#sfhtml5 Wikimedia team printed Chrome DevTools & analyzed what is slowing down page load, ended up doubling speed! https://t.co/OYZHYxVw9B
— Fumi (@Fumi) October 24, 2015
AMP: Accelerated Mobile Pages with Paul Bakaus
AMP Anatomy with Malte Ubl
Q&A with Paul Irish, Malte Ubl, Jordan Adler, and Paul Bakaus
Disclaimer: The opinions expressed here are my own, and do not reflect those of my employer. -Fumi Yamazaki
0 件のコメント:
コメントを投稿