May 21, 2019

BUILD 2015 Summary: Introducing the Windows 10 App Model




//BUILD/2015 wrapped up last Friday, during the three day conference, a lot of news came out, but the important questions, like how to develop for Universal Window Apps, don’t find answer easily in the media. They don’t have time for these. I am afraid most developers can’t find time either. If you do, I bet you don’t want to watch those long, boring videos from BUILD. I am not sure if people are aware why those technical speeches are boring. I tell you why: 1. Most of technical speakers are not good speakers. If you don’t believe me, pick some of the links from here, see if I am right. 2. Listening to technical speeches is like your brain running a marathon, that’s very truthful, you just don’t realize it. Think about it, the speaker had run the content many times in his brain, so he talks at ease. But the listeners has to digest a very challenging topic very fast to catch up. I found this truth: it takes each listener 10 times brain energy than the speaker to catch up what he is saying.

Any way, I will do the listening for you, after that I write down some key points from the video. For some important ones, you’d better watch for yourself, for some, you can skip the video, just read my notes. I will put he notes after the video.

This is the first one, generic things about Universal Windows Platform App Model. Mostly concepts. As always, forgive my typing errors.


>> Project Centennial: Converting Classic Windows apps to run on Universal Windows Platform
Interesting topic. I haven’t heard of this. So, what is an classic app?

Classic Windows App: Every program that is not Windows 10 Universal App, or previous Windows and Windows Phone app. They include Win32 applications, .Net applications, WPF or Windows Form applications, etc.
A classic Windows app is wrapped into AppX for deployment, just like UWP apps.
1. AppX is the deployment model
2. Better way to install/uninstall/update
3. Runtime isolation registry/disk access
4. Enforce App Model Policy
5. Integrate into new app model
Three things make this happen:
a. Registry keys are stored locally to the app folder.
b. Take advantage of some UWP feature, like Cortana. (How?)
c. Windows Desktop App Model Policy: Allow Full API access and existing Desktop app lifecycle. Not allow access of drivers, NT services. No admin elevation, shellExtension
AppX: supports 150G
>> Developer Unlock: just an setting options from control panel.
Limit: 20 apps, Desktop: no limit
Debug can be done on WIFI.
(not working yet)
>> Install apps on removable storage
encrypted, options in manifest
>> App Resume Policy: (30:34)
All UWP apps will resume by default
All 8.1 phone apps and 8.0/8.1 desktop apps also resume
WP7.x and 8.0 apps do not resume (he said reason is for compatibility, those apps assume new instance. I think he is wrong, but…)
>> App to App/App Service
Cortana/People app for example
* I don’t real understand this yet. Is this like background tasks, like camera task. Looks like you create and publish App Services in your app, and other apps can call it.
>> Adaptive Tile Template – there are many templates for different need. Nice.

>> Utilize notification and action center

Not much details.


HoloLens FOV – What’s Next

HoloLens – The Matter of FOV

Register for: A Developer’s Guide to Windows 10