Talking Code
Stop Treating Email Like the Web
Episode Summary
Justine Jordan explains how your company should treat email, the difference between designing for email and the web, and what you can do to up your open rates.
Episode Notes
Justine Jordan explains how your company should treat email, the difference between designing for email and the web, and what you can do to up your open rates.
Here's what to listen for:
- 00:44 How are most people reading email today?
- 02:46 What are most companies doing to send email?
- 04:23 What’s the distinction between transactional and marketing email companies?
- 06:58 What are the downsides of building your own email platform?
- 08:35 What are the differences between Mailchimp and Mandrill?
- 11:30 Is designing an email the same thing as designing a web page?
- 14:10 What does it mean practically that email and web are different?
- 16:36 Why is that you might design an email and it looks great in Gmail but it looks completely different in Outlook?
- 20:20 How do you feel about automated CSS inlining?
- 22:53 What is responsive design, how does it work, and what does it mean for email?
- 25:57 Are there any challenges with non-integrated design and development teams where a designer is building an email to look a certain way and now a developer has to try to make it work on different devices?
- 29:45 What’s the experience difference between responsive and non-responsive emails?
- 32:57 What happens to my business if my emails look bad on mobile devices?
- 34:55 What are good takeaways for teams trying to make their emails look good everywhere?
- 36:25 As a startup, how much work should I be putting into my emails?
- 38:36 What can I do to support my developers in making email easier?
- 40:34 Can you share what Litmus does?