I think there's a time and place to use rich HTML emails (and a time and place not to).
For me the time to is newsletters, promotional emails, great-big new feature emails etc. The sort of time you want to showcase something great.
However system emails, like password resets and invitations are times when you need to be efficient. I don't think they should be rich HTML emails.
System emails are not for looking at and enjoying, they're there to make the system run as smoothly as possible. To get the user from A to B.
Mailrox is all about speeding up development. It was a really tricky decision to make the invite email non-fancy, but I think it's the right one. If you see what I mean.
I think there's a time and place to use rich HTML emails (and a time and place not to).
For me the time to is newsletters, promotional emails, great-big new feature emails etc. The sort of time you want to showcase something great.
However system emails, like password resets and invitations are times when you need to be efficient. I don't think they should be rich HTML emails.
System emails are not for looking at and enjoying, they're there to make the system run as smoothly as possible. To get the user from A to B.
Mailrox is all about speeding up development. It was a really tricky decision to make the invite email non-fancy, but I think it's the right one. If you see what I mean.