Windows support (UWP)

[valentinstoychev]

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.

[nemephx]

Not sure if Win10 will support Silverlight dev for mobile, but I'd say focus only on the universal APIs.

[Klors]

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]

+1 i dont have windows...

[karundeepyadav]

• from my side. Looking for windows this support..

[enchev]

You can run now Android applications on Windows Phone 10 including {N} apps: https://twitter.com/ligaz/status/630996030864142336

[RonaldV]

+1 for native Universal Windows app support.

[SunburnedGoose]

+1

[calebeaires]

+1

Focus on Windows Universal APIs

[maury91]

+1

[danicomas]

+1

[pzskyz]

+1

[phulst]

+1

[Tim-Wils]

+1

[rui-cruz]

+1

[kaurag007ph]

+1

[johnmurphy01]

+1

[TryingToImprove]

+1

[DarrinRobertson]

+1

[MarkEwer]

For the consumer market, Android and iOS support is all you really need. But, I work in the corporate market so Windows support is a must. BTW, support for Mac desktop apps in addition to Windows Universal would round this out into the only platform I would need.

[DenisBazhan]

+1

[thuffamatwork]

+1 and (I suspect off topic) support to compile/translate into a true web project.. that would rock.

[sandorfr]

I think this should be a top priority. There are already plenty of xplat frameworks without decent windows support. This would make a huge difference.

[nikolayDemirev]

+1

[burnsting]

With Windows 10 and its new Universal App Platform already running on over 110 million desktops worldwide, I'd say this is a must. Coming holiday season a lot of laptops, 2-in-1's, etc will be sold, and most of them will be running Windows 10. No matter how you look at it, Android dominates mobile (with iOS taking a sizable chunk as well), but Windows dominates the desktop. And I'd love to bring the apps I'm developing to these people sitting behind a computer every day.

I think the Microsoft people have been pretty helpful with Phonegap, and getting every type of developer being able to develop apps for their platform. They're even working on support for Java, Objective C for native apps. So maybe the Telerik people should get in touch with them. I think they'd be happy to help. Just a thought..

[mtringuyen]

nativescript should be available for windows mobile asap :)

[rkyoku]

+1

[sidewinder]

+1

[mike-ense]

@valentinstoychev and all other, maybe following up in this separate issue NativeScript/windows-runtime#5 is preferable.

Will be very excited to learn to know your perspectives on this one - I understood the general problem on how to implement Windows Support above but a lot of additional detail would be great also. I hope we can get Nativescript on Windows soon.

[DanielEgbers]

+1

[touseefbsb]

i come from uwp development background and now I want to adapt to android and ios as well with one codebase, xamarin forms already provide this but they are not as performant, I was hoping nativescript can support this because in coming future uwp development is going to be huge, because Microsoft is gradually moving everything to uwp plaform and with so many number of platforms including xbox, surface, and specially holo lens, windows 10 development will be huge in near future, so uwp support must come with nativescript ASAP

[Serge-SDL]

very interested too!

[ciolt]

+1

[mike-ense]

@valentinstoychev (and @jasssonpet @fealebenpae ), please provide a response to the public question posed in this thiread NativeScript/windows-runtime#5 soon.

I have also discussed that thread with TJ.

Please refer to the thread for details. What's at stake is, knowing if the NS JS binding model will work on the UWP, so that this way the NS users who will want to make UWP solutions in 1-3 years, will know that at least with respect to engineering possibilities, that's a realistic plan. The reason I have been keeping asking you this question for four months now and giving energy to wait for your response, is that I interpreted from your extremely brief public communications that you maybe had a worry that actually the NS JS binding model would not work for UWP/C++ as it does for ObjC/Apple and Java/Android. So please ask your devs to give time to elaborate on this one. Thanks!

[kuashe]

I'm not a member of nativescript / telerik but I'm pretty sure that @NathanaelA statement is exact.

Nativescript Survey was released and it's not showing a glimpse of support for Windows or Mac OS .

Also Nativescript is not Node.JS . Meaning , even if Nativescript is ported to Windows / Mac you would not have acces to Node.JS API unless giant investment is be done by the community. This would make the platform very limited in my opinion .

[geminiyellow]

I cannot open the vote page. so, I have to vote here 👍

[rkyoku]

Well, Windows Phone is kinda dead now, is it not? Do we really still need to support it? I personally don't think so... I'm withdrawing my upvote from this feature. Le mar. 22 mai 2018 à 11:50, Shimmy <notifications@github.com> a écrit :

…

I'd switch to NativeScript if it had Windows support. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#254 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AApUID1vn7ueDJZLKw8ZWlOU0qOOe7EVks5t0996gaJpZM4Ey41k> .

[weitzhandler]

+1
I'd switch to NativeScript if it offered UWP support.

@rkyoku

Windows Phone is kinda dead now

It is, but UWP targets Windows 10+, desktop, tablets, notes, or phones.

[rkyoku]

Thanks for the precision! I admit I wasn't aware "windows" meant anything more than windows phone. Thanks again! Le mar. 22 mai 2018 à 12:17, Shimmy <notifications@github.com> a écrit :

…

+1 I'd switch to NativeScript if it offered Windows support. @rkyoku <https://github.com/rkyoku> Windows Phone is kinda dead now It is, but UWP targets Windows 10+, desktop, tablets, notes, or phones. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#254 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AApUIJl2eaFYsGmt_fQ6DPW_jkhP6d-yks5t0-W6gaJpZM4Ey41k> .

[touseefbsb]

@rkyoku yes windows phone is dead, but it is definitely coming back. nt sure how soon but it will be back better than ever running directly newer versions of uwp. and also uwp consists of many devices not just windows phone.

[jamlfy]

Well windows phone is dead, this issue is close?

[weitzhandler]

@alejonext no. the issue is not about windows phone, it's about UWP which is live and kicking.

[rkyoku]

Maybe the ticket title should be updated then, to avoid any unnecessary confusion? Le ven. 1 juin 2018 à 02:45, Shimmy <notifications@github.com> a écrit :

…

@alejonext <https://github.com/alejonext> no. the issue is not about windows phone, it's about UWP which is live and kicking. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#254 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AApUIDW2sRVZHoEx0BAfRAfgSzEdtFX8ks5t4I62gaJpZM4Ey41k> .

[touseefbsb]

the title says windows support, which is correct, it doesnt say windows phone support, how is it confusing?

[rkyoku]

Apparently a few people find it confusing, but if you want to fight against this small title update for an obscure reason, I will leave you fight alone. I just wanted to make things clearer. Le ven. 1 juin 2018 à 11:10, Touseef <notifications@github.com> a écrit :

…

the title says windows support, which is correct, it doesnt say windows phone support, how is it confusing? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#254 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AApUIHhHKLD723ffRjiDl0ubzz5S1XMUks5t4QTvgaJpZM4Ey41k> .

[touseefbsb]

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]

and vote for this feature in our ideas portal.

Your "ideas portal" suck.

[manojdcoder]

@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]

@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]

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

[steskalja]

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]

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