My observation now after a couple of years of UWP development for apps that have to be published on Microsoft Store is:
- Use pure UWP when it is OK to run your app in a sandbox and you don't need full access to the file system and/or want to run long lasting background tasks without a UI (i.e. time triggered tasks, network listening tasks, etc.).
- Use desktop bridge with a WPF process as entry point and XAML island with UWP controls for the UI when full access to the file system is needed and when you want to run any type of process/task in the background.
My conclusion today then is: Any serious project requires desktop bridge with WPF. When you go the UWP way somewhere along the road you will probably hit a wall.