What's new and coming for Windows UI: XAML and composition

Play What's new and coming for Windows UI: XAML and composition

The Discussion

  • User profile image

    One of the speakers was very disturbing to listen to, stutters all the time "uh uh uh... brings you .. uh uh uh"

  • User profile image

    I disagree. Perfectly listenable.

  • User profile image

    I agree with Greg.  Perfectly listenable.

  • User profile image
    Sean Ledbetter Pulagatha

    Have a set of rules, don't just let people make whatever they want.

    Look at Flat Bookmarks for Firefox for a well done tree layout.

    * First and foremost, separate the menu buttons from the action buttons. The buttons being intermingled is confusing to the user.
    * A one pixel border is necessary to differentiate the work area of one app from another.
    * The sidebar should be on the left side only as the user is "reading" the app.
    * Oversized elements and empty space are a poor design choice.
    * Menu highlights should be noticeable, while background elements should blend. (The highlighted color is enough, giving the icon an extra bottom bar or symbol is unnecessary in most cases.)
    * For dark mode, use a dark grey and not solid black. (and make it system wide, there doesn't need to be several different apps using several different versions of dark grey.)
    * Be minimal with animations.

  • User profile image

    MICROSOFT please !!!!

    do more and more videos like this , this is the one thing end user care about , UX !!!

  • User profile image

    *Only thing :p

  • User profile image

    First off, this is really nice stuff and these are definite improvements! But, something needs to be said here.

    To me it seems the UI modifications introduced originally as part of Windows 10 were a big step in the wrong direction. The power of perceived affordances took a backseat to 'flat design', effectively stripping many UI elements of their clarity in how they can be used (where to click, can they be clicked, what type of element it is).

    Surely, 'reveal' and the importance of 'light' in this update address these problems, while simultaneously looking more pleasing to the eye, but the problem would not have been there in the first place if 'flat design' wasn't introduced to the extent that it was in Windows 10 (thus a bit of a straw man argument). The calculator application shown in this presentation is a great example of this.

    While it is awesome to have additional development tools available to create more pleasing 'on hover' effects, conceptually this is nothing new. From a design perspective, it would still not make sense to require a user to hover over important UI elements to only then be able to interpret what they are. Thus, 'reveal' should likely be used sparingly, only for secondary or tertiary user interface controls.

    Funny enough, as part of this presentation, Ashish demonstrates a perfect example of the downside of stripping UI of too many perceived affordances, as he spends 32 seconds (19:34 – 20:07) on resizing a window to its desired size, while narrating it as "Sorry. If this machine cooperates." and Tim helpfully instructs him "Anchoring it too high ...". I previously blogged about these missing affordances in the window manager of Windows 10 (https://whathecode.wordpress.com/2015/10/15/missing-affordances-in-windows-10/
    ) and found it quite ironic to see the consequences of this at play here.

    Bottom line: great new stuff, but I hope it won't get overused (afraid it will).

Add Your 2 Cents