4 ms·
The amount of effort it can take to the the actual link to the article is just insane. Trying to share something through your phone that has been AMP'd is basic
by JakeTheAndroid 6y ago
The amount of effort it can take to the the actual link to the article is just insane. Trying to share something through your phone that has been AMP'd is basically signaling it's not worth the effort to send the article at all.
Add that to how untrustworthy the link looks, it's just terrible execution on an idea that might have merit.
- what_ever 6y agoThat's not been my experience on Android. I just opened an AMP link from Google search which opened in Chrome based WebView. Clicking on share - how I usually share things - presented me with the actual link of the article. From there I could copy or open any of the apps to actually share the link. AFAIK, this has been long fixed. Disc: Googler.
- ec109685 6y agoOn iOS it is the same way. Apple also figures out the canonical link and shares that.
- osrec 6y agoIs your original Google search done in Chrome or via the Google "app"? I guess that's why your result opens in a WebView? I usually just go to google.com in Chrome to search for things, and the amp link in the address bar is really rather confusing.
- JakeTheAndroid 6y agoI usually search for things using the Google widget on my home screen. And from there I will "Open the link in Chrome". This means that I end up opening an massive AMP link not the direct link in Chrome. So I have to basically copy the title of the article from the AMP'd version, and paste that into Google through a new Chrome tab and usually that works. But why is using the Google AMP service through the Google widget so terrible? I would expect a more fluid experience, but you end up with this really terrible experience trying to leverage the Google ecosystem. Theres nothing from stopping me from opening FireFox and searching the article title in Bing or DDG at that point.