{"id":968,"date":"2014-11-05T17:24:37","date_gmt":"2014-11-05T17:24:37","guid":{"rendered":"http:\/\/freshinbox.com\/blog\/?p=968"},"modified":"2015-02-07T09:04:13","modified_gmt":"2015-02-07T09:04:13","slug":"why-better-css-support-in-outlook-benefits-microsoft","status":"publish","type":"post","link":"https:\/\/freshinbox.com\/blog\/why-better-css-support-in-outlook-benefits-microsoft\/","title":{"rendered":"Why Better CSS Support in Outlook Is Good For Microsoft #letsfixemail"},"content":{"rendered":"



Dear Microsoft,<\/span>

<\/p>\n

With the next version of Office<\/a> around the corner, the number one question on the minds of email designers and coders is:

<\/p>\n

   “Will Outlook finally support modern web standards?”<\/em>

<\/p>\n

Ever since Outlook 2007 the Word rendering engine<\/a> has been used to render emails in Outlook. The Word engine has limited support<\/a> for CSS based layouts and ever since then email coders have had to design around its numerous quirks<\/a>.<\/p>\n

In fact Outlook is the ONLY reason all emails are still designed with tables<\/a>.<\/p>\n

Lets explore why Web Standards support in Outlook is a good idea as well as one possible way to get there.


<\/p>\n

How Modern Email Support in Outlook Benefits Microsoft<\/h4>\n
Better User Experience<\/h5>\n

As more and more developers and designers cut their teeth on modern HTML5 and CSS3 designs, the art of table-making will become obscure. Unless Outlook supports modern email, Outlook users will see ever increasing instances of broken emails<\/a> which negatively impact their experience.

<\/p>\n

Consistent and Modern Product Experience<\/h5>\n

Outlook.com, the Windows Phone email client, and even surprisingly Outlook 2011 for the Mac and the recently released Outlook for Mac<\/a> already support HTML5 and CSS3. What better way to showcase a consistent experience between your products than to add the same support to Outlook on the PC!
<\/p>\n

Supports Office 365 Developer Programs<\/h5>\n

One of the key advantages of the Office 365 developer program<\/a> is that developers can leverage their existing HTML5 and CSS3 investments.<\/p>\n

 \u201cThe Office 365 user experience and app extensions are designed using industry open standards like HTML, CSS3\u201d<\/em><\/p>\n

However, when developers create apps that compose and send emails, imagine the support complaints you\u2019d be getting from developers asking why their HTML5 and CSS3 investments don’t work inside email.
<\/p>\n

Perception and Goodwill<\/h5>\n

At one time the Internet Explorer browser (IE6) had a reputation as a browser that didn’t support web standards. IE8 finally addressed that with much better support for web standards.<\/p>\n

However, during a recent online interview<\/a>, a member of the Internet Explorer team admitted that the negative perception of Internet Explorer is still so prevalent that they considered retiring the Internet Explorer name!<\/p>\n

In the same vein, having developers complain about Outlook in social media can’t be good.<\/p>\n

\n

@Outlook<\/a> https:\/\/t.co\/dSw0Sz5R1o<\/a> shows how poor HTML\/CSS support is for Outlook clients, would love to see commitment to improve #emailgeeks<\/a><\/p>\n

— Kevin Mandeville (@KEVINgotbounce) November 4, 2014<\/a><\/p><\/blockquote>\n

\n

New slogan for @Microsoft<\/a> @Outlook<\/a> – Making #HTML<\/a> email #design<\/a> look like crap for over two decades. . #webdesign<\/a> #emailmarketing<\/a> #CSS<\/a><\/p>\n

— Chris Spence (@CreativeJOOS) November 3, 2014<\/a><\/p><\/blockquote>\n

\n

Doing proper email design for the first time. Lolling at Outlook 2007\u20132013's CSS support. http:\/\/t.co\/VPgEebNCYo<\/a><\/p>\n

— Joni Korpi (@jonikorpi) October 7, 2014<\/a><\/p><\/blockquote>\n

\n

Daaaaamn you, Outlook 2007, 2010, 2013!!!!!!!!!<\/p>\n

— jennz0r (@mybluewristband) December 29, 2014<\/a><\/p><\/blockquote>\n

\n

A frustrating day battling Outlook with HTML email layouts. It's like going back in time before web standards. #emaildesign<\/a> #toeachhisown<\/a><\/p>\n

— Bert Mahoney (@berchman) February 4, 2015<\/a><\/p><\/blockquote>\n