Repository navigation
Windows support (UWP) #254
Description
This is a work in progress at the moment, but having your feedback and comments can increase its priority. We are planning Windows10+ support at the moment.
At a high level the tasks are as:
1.7
- Release a PREVIEW version of the runtime for Windows Universal - https://github.com/NativeScript/windows-runtime
Not planned
- Implement the cross-platform layer on top of the runtimes to support the Windows UI.
- Implement support in CLI
If you are interested in this feature please add comments below with specific requirements and vote for this feature in our ideas portal.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Activity
[-]Windows WinRT mobile support[/-][+]Windows support[/+]nemephx commentedon Jun 3, 2015
Not sure if Win10 will support Silverlight dev for mobile, but I'd say focus only on the universal APIs.
Klors commentedon Jun 11, 2015
This would be very useful as it would allow us to attempt to use NativeScript (with our existing web development knowledge) as our corporate cross platform mobile development solution.
+1
jamlfy commentedon Jun 17, 2015
+1 i dont have windows...
karundeepyadav commentedon Aug 5, 2015
enchev commentedon Aug 11, 2015
You can run now Android applications on Windows Phone 10 including {N} apps: https://twitter.com/ligaz/status/630996030864142336
RonaldV commentedon Aug 12, 2015
+1 for native Universal Windows app support.
SunburnedGoose commentedon Aug 24, 2015
+1
calebeaires commentedon Aug 28, 2015
+1
Focus on Windows Universal APIs
maury91 commentedon Sep 4, 2015
+1
danicomas commentedon Sep 8, 2015
+1
pzskyz commentedon Sep 9, 2015
+1
phulst commentedon Sep 15, 2015
+1
Tim-Wils commentedon Sep 16, 2015
+1
118 remaining items
jamlfy commentedon May 31, 2018
Well windows phone is dead, this issue is close?
weitzhandler commentedon Jun 1, 2018
@Alejonext no. the issue is not about windows phone, it's about UWP which is live and kicking.
rkyoku commentedon Jun 1, 2018
touseefbsb commentedon Jun 1, 2018
the title says windows support, which is correct, it doesnt say windows phone support, how is it confusing?
rkyoku commentedon Jun 1, 2018
touseefbsb commentedon Jun 1, 2018
haha no no why would I fight? change the title by all means sir :) I was just asking why it can be confusing, I have nothing against title change.
alensiljak commentedon Apr 3, 2019
Your "ideas portal" suck.
manojdcoder commentedon Apr 3, 2019
@mistery The exact description of this issue was written in 2015 on which period Ideas Portal was active. Later {N} had released a blog post confirming migrating to Github reactions from Ideas Portal.
Now you vote by reacting with a Thumbs Up in the description of issue.
alensiljak commentedon Apr 3, 2019
@manojdcoder, thanks a lot for that explanation for me and numerous others who did not read NativeScript blog back in 2017. This Ideas Portal still seems active as the link takes us there but then it responds with Page Not Found message, which is confusing.
This information is fairly useful so I would suggest someone copy/pastes it to the issue description. That would remove redundant instruction to visit the Idea Portal and hopefully also assist all those who would otherwise add "+1" in the comments.
shirakaba commentedon Apr 12, 2019
My tentative idea for reviving Windows support at relatively low development cost: adapt the NativeScript iOS runtime to Microsoft's iOS Bridge ("Objective-C for Windows"):
NativeScript/ios-jsc#1126
[-]Windows support[/-][+]Windows Phone support[/+][-]Windows Phone support[/-][+]Windows support (UWP)[/+]steskalja commentedon Jul 19, 2019
Now that Windows 10 has more than 1 Billion devices. Will you be looking at building support for a Windows runtime. Maybe you could take a look at the work Microsoft is doing with React Native, since it is open sourced: https://github.com/Microsoft/react-native-windows
redradist commentedon Feb 5, 2021
This feature right now is not no optional ... it is almost required to be competitive with other implementations like Flutter, Blazor Mobile Bindings (allow not only use platform API but also use hybrid approach and mix code) and so on