#204 – suggestions

 Hi.

A couple of thoughts:

(1) What is your rational for defaulting to show the non-AMP website on mobile devices while providing the AMP pages for Google to show in search results? Your AMP pages work so well and load so fast that it would be nice to have the option to default to showing them in mobile while using non-AMP pages in non-mobile use.

(2) Sometimes my non-AMP pages don't translate to AMP as well as I would like. I can then design a separate page for AMP use. It would be nice to be able to edit the AMP menu to replace original pages with pages specifically designed for AMP where appropriate.

(3) FYI - Apparently my IDX does not work in AMP application because it is designed using inline JS. That is being changed and my programmer will make a new version available to me for Beta testing next week. He assures me that the new version will be 100% AMP compatible. Fingers crossed!

Thanks.

Hi Andy

(1) What is your rational for defaulting to show the non-AMP website on mobile devices while providing the AMP pages for Google to show in search results? Your AMP pages work so well and load so fast that it would be nice to have the option to default to showing them in mobile while using non-AMP pages in non-mobile use.

AMP pages are rarely fully featured, they often miss things from the full, responsive versions.

I see no actual reason in favor of defaulting to showing the AMP pages, which is why I never implemented that option in our WordPress plugin - we had that from the start in our Joomla plugin, due to a couple customers requests but that was a bad idea and I never implemented it on WordPress.

The actual way to do this is IF you can produce a fully featured AMP page then always use AMP, including on desktop. But having both a desktop version and showing the AMP version to mobile users does not make any sense in general. The only exception would be if your site is very ancient and you do not have a responsive or mobile version. Don't think many people are in that position right now.

(2) Sometimes my non-AMP pages don't translate to AMP as well as I would like. I can then design a separate page for AMP use. It would be nice to be able to edit the AMP menu to replace original pages with pages specifically designed for AMP where appropriate.

AMP menus are just regular menus. It's common to create one or more menus for the AMP version, where you put exactly what you want. Then you select which menu you want to display on AMP pages. See this page of documentation, there are many options for including menus.

(3) FYI - Apparently my IDX does not work in AMP application because it is designed using inline JS. That is being changed and my programmer will make a new version available to me for Beta testing next week. He assures me that the new version will be 100% AMP compatible. Fingers crossed!

Indeed! That's good news and unfortunately sometimes comes with AMP implementation!

Best regards

Thank you and best regards.