About that ‘mobile’ in Accelerated Mobile Pages
There’s nothing inherently ‘mobile’ about AMP. AMP is designed to be mobile friendly, and with slow hardware and high latency connections, the boost you get with AMP on smartphones is going to be felt a lot stronger than on desktops. But AMP isn’t mobile only – it’s mobile first.
.. But the paired mode – creating a separate path for your AMP pages that will only ever be seen on mobile (e.g. through a redirect to a /amp/ directory) – comes with a set of issues attached: Sharing links between AMP and Desktop sites can fail in many ways, like showing a mobile variant on a way-too-large Desktop browser. Content that’s available on the Desktop pages might be accidentally missing or outdated on the functionally reduced mobile AMP pages. You’re now repeating many mistakes of the m.dot world (m.dot describes having an entirely seperate version of your site for mobile).
Instead, you can, and probably should, go “standalone”. This means you’ll use AMP like any other web component library out there. Instead of branching out your pages, you continue to have a single, AMP-enabled page.