Live data from Hacker News

Why does email development have to suck? – Explaining all the 's and 's

dodov.dev

71–80 of 183 posts

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#71

Earlier quoted context omitted.

Ironically, plain text emails actually do better for us - the problem is that plaintext emails are often more likely to be caught up by spam filters.

The data I've seen suggests the opposite?

All of our internal tests have confirmed this, and even the email providers have more or less confirmed the same thing: https://blog.hubspot.com/marketing/plain-text-vs-html-emails...

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#72
post #3

> An email is essentially just an HTML document, like a web page, except it's visualized in an email client, rather than a web browser. However, both are capable of rendering, which is the process of turning HTML code into text, rectangles, and images, i.e. the visualization of the content. No, it is not. An email is a text document. That document might be HTML, but it doesn't have to be. And if such email is sent to…

You will hate me then. I have recently started to embrace html emails. I needed to book a room for a series of events and color highlightinged the available options.

Another time I needed to provide a summary of options for fees and that got added as a table with colours to indicate fees, profits and losses.

And I don’t care at all if it meant that it could not be read in mutt. At some point we have to march forward or we will never progress at all.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#73

Earlier quoted context omitted.

Transactional mail is not marketing mail. It's typically a notification in response to an action you initiated on some web application. https://postmarkapp.com/blog/what-is-transactional-email-and...

OK. So what, I'm not going to complete my password reset notification because the page isn't beautiful? If you are tracking response rates it is because people aren't expecting an email, because they didn't ask for one (i.e. it isn't a password reset notification). GP is right - I want information I /need/ to be in an email in a succinct format, and I don't want emails I don't need.

1. Yes, normal people who don’t read HN have less trust in a plaintext email.

2. Yes, abandonment will be higher if the user can’t click the password reset link in the email.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#74
post #53

Wouldn't most of these pains go away if you simply could include style tags (not attributes) in the body? I've always wondered why it's possible to include script tags pretty much everywhere but not style tags.

Nope, that doesn't work as well. I tested it before finishing up the article a few days ago. If you put `` in the ``, it gets removed when the email is forwarded and it still looks like shit.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#75
post #66

Earlier quoted context omitted.

This is an absurdly wrong, yet characteristically HN take. Transactional mail typically requires some hyperlink for the average user.

No, it doesn't. Email is a great feedback medium. "If you want to continue with the subscription, reply with the word YES on a line by itself. You can put comments on other lines and we will read them." do-not-reply@marketing.com is one of the stupid innovations by people who can't automate their email. Transactional email gets handled by robots and fed into a ticketing system when it goes awry. Treat your customers…

Why would transactional mail come from do-not-reply@marketing.com?

Transactional mail is not marketing mail.

It’s not a good look to declare things as stupid when you aren’t sure what the discussion is about.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#76
post #3

> An email is essentially just an HTML document, like a web page, except it's visualized in an email client, rather than a web browser. However, both are capable of rendering, which is the process of turning HTML code into text, rectangles, and images, i.e. the visualization of the content. No, it is not. An email is a text document. That document might be HTML, but it doesn't have to be. And if such email is sent to…

Once again the stereotypical HN comment of « no this is all wrong, my way is right »

For all communications that matter today, email is HTML. No one cares that JohnFen choses to not render them as HTML.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#77

"So if you want a reasonable portion of users to see your email as intended, let's say 95%, you have to stick to the most basic features of HTML and CSS..." Or, you know, you could just SEND TEXT.

Wow so clever. That totally solves the need to show logos and images, colors, formatting, centering things, making things visually appealing, etc.

Can you conceive your needs and your basic understanding of an issue is not, in fact, the whole thing?

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#78

I don't understand the insistence on building "beautiful" emails. I'm not the kind of person to insist on text-only e-mail, but I do think it's ridiculous to spend lots of time and money making e-mails that look like fully-fledged Web documents. Either your message does have some useful information for the reader, in which case say that and then get out of my way, or it doesn't , in which case you're a spammer. There…

It's weird that your can't conceive of useful information that benefits from HTML elements (images, actual tables, links) and layout design to make it more readable. In pretty much the same way a web page does. I benefit from this as the reader. I want it.

That non-existent third option is critical for good communication.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#79
post #66

Earlier quoted context omitted.

This is an absurdly wrong, yet characteristically HN take. Transactional mail typically requires some hyperlink for the average user.

No, it doesn't. Email is a great feedback medium. "If you want to continue with the subscription, reply with the word YES on a line by itself. You can put comments on other lines and we will read them." do-not-reply@marketing.com is one of the stupid innovations by people who can't automate their email. Transactional email gets handled by robots and fed into a ticketing system when it goes awry. Treat your customers…

Now you need to deal with « yes », « Yes », « YES. », HTML wrapping, user signatures, dangling spaces, etc.

I’ve worked with a system that let users order domain names by email and it was a nightmare to maintain. Don’t EVER build a system that relies on reading and parsing emails sent by users, it WILL fail horribly.

Re: Why does email development have to suck? – Explaining all the <tr>'s and <td>'s

#80

Text. Just use damn text. Nobody wants to look at your logo. Why biz people have to ruin everything.

If only it was a simple logo. My HRs send emails with a full blown wallpaper on top, which stretches the inbox on a smaller screen so much that horizontal scroll appears, and text below it also overflows. Or when I disabple dynamic content, then they manage to create links inside the graphical buttons with no alt text, invisible without the picture. And these are people whose main job are emails. Sigh...
Post reply on HN