Quick blog post for you all today. As you may know if you’re on the fast ring Insider build of Windows 10 Mobile there is an issue when trying to deploy UWP apps out to a device from within Visual Studio. Developers are met with the error: DEP6100 and DEP6200 both relating to a failure while Bootstrapping to the device.
Our Windows team at UI Centric has hit this issue with multiple devices against several different dev machines so we know it is probably hitting many other Windows 10 developers. With build 10581 of Windows 10 mobile it appears Microsoft have fixed the underlying issue, however if your tools are in a bad state – or if you try to deploy to a phone that still has this issue and hit it once – you made need to take steps to get back to a working setup.
We’ve used the following steps on several PCs and Laptops so at this point I’m expecting they will work if followed exactly, that said, your mileage may vary.
It is increasingly looking like the folks at Microsoft have torn up the UX metaphor cookbook that was in place in Windows 8 and Windows Phone 8. Windows 10 already appears to have moved away from landscape scrolling to the traditional portrait. We also know that the charms bar is already dead in the latest builds requiring search and share prompts to be brought into an app’s UI. The other potentially polarising change to acknowledge, discuss, and start getting ready for is the apparent end of the app bar as we know it.
Possibly the biggest change for modern Windows developers that comes with the Windows 10 system is that we no longer need to support just a few aspect ratios and scales, we have to support almost any possible aspect ratio at any scale. This is thanks to the ability to have Windows Store apps run in their very own windows in the desktop, which makes absolute sense for keyboard and mouse users.
We could argue that the snap view possibilities in Windows 8.1 already started this layout, but the difference with snap is we had a relatively guaranteed minimum size on the vertical plane, and could focus on layouts which showed more or less on the horizontal plane. This approach was closer to adaptive design, and had the benefit of always having a large vertical plane available (minimum of 768 pixels).
Now that users are able to resize and change the window across both axis, we have to start considering how we as developers should support this concept. This of course isn’t a new problem, just look at how web design has changed over the last few years, and even before then we have traditional Windows Forms apps which worked in the same way. That said it is at least partially new for XAML in Windows Store apps.
In this piece I will explore how we can take inspiration from Responsive web design and apply those lessons to current Windows Store apps so that they are ready for use on the desktop in Windows 10.