August 26th, 2019

Replying to a tweet from @cramforce

Yes, I linked to that in my post.

But this wouldn’t be “arbitrary” content—there would be strict criteria for admission.

It feels like there’s a big spectrum between “arbitrary” and “only AMP”.

42° N , 88° E

Also on Twitter

Reply Retweet Favourite

Responses

Malte Ubl

Yeah, it’s just really complicated for the page author to get right, and roughly ~zero docs that aren’t AMP on the web comply today. The proposed method works for all docs and is also almost certainly going to ship faster.

# Posted by Malte Ubl on Monday, August 26th, 2019 at 6:55pm

Jeremy Keith

Oh, yes, I wasn’t suggesting that any pages are ready to be hosted and pre-rendered as they are today—there would certainly need to be some rejiggng done, either by the author or the host. adactio.com/notes/15730

Malte Ubl

Oh, and the proposed path fixes the URL issue. I really don’t want to go further down the pre-fix path. AMP is also switching to preloading for non-embedded experiences, so I really think aligning there makes sense.

# Posted by Malte Ubl on Monday, August 26th, 2019 at 7:00pm

Malte Ubl

The next thing that is ready is preloading and “speed assessment via metrics”. No timeline, but within reach. Embedding cases like the image search swipe up are blocked on progress on portals.

# Posted by Malte Ubl on Monday, August 26th, 2019 at 7:11pm

Have you published a response to this? :