Parcel as Builder, Litmus Tester at Figma

This shows Parcel won the core workflow while Litmus stayed as a specialized testing utility. At Figma, the day to day job is not just checking how an email renders, it is writing code, reusing templates, collecting comments, and shipping campaigns fast. Parcel fits that production loop, while Litmus stays useful when a team needs inbox previews for a brand new template or a major transactional email layout update.

• The practical split is builder versus tester. Figma writes marketing emails in Parcel, but keeps Litmus for previewing new templates and for product and engineering teams testing transactional emails. That means the tools can coexist without actually serving the same buyer need inside the company.
  1 sacra 2 sacra 4 sacra
• Other email developers describe the same line. Parcel is treated more like a VS Code for email, with components, versioning, code inspection, and feedback. Litmus is treated primarily as the place to see how HTML will break across Outlook, Gmail, and other inboxes.
  3 sacra 4 sacra 5 sacra 6 sacra
• That difference matters economically. Figma did not want a broad group of product and engineering users inside Parcel, and Litmus could be shared for occasional testing. Parcel becomes most valuable when a dedicated email team is producing high volume marketing work every week, not occasional QA runs.
  1 sacra 2 sacra 4 sacra

The market is moving toward one system owning more of the email production workflow. As preview features improve inside coding tools, more teams will reserve Litmus like products for edge cases and large layout changes, while the main budget and daily usage shift to the tool where teams actually build and review emails.