Sandboxing Email Fixes Inside Litmus
Kelvin Liu, Founding Engineer at Beacons, on the email product development process
This shows Litmus working less like a source of truth and more like a sandbox sitting between code and inbox. Beacons builds emails as React blocks, sends the generated HTML into Litmus, then uses Litmus to make tiny HTML fixes and instantly re-run screenshots across Gmail, Apple Mail, and Outlook. That matters because email bugs are usually small rendering breakages, so the fastest way to learn is to tweak the output directly before deciding what belongs back in the product codebase.
-
For Beacons, this shortcut exists because their real source files are abstract blocks, not hand edited HTML. Litmus lets the team test the final rendered output without reopening React files, rebuilding, and resending every time a padding, image, or table issue appears in Outlook.
-
This is different from teams like Podia, where email HTML goes through a compile step before testing. There, edits inside Litmus are useful for experiments, but the real fix still has to be made upstream and recompiled, because the tested HTML is machine generated and can drift from the actual source.
-
The broader product split is that Litmus is strongest as a testing and preview layer, while Parcel is built more like an email IDE. Agencies using Parcel emphasize code editing, inspect element, shared files, and richer developer workflows, while Litmus remains valuable for quick previews and lightweight code pokes inside the QA loop.
The next step for the market is tighter links between component based email systems and automated previewing. As creator platforms like Beacons add more reusable blocks and more message types, the winning tools will collapse edit, test, approval, and export into one loop, so teams spend less time manually probing broken clients and more time shipping branded emails safely at scale.