• 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

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!