Thanks for reaching out, and awesome that you’re liking NativeScript . Straight to the point though—we’re not actively working on UWP support because 1) it’s a ton of work to add a new platform and commit to supporting that platform indefinitely, and 2) we’re not seeing nearly enough demand from our community to justify taking on that work.
That doesn’t mean that UWP support in NativeScript will never happen, but it’s not coming in the short term because we’re just not seeing the demand. That can always change though. I’d encourage you to add your use case to the GitHub issue open for adding UWP support in NativeScript: https://github.com/NativeScript/NativeScript/issues/254. Yes, the issue is somewhat ancient, but we really do pay attention to well-thought-out comments during roadmap discussions.
I’ll note two other things. First, our initial work on making a Windows runtime is completely open source and available on GitHub: https://github.com/NativeScript/windows-runtime. We’d love to have community help to make the new runtime a reality.
Second, one option you have is to build your iOS and Android apps with NativeScript and Angular, and to use our code sharing approaches (see https://www.nativescript.org/blog/code-sharing-between-web-and-mobile-with-angular-and-nativescript) to share your Angular code with other apps. You could take that approach to share Angular code between your NativeScript apps and your UWP apps if you use something like Electron. This approach isn’t ideal, as you’d probably prefer to build a completely native UWP app, but it’s something to consider if you’re open to using Electron.
Anyways, hopefully you found some of this helpful. If you have any other questions feel free to follow up.