• 0

Office 2013 Interface - Really? This is The Best They Can Do?


Question

Just when you thought things couldn't get any worse on the Microsoft Windows 8 world...

Take a look at the new Office 2013. This is a screenshot of Microsoft Word 2013 and Outlook 2013, the final version. My question on my mind is: What kind of drugs were those designers doing when they did this? I got a headache from looking at this for over 5 minutes. This is ridiculously white. Too bright for the eyes and no way to change it to anything acceptable, except for a light gray or dark gray, which are not darker at all and don't make things any better.

adtqW1I6.jpg

acp08WWs.jpg

  • Like 3

Recommended Posts

  • 0

I don't see how the dark grey theme can be considered too bright for your eyes. It's not exactly dark, but unless you literally have your monitors brightness blasted up full, it's very much fine.

  • 0

I like the new look better, personally, its sharp, clean, and simple. I thought Microsoft was too stuck on shading things. White doesn't bother me. A lot of minimalistic websites; Bing, Google, etc. rely mostly on white. Its a change for Office, that's for sure.

I'm not saying that as a fanboy, I like Windows 8 too, but am not afraid to criticize their UI decisions when I don't like them.

  • 0

I guess beauty is in the eye of the beholder because I think it's great! Soft and easy to view/use, very functional on desktop and tablet. Superb actually. Best Office yet.

Really slick. I would like all my Windows apps (desktop apps) to look and function similarly.

  • 0

I'm going back to Office 2010. This white is driving me crazy. I have a bad headache right now. I can't deal with this sh...t. This is horrible.

Epic fail Microsoft. Sorry fanboys, but this UI really sucks.

What about the Light Gray and Dark Gray options?

  • 0

Excel and OneNote work pretty well in 2013, but I agree with Outlook 2013. That will be the first Outlook, I will not upgrade to because they got rid of the To-Do bar. Metrics probably showed nobody interacted with it, but metrics cannot show that I didn't use it! I need that for my upcoming meetings!

I think the complaints about the white though is because of your monitors. Turn the brightness down and it won't be that bad, and yes, you are supposed to turn it down!

  • 0

But what's killing 2013 for me is the terrible font rendering, and killing off hardware acceleration to "fix" it isn't an option.

It's perfectly possible to disable Words sub-pixel font positioning if you wish, without disabled hardware acceleration. (The Text won't be hardware accelerated anymore of course, but the rest will). Though I personally think it looks much nicer :p

  • 0

I like the new design actually, but just basing this opinion on the screenshots, I have not used it yet on a daily basis.

But I also prefer the simpler, minimalistic approach to UI design. So I like it, a lot actually, based on the screenshots.

  • 0

They don't really help the eyes.

They look fine for me, so I guess I'm having a hard time understanding what is "horrible" about the interface. Can you post a screenshot and maybe point out what is the problem specifically with the Dark Gray option?

  • 0

Excel and OneNote work pretty well in 2013, but I agree with Outlook 2013. That will be the first Outlook, I will not upgrade to because they got rid of the To-Do bar. Metrics probably showed nobody interacted with it, but metrics cannot show that I didn't use it! I need that for my upcoming meetings!

I think the complaints about the white though is because of your monitors. Turn the brightness down and it won't be that bad, and yes, you are supposed to turn it down!

You have valid reasons for being displeased with Outlook based on your usage. It's a shame too. 2013 is the lightest, most well optimized Outlook yet. Outlook accounts for most of our Office Corporate desktop support and I'm happy with where it has gone. Hopefully you can utilize the rest of 2013.
  • 0

You know what was so nice about Office 2010 with a dark theme? It wasn't about the user interface, it was about your content. With the dark theme it feels like the user interface is taking a step back and your content, whatever you're working on, is taking the spotlights. With Office 2013 it's the opposite. Your white page just drowns amidst a whole user interface of whiteness. There is almost no visible separation between content and tools. It is distracting and annoying to work with for longer periods of time.

And seriously, that "dark gray" setting is barely worth. It's not dark, it's just slightly less white.

This is a good content-focused UI. Microsoft had it and threw it away and that was a horrible mistake.

Shrjv.png

  • Like 3
  • 0

It's perfectly possible to disable Words sub-pixel font positioning if you wish, without disabled hardware acceleration. (The Text won't be hardware accelerated anymore of course, but the rest will). Though I personally think it looks much nicer :p

I wonder if there are video card/monitor specific issues because it really looks fantastic to me. Seriously. Whites have never bothered me but I do adjust the gamma and dynamic contrast using my monitor controls and Catalyst Control Panel to get it perfect for me.
  • 0

They look fine for me, so I guess I'm having a hard time understanding what is "horrible" about the interface. Can you post a screenshot and maybe point out what is the problem specifically with the Dark Gray option?

I already posted screenshots. Go back to the first page of the thread.

You know what was so nice about Office 2010 with a dark theme? It wasn't about the user interface, it was about your content. With the dark theme it feels like the user interface is taking a step back and your content, whatever you're working on, is taking the spotlights. With Office 2013 it's the opposite. Your white page just drowns amidst a whole user interface of whiteness. There is almost no visible separation between content and tools. It is distracting and annoying to work with for longer periods of time.

And seriously, that "dark gray" setting is barely worth. It's not dark, it's just slightly less white.

This is a good content-focused UI. Microsoft had it and threw it away and that was a horrible mistake.

Shrjv.png

(Y)

  • 0
Snip

While this doesn't bother me at all, I do see what you're talking about. I can see how it would bother some if they need that contrast.

  • 0

While this doesn't bother me at all, I do see what you're talking about. I can see how it would bother some if they need that contrast.

Thanks for understanding.

This is also one of my issues with the lack of transparency in Windows 8. I think it's great how Windows 7's windows are transparent. Absolutely not because it looks fancy, but because it pulls focus away from it. The frame isn't important, it blends into the background. It's about what's inside the frame.

  • 0

I already posted screenshots. Go back to the first page of the thread.

(Y)

I actually thought the dark option in 2010 was way too dark, so our opinions are the opposite on the topic for this thread. But, for me to say 2010 was "horrible" is a stretch to say the least especially considering the Silver option worked great for me. So I was just curious if it was something actually horrible with the UI or you just have a preference for a darker appearance.

  • 0

Actually Office 2013 is not that bad... but it really needs the light gray theme, also, for those of us that are really bothered by all the white on nights, we can use f.lux to reduce eye strain considerably... it really works.

ofice2013.png

  • 0

I am using the 60-day trial, but how do I change it [Word] from all white? I am using the desktop version, not the ****ty Metro version!

File->Account->Theme

  • 0

Also 2013 preview really clashes with the rest of my setup:

and a sneak peek at the review I'm working on!

post-361542-0-63958700-1353184635.png

  • 0
It's perfectly possible to disable Words sub-pixel font positioning if you wish, without disabled hardware acceleration. (The Text won't be hardware accelerated anymore of course, but the rest will). Though I personally think it looks much nicer :p
I wonder if there are video card/monitor specific issues because it really looks fantastic to me. Seriously. Whites have never bothered me but I do adjust the gamma and dynamic contrast using my monitor controls and Catalyst Control Panel to get it perfect for me.

It's always possible, a random web search shows others getting the same issue, and others who don't. For me anyway it's totally ignoring ClearType and looks pretty bad, where 2010 correctly renders fonts as expected.

And seriously, that "dark gray" setting is barely worth. It's not dark, it's just slightly less white. This is a good content-focused UI. Microsoft had it and threw it away and that was a horrible mistake.

Exactly -- I use the silver version myself which still draws your eyes to where the content is. Personally this is what I'd prefer out of the default 2013 look instead of the stark white. It's white but still has easily defined separation in the various areas, and the content is still the main focus. (Scaled wayyyyy down.)

sshot1hf.png

Personally Visual Studio 2012 got the "desktop Metro feel" done a lot nicer. Again, drastically scaled down.. you get the general idea. The main focus is white, the rest is a bit darker and everything has easy to see boundaries. Has the Metro "flavor" (minus the menus that YELL at you, turned those off), but it's easier on the eyes.

sshot1me.png

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!