I'll take a look. In general: AMP wants to limit itself to content-only use cases. Nothing that falls into app realm.
-
-
Replying to @cramforce
sure, but lots of content sites have "rich" content or social structure (like Bustle, Vox or Discourse)
1 reply 0 retweets 0 likes -
Replying to @wycats
yeah, so what you describe is exactly what we want to support.
2 replies 0 retweets 0 likes -
Replying to @cramforce
a lot of the perf work I've done for the past 18 months has been for LinkedIn Mobile, which is also quite content rich.
1 reply 0 retweets 0 likes -
Replying to @wycats @cramforce
would you say the criteria is: "expects a lot of traffic from SRPs"?
1 reply 0 retweets 0 likes -
-
Replying to @cramforce
what counts as "content" then? Journalism? Or something else?
1 reply 0 retweets 0 likes -
Replying to @wycats
mostly: works with stale-while-revalidate caching model. Does not need app like functionality. Wants to be embedded into other apps.
2 replies 0 retweets 1 like -
Replying to @cramforce
I'd think pages that were meant to be driven from SRPs would satisfy these requirements almost by definition.
1 reply 0 retweets 0 likes -
Replying to @wycats
I don't think much about search stuff. But need to take my date night more serious now :) cheers.
1 reply 0 retweets 2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.