Model answer
Clarify & scope
I’d treat AMP as a user-experience and open-web question, not a yes-or-no browser compatibility decision. AMP can make pages load quickly on mobile, but its distribution through Google’s cache and the use of separate AMP URLs can weaken publisher control and make it harder for users to know which site they’re visiting. Mozilla should preserve access to content while giving users more choice and promoting performance improvements that work across the open web.
User segments & pain points
I’d prioritize mobile readers on slow or expensive connections. They need pages that load quickly, use little data, and behave reliably; they also need to trust who is serving the page and be able to reach the publisher’s canonical site. Publishers and developers matter too, but I’d judge decisions by their effect on readers first.
Goals & success metrics
The North Star would be successful, trusted content consumption on mobile, not the number of AMP pages Firefox blocks or converts. I’d track time to usable content, page-load success, data transferred, and reader engagement, segmented by network quality and whether the page is AMP or standard HTML. Guardrails would include site compatibility, crashes, privacy, and user reports that pages are missing content or unexpectedly changing URLs.
Solutions
- Keep AMP pages working in Firefox. Breaking or degrading them would punish readers more than it would change publisher incentives.
- Improve performance for the web generally: invest in Firefox Android loading, caching, efficient rendering, and standards-based web capabilities. Share performance guidance with publishers and support interoperable standards rather than a Mozilla-specific format.
- Give users clear, optional control when an AMP page is served from a cache—for example, a way to navigate to the publisher’s canonical URL when it is available. Make this transparent and reversible; don’t silently rewrite pages or promise that every conversion will work.
Recommendation: Support AMP as content, but don’t make AMP the solution Mozilla advocates for. Focus Mozilla’s engineering and advocacy on fast, interoperable web pages and user choice.
Prioritization & trade-offs
I’d prioritize general mobile performance first: it benefits readers regardless of publisher or format. A canonical-link control is a smaller, opt-in follow-up. Automatic AMP-to-HTML rewriting might offer more control, but it risks breaking pages, adding maintenance burden, and confusing users about the source of content.
MVP, measurement & rollout
Start with a Firefox Android performance baseline and a small usability study of readers on constrained networks. Prototype an optional canonical-link action, test compatibility across a representative set of AMP pages, then roll it out behind a preference or experiment. Compare performance and successful reading against a control group, monitor the guardrails, and expand only if users gain control without losing speed or reliability.