Nativescript 3.0: Faster Apps, Built With Javascript [Webinar]

DZone 's Guide to

Nativescript 3.0: Faster Apps, Built With Javascript [Webinar]

This Webinar gives you the scoop on NativeScript 3.0 and all the improvements, added support, plugins, and a special announcement.

· Mobile Zone ·
Free Resource

A big thanks to everyone who attended May's webinar on NativeScript 3.0! We are always happy to see such an engaged community around NativeScript. It truly is you who have helped make this open source project into what it is today.

The entire NativeScript Developer Relations team (Jen Looper, TJ VanToll, Sebastian Witalec, and Rob Lauer) put on quite a show, giving you the inside scoop on everything 3.0:

Be sure to read the original NativeScript 3.0 release post for even more information.


If you missed the webinar, no sweat- it's up on YouTube for you to view:


Once again we leveraged Twitter to handle all of our Q&A for the event. You can actually go back in time (well, not literally) and check out all of the questions and answers by looking up the #askNativeScript hashtag.

One of my favorite questions was: 

Image title

And the answer? NativeScript was built in a manner to make it extremely flexible and not be tied to a specific framework (hence the ability to use Angular today, or not). It just so happens that we have a community-run initiative to add Vue.js support! Look for more news on this subject in the coming weeks and months.

What's Next?

If you're new to NativeScript, your first stop should definitely be to try one of our two end-to-end getting started tutorials:

Also, keep an eye on the public roadmap, as we will be continually updating it to show you what is in store for NativeScript in 2017.

Finally, npm install -g nativescript, update your apps and enjoy the latest bits!

javascript ,mobile ,mobile app development ,mobile app performance ,nativescript

Published at DZone with permission of Rob Lauer , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}