Microsoft-ui-xaml: Discussion: So, Windows 10 X... Time to talk about the dev and insider story?

Created on 2 Oct 2019  路  7Comments  路  Source: microsoft/microsoft-ui-xaml

Discussion: Windows 10 X + WinUI

Windows 10 X has been demoed and outed. Can work be ramped up on Win UI and supporting this new OS and UX. Dev docs, SDKs, Insider builds, Demos, Samples, etc.

What kinds of devices this new shell will run on, and what new patterns and workflows are needed for a world without File Explorer, Taskbar Trays, Live Tiles, etc.

image

Related Links

Introducing Windows 10X: enabling dual-screen PCs in 2020

discussion

Most helpful comment

We will be rolling out more detailed information about developing for Windows 10X and dual screen devices over the coming months, eventually including builds, sdks, docs, samples, etc.

Astute observers of the Introducing Surface Neo video will have noticed plenty of use of Fluent Design System and WinUI-based experiences, so it's certainly an exciting future for everyone in this community! :)

If you want to take action now to prepare for Windows 10X while you await more details, I'd say that following our Fluent Design Guidelines for Windows and other best practices for Windows 10 app development today - including things like being responsive to window sizes, working well with all inputs including touch and pen, and making use of standard controls where available - are all things that make sense to do that will accrue to help your app shine not only on Windows 10 but also on Windows 10X.

I'm sure many of us (including @chigy) would be happy to hear any early input and thoughts you'd like to share in the open about how you'd imagine updating your apps for dual screen devices and/or things you'd imagine wanting of the platform to help support you in doing so. We'll have more to share back ourselves in the future.

All 7 comments

for a world without File Explorer

There is a File Explorer icon in the image you linked.

No indication yet if the system tray will still be around or not.

Otherwise, the majority of the work appears to be in the shell which will handle all the window management (positioning/snapping/expanding).

The "Wonder Bar" is the main thing that needs new interaction APIs. Otherwise I presume we'll be using the new AppWindow API to create apps with interdependent, non-spanned windows.

I would guess there would be a modern and simplified File Explorer built with XAML for this new device/SKU - At least I would hope so, as this is a rethink of the OS UX.

Hey folks! There's a lot of excitement (and fun speculation) on these new devices and Windows 10X; I think we'll soon have more we can share on the WinUI / development implications for these devices.

Looking forward to hearing what is planned for developers around these new devices / UI experiences. I'm especially curious to see how we are expected to handle splitting the same app in two windows across screens. That's potentially going to change a lot in how apps are designed and I'm actually hoping it's an opt-in feature that apps can disable.

I just keep thinking of the Nintendo DS consoles.

We will be rolling out more detailed information about developing for Windows 10X and dual screen devices over the coming months, eventually including builds, sdks, docs, samples, etc.

Astute observers of the Introducing Surface Neo video will have noticed plenty of use of Fluent Design System and WinUI-based experiences, so it's certainly an exciting future for everyone in this community! :)

If you want to take action now to prepare for Windows 10X while you await more details, I'd say that following our Fluent Design Guidelines for Windows and other best practices for Windows 10 app development today - including things like being responsive to window sizes, working well with all inputs including touch and pen, and making use of standard controls where available - are all things that make sense to do that will accrue to help your app shine not only on Windows 10 but also on Windows 10X.

I'm sure many of us (including @chigy) would be happy to hear any early input and thoughts you'd like to share in the open about how you'd imagine updating your apps for dual screen devices and/or things you'd imagine wanting of the platform to help support you in doing so. We'll have more to share back ourselves in the future.

Will NavigationView be expanded to allow for two Frames which can be oriented side-to-side or top-and-bottom by the developer (and swap as the device is rotated) It would be good for a NavigationView to treat both displays individually while also being able to apply a menu or command bar(s) across the top as a single app spanning both displays.

Was this page helpful?
0 / 5 - 0 ratings