Yes, it does provide screen real estate, but also features that cannot be achieved without AMP such as fast swiping between results.
-
-
Replying to @cramforce @domenic and
But you earlier said that there's no point in standardizing AMP because the primitives already exist. This is a counterexample.
1 reply 0 retweets 0 likes -
Replying to @wycats @cramforce and
Yehuda Katz 🥨 Retweeted Malte Ubl, Immigrant
https://twitter.com/cramforce/status/900794363172724736 … The deep coupling between Google Search and AMP is allowing you to miss obvious missing primitives in good faith.
Yehuda Katz 🥨 added,
1 reply 0 retweets 0 likes -
The process is under way. I'm not sure it will yield something that people want, but I'm hopeful.
2 replies 0 retweets 0 likes -
Replying to @cramforce @domenic and
The process is under way in public? Or internal to Google?
1 reply 0 retweets 0 likes -
Feature policy is the direct outcome of the work. Trying to push for stateless prefetch.
1 reply 0 retweets 1 like -
Replying to @cramforce @wycats and
Needless to say, I want to use all these things in AMP, so I can delete a bunch of code.
1 reply 0 retweets 0 likes -
Replying to @cramforce @domenic and
I think it's not an understatement to say that many people would LOVE to see a standard solution to the search page problem.
1 reply 0 retweets 1 like -
Replying to @wycats @cramforce and
Lots of people would love to help too. Is there a reason the preliminary work needs to happen inside Google?
2 replies 0 retweets 1 like -
Replying to @wycats @cramforce and
where are these lots of people? Would love to meet them. Have been calling out for contributors for months.
1 reply 0 retweets 1 like
The lots of people don't want to work on AMP, but rather standards work that would make Google Search uncoupled from AMP.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.