Why not try, though? First and foremost, I think it's a good thing that designers are getting work. I also think huge "for fun" webapps are in a particularly advantageous place when it comes to pushing the boundaries of design, mostly because they have people on hand who can do it and who probably want to do it. Next, it's really a low risk preposition.
Maybe Office 365 needs to be conservative with fonts. Twitter can push boundaries, though. I wish they'd push boundaries more, ala Bertone or Memphis Group, but I guess the risks are larger the more you push the boundaries.
> "Maybe Office 365 needs to be conservative with fonts. Twitter can push boundaries, though."
What's the difference between Office and Twitter here? Both are apps that should just get out of the way of the content.
Most software should just have native UI that follows the platform guidelines. Unfortunately software companies hire graphic designers who know nothing about interaction design, and generalist programmers who want to do one-size-fits-all UIs. And that's how you get unreadable fonts in slow Electron apps.
Why not try? Because the cognitive dissonance when people's eyes and brains run into a large variety web-based and app-based screen fonts. Web based font performance is still terrible. So.. because: the brain doesn't like it.
Different presentation fonts in web pages, desktops, etc. can start to have the experiential impact of (gui) skins, or non-standard dotfiles.
Please note the things I'm leaving out of this... print, books, static things, etc.
Maybe Office 365 needs to be conservative with fonts. Twitter can push boundaries, though. I wish they'd push boundaries more, ala Bertone or Memphis Group, but I guess the risks are larger the more you push the boundaries.