This impression (which I don't believe is unique) only seems to have come about recently with Panay.Įvery change that's been released from Panay's era so far has been refreshing, different and improved.
Like they tried to give 8 its Vista->7 moment but it backfired and only served to highlight their design flaws and poor tastes.Ĭurrently though, it's like they're Quantum Leaping the Windows product undoing obvious wrongs throughout its timeline. And that didn't really change too much with the Windows 10 era which felt more like a mulligan to try to give the Metro idea another go. This guy was using a Mac at home and he was on the Microsoft user experience team. I don't get the impression anyone at Microsoft actually used Windows 8 or else they'd be driven mad by all the bad designs and inconsistencies. And finally to the question of "do you believe anyone at Microsoft actually preferred using the platform after Windows 7?". Next, "What changes is Microsoft making to their user experience now that can point out their inadequate deficiencies in Metro and UWP design?". They had that in 2009 and they got rid of it for the same type of reasons as the startup sound. To answer your question, it may seem illogical or even silly to extrapolate simply the example of this startup sound removal, but it's a good easy-to-understand example to introduce their pattern of failures which should immediately be followed up with questions like "how much money is Microsoft pouring into Windows with Sun Valley to support rounded corners and a consistent UI?".
On a rejoined session where it's coming out of sleep or hibernation, don't. That was a genuine problem but the concept seems like it would be obviously better handled by simply referencing the state in which the login session has opened with regard to use cases in mobile devices: On a new session start from cold boot or fresh login where someone specifically logged out, play the sound.
0 kommentar(er)
