2025–2026 · in progressOutlook · Windows (new)Critical
Word rendering engine → Chromium
New Outlook renders with a Chromium engine — like Outlook.com — instead of the old Word engine. It gains modern CSS (flexbox, media queries, background images) and drops the Word-engine crutches: MSO conditional comments are ignored, VML buttons and backgrounds stop applying, and Outlook-only ghost tables can behave differently. The danger is silent — fallbacks built for classic Outlook simply vanish in new Outlook.
- Patterns hit
- Any template that leans on MSO conditional comments (
<!--[if mso]>), VML buttons or backgrounds, ghost tables, or fixed widths tuned for the Word engine. - Who it affects
- Almost any template built before ~2024 that relies on Outlook-only fallbacks to hold its shape.
- The fix
- Make sure the design holds up without the Outlook-only crutches, then retest in new Outlook.
- Timeline
- Business auto-migration began Jan 2025 · enterprise from Apr 2026 · Word-engine support ending ~Oct 2026
iOS 18 (2024) → 18.2 (Dec 2024) → 2025Apple Mail · Apple IntelligenceInfo
AI summaries, inbox categories & Branded Mail
On Apple-Intelligence devices, AI message summaries can replace the preview / preheader under the subject line — generated on-device, per person, and not controllable by markup, ALT text or hidden preheader text. Inbox categories with Group-by-Sender change how a send is seen, and Branded Mail shows the sender’s logo when registered with Apple Business Connect (DKIM required).
- Patterns hit
- Reliance on hidden-preheader tricks; the top ~350px of a design (what shows in grouped view); critical text baked into images.
- Who it affects
- Every send seen on an Apple-Intelligence device — increasingly the norm on iPhone, iPad and Mac.
- The fix
- Lead with meaningful live text, vary the top of each design, keep critical words out of images, and register Branded Mail.
- Timeline
- Announced iOS 18 · shipped iOS 18.2 Dec 2024 · categories to Mac/iPad in the 2025 line
Sep 2026Gmail · iOS + Android appsWatch
Gmail now honours color-scheme — you can force light
Gmail’s iOS and Android apps now support the color-scheme meta tag, so a sender can finally force the light version with <meta name='color-scheme' content='light only'>. That resolves the long-standing forced-dark-mode issue, where Gmail applied its own partial inversion with no author control. One catch: light only can stop your prefers-color-scheme: dark styles from applying in clients that do support author dark mode, like Apple Mail.
- Patterns hit
- Templates that rely on
prefers-color-scheme: dark for Apple Mail; anyone adding color-scheme: light only to tame Gmail. - Who it affects
- Senders who want a predictable light render in Gmail — and anyone who also ships an Apple Mail dark treatment.
- The fix
- Force light in Gmail with the meta tag, but pair it with
:root{ color-scheme: light dark; } so your Apple Mail dark styles keep working. - Timeline
- Reported Sep 2026 · both Gmail apps
OngoingGmail / Yahoo · AMP for emailWatch
AMP / dynamic email — future uncertain
AMP-for-email (dynamic email) adoption has stalled, and its long-term support in Gmail and Yahoo is an open question. Worth watching before building anything that depends on it.
- Patterns hit
- Templates that ship a dynamic (AMP) version.
- Who it affects
- The few programmes that actually use dynamic email.
- The fix
- Keep the plain-HTML version fully functional on its own; treat AMP as an enhancement, never the foundation.
- Timeline
- Watch · low priority