Back in February at AMP Conf 2018 in Amsterdam, Gmail announced support for interactive email and real-time dynamic content in email powered by AMP (Accelerated Mobile Pages), an open-source initiative stemmed in improving web performance.
You can watch the full announcement below:
A separate MIME-type of
text-x-amphtml of an email will be required by Gmail in order to render the interactive, AMP-powered version.
The entirety of AMP won't be supported by Gmail, only a subset. Here's the full list of supported components:
Examples of ⚡️AMP4Email
🤷♂️ Gmail hasn't officially listed anything. The video announcement showcases Gmail webmail, but Gmail rendering is highly fragmented between webmail, mobile, and different account types. My best guess is this will work where media query support for Gmail works, which would notably exclude POP/IMAP accounts using Gmail.
🤷♂️ Half a year later, Gmail still hasn't shared expected an release date. Developers can apply for access here, but I'm unaware of anybody in the community having success with this application. Seth Weisfeld from Pinterest stated that it's "looking more like Q1" for a public release at #LitmusLive panel in San Francisco and Sparkpost noted the same in a recent webinar about interactive email.
Here was my instant reaction to the ⚡️AMP4Email announcement when it happened on The Email Design Podcast:
✅ Improved analytics tracking: Gmail currently caches images which impacts our ability to accurately report Gmail opens. ⚡️AMP4Email offers the potential to work around this limitation to record Gmail opens and provides the ability to more easily track click events for interactive email. Today, interactive email requires an individual tracking pixel fired off as a background image for each action, but can only measure *if* a user interacts with an element and not how many times they interact with an element. ⚡️AMP4Email's dynamic content ability will allow us to inject dynamic pixels for every interactive event we want to track.
❌ Creates further email rendering fragmentation: This is perhaps the most problematic problem to ⚡️AMP4Email. We don't need further fragmentation and various implementations for HTML email. This moves the industry further away from a unified set of standards. I don't see Apple or Microsoft adopting AMP into their email clients, either (which are the only other two that matter).
❌ Lack of ESP support: There's been virtually *no* support for ⚡️AMP4Email by ESPs. I tweeted major ESPs back when this announcement was made asking about them supporting it. Only Sparkpost has publicly stated supporting this functionality in the near-term. Gmail massively missed on this and is out of touch with the email marketing community in this regard. Email marketers don't even have the ability to send emails with ⚡️AMP4Email support if they wanted to because the ESPs don't support it. It's like they put a luxury resort on Mars...sounds cool, but there's no way to get there. If Gmail was smart, their launch would have included some major ESPs announcing support for it. Or better yet, they would have used a JSON/Microdata approach like they are with Annotations in the Promotions Tab to get mass adoption right away instead (especially since they're only supporting a subset of components). That approach also has better potential for eventual cross-client support and standards.
❌ Duplicates development work: ⚡️AMP4Email requires a separate MIME-type for sending. I don't care if it's relatively lightweight on the code side, this creates extra work for every email that many will bypass. A new learning curve exists for email marketers to learn AMP altogether.
❌ Ads potential scares me: There's an
amp-ad component in AMP. I can't trust Google's intentions with this existence, as it opens up the possibility of polluting inboxes with ads or introducing pay-to-play inbox visibility.
Gmail's approach to interactive email is a developer-centric approach that is completely out of touch with the email marketing landscape and how it operates today. They are introducing functionality with massive barriers to adoption. Yet, it's completely in line with Gmail's security and privacy driven product culture.
I hope ⚡️AMP4Email fails. I doubt it will ever gain significant momentum or take off. Marketers and developers want to provide interactive and dynamic email experiences for subscribers, but ⚡️AMP4Email is the wrong implementation. We didn't ask for this. We don't want it this way. I'll play with it for educational purposes, but I hope you all join me in boycotting ⚡️AMP4Email and getting Gmail to improve HTML & CSS rendering and support standards instead.
Do you like or dislike Gmail's idea of ⚡️AMP4Email to support interactive and dynamic email? Will you develop emails with AMP just for Gmail? Let me know @KevinMandeville.
Like this article? Give it a share on Twitter.