It is unfortunate, but I think Dr. McCoy from Star Trek: The Original Series said it best: ‘Windows 10 Mobile is dead, Jim“…. and just to pile on with one more.
Buried underneath the red shirt like death of Windows 10 Mobile lies the amazing Universal Windows Platform (UWP).
The developer capabilities of the Universal Windows Platform have been documented in many a location.
UWP provides:
- Full developer parity at the API and framework level across all flavors of Windows 10, Xbox One, HoloLens, and Windows 10 Mobile devices.
- A simplified install model via APPX bundles.
- A per-app separation of registry and file systems.
- XAML controls ‘just work’ across all Windows 10 / UWP devices.
- Targeting the UWP API set ensures that your app works across Windows 10 / UWP devices.
In my experience, there is nothing weirder than seeing your Windows 10 / UWP app just work on an Xbox One, in a virtual projected rectangle via a HoloLens, and via mouse and keyboard on a standard Windows 10 PC.

HATEOAS stands for “Hypermedia as the Engine of Application State” and it is one of the possible constraints that you can place on a REST compliant API. Essentially what it means is that your API is as navigable as a normal website, with hyperlinks leading to other resources. The focus of this blog is not HATEOAS itself – instead focusing on an implementation of it our team recently used for our project’s API.