Podia's Email Editor for Legacy Clients

Supporting old email clients forces a product team to build more like it is coding for Word than for the modern web. In practice that means writing simple HTML, pushing as much CSS inline as possible, swapping SVGs for PNGs, and using tables for layout because old Outlook and Lotus Notes versions break on newer patterns. That tradeoff fits Podia because reliable delivery across creator audiences matters more than elegant code.

• The workflow was compile first, test second. Podia wrote basic HTML and CSS, ran it through Roadie to inline styles, then pasted the generated HTML into Litmus. That let the team fix compatibility at the CSS layer without constantly rewriting template structure.
  1 sacra 3 github
• This is the standard playbook for broad client coverage. Can I Email tracks uneven support for things as basic as style tags, and Litmus still offers previews for legacy environments like Outlook 2007 and Lotus Notes 8.5, which explains why teams code to the lowest common denominator.
  2 caniemail 4 litmus 5 litmus
• The contrast with tools like Parcel is useful. Litmus is mainly a preview and QA product, while Parcel is built more like an email IDE. Podia needed proof that compiled emails rendered safely in old clients, not a richer coding environment.
  6 sacra 7 sacra 8 sacra

Email builders aimed at creators will keep converging on this approach. The winning products will hide the ugly parts, tables, inline CSS, client specific fallbacks, behind a simple editor, while preserving enough control to keep messages stable in Outlook heavy and long tail inbox environments.