One of the questions we receive from the community is how secure is NativeScript as a framework compared to the native iOS and Android frameworks. Very often there is not enough knowledge how the native frameworks protect the applications and how the use of JavaScript affects the “security” of the apps.
So let's fix this! I will give you an overview of how the native apps protect the code and data and how NativeScript does this.

Hold tight - this is our biggest release ever. A lot of new features and polish were done in the last 2 months!
With 360+ plugins for NativeScript it is clear that the community is now producing much more code than the core team. This is a huge milestone for every open source project. Thank you everyone for all the contributions and plugin work. Below you will see some major highlights of the core framework that were done by the community.

So your company already have one or more first class native mobile applications and is struggling to keep with all the changes and support they require to keep them in top condition? Maybe you have a larger team of web developers that you will be happy to work on your mobile apps?

This is a very compelling story for everyone that want to faster create first class mobile applications. But sometimes your company already have an existing native applications that they want to extend and do not want to start from scratch. Having two native versions of a mobile app causes just too much problems. You need to have often different people (or even teams!) that implement and support the apps. Syncing the feature set, need to write the app twice and paying to the developers for this is an unneeded overhead these days.

At the end of September we hosted the first NativeScript Developer Day in Boston, MA. I’m sure everyone who attended left with a lot of positive vibes and enthusiasm about what can be done with NativeScript.
For those of you who could not manage to come, we hope to see you next time!

With the recent Angular 2 public release the write once, run everywhere is no longer a myth or something that we should try to avoid due to all the complications that were involved previously.
Now we have a framework that does this for us. When you combine Angular 2 with NativeScript you have a complete story that allows you to share code that runs NATIVELY on the target platforms - web and mobile. Support for desktop is planned for NativeScript as well.

Just in time for the NativeScript Developer Day event we are glad to announce the immediate availability of our 2.3 release. Get the bits here!
360+ plugins, 8k+ GitHub stars, 20k+ followers on twitter, 250,000+ npm downloads, loved by the Angular community (discussion happening right now to rename NativeScript to Angular Native :)), iOS10, FlexBox, Android 7, WebStom, VS Code, TypeScript Security, LiveEdit - this is what NativeScript 2.3 is.

Knowing the community and its needs is very important for every product. There is tons of feedback on Github and on StackOverflow, we talk directly with many of you, but we can’t reach out to everyone (and this is a good problem to have :)).
Please help us and the community experts serve you better by filling out the survey.

It is time to celebrate! The long awaited official release of Angular 2 is now live! At a special event today Brad Green announced the immediate availability of the Angular 2 bits.
NativeScript team is also pleased to announce our compatible NativeScript SDK integrated with the official Angular 2 bits today!

I’m extremely excited to announce an initiative that we were working for several releases now - NativeScript Code Samples!
To make you more productive and to get onboard faster we are releasing 60+ code samples, entirely according to the native UX guidelines, documented, tested and most important entirely open source and contribution friendly!

It is the middle of the summer here at the NativeScript headquarters, but this isn’t an excuse for us not to deliver another quality and on-time release. Please welcome NativeScript 2.2; go get the code and read about all the new things we managed to release in the last month.not

NativeScript 2.1 is now live! Quick links - upgrade now or read the full release notes (total 118 GitHub issues were closed).
If I have to mention just two highlights in this release these will be 1) performance improvements in Android (both load time and runtime performance) and 2) much faster and stable LiveSync (HotReload) functionality as part of your development process.

If you missed the recording our launch webinar that we did yesterday with John Papa, you will be glad to know that the webinar is recorded and available in YouTube today in the NativeScript video channel.

Expectedly there is a ton of excitement these days around the launch of the Angular 2 Release Candidate at ng-conf. With the new Angular architecture you can reuse skills and code between your web and native app

Almost 2 years ago it was my privilege to announce the first public release of NativeScript. Back then my team and I promised a lot of things for the future. Well, the future is now, and when I look back I’m extremely happy to see that we delivered on all of the things we promised in that very beginning, plus we added some more.

It feels like yesterday when we released 1.6 release, but 1.7 is now here and available for immediate download.ere are the major highlights:
Full integration with VS Code editor and debugging for iOS/Android on Mac and Windows.
First preview of the Windows Runtime for NativeScript
Angular 2 SDK - Alpha release
we

The latest release delivers some huge improvements across the framework in these areas - Performance, UI, Debugging/Hot Reload, Angular 2.0, Plugins.
Before taking a closer look at everything we are shipping today, we have an exciting news to share - we just opened a public NativeScript Slack channel! To join the discussions - join the NativeScript Slack channel.

With the latest release of NativeScript you can use the huge amount of icon fonts available on the web inside your native mobile application. This works cross-platform, for both iOS and Android and is as simple as placing the font in the “app/fonts” folder and declaring the icon you want to use in the UI. The NativeScript framework is doing its magic behind the scenes so you don’t need to worry on which OS you run. This is just one those things that make your life easier and is helping you to reuse your existing skills/resources. (using CSS, native libraries, JavaScript code and AngularJS skills are the other things that we make available in NativeScript).
So why is this a big deal and why it is a best practice to use a font instead of an image file to display an icon?