Read all about the latest NativeScript 3.1 release, which introduces new features like the Chrome DevTools Elements tab, Android snapshot builds, and more.
NativeScript 3.0 is now available! Read all about the new release and attend our webinar on May 17th to learn about the highlights from our panel of experts.
The NativeScript 3.0 release candidate is available for use today!
Georgi Atanasov gives us a sneak preview of NativeScript 3.0, due out in mid-April.
Another feature-packed release of NativeScript is available for download! Version 2.5 brings a variety of fixes and enhancements including support for WebPack 2.0, debugging via Chrome DevTools, and a variety of CLI improvements.
Every now and then we receive feedback on the performance and APK size of some NativeScript Android application, especially built with Angular 2. In this post I will try to elaborate a bit more on the technical challenges behind the Android Runtime, Core Modules and Angular 2 integration projects as well as to share some easy steps that would boost the performance several times.
Every now and then the question about the size of a NativeScript application package pops up, especially for the Android platform. The purpose of this post is to provide an in-depth and thorough answer to this question and why, by default, the Android application package (*.APK) adds some ~12MBs on top of a blank, purely native Android application.
There are three reasons for the NativeScript framework to exists - native UX, performance and a cleaner and easier programming model for cross-platform mobile applications.
A common user experience for an application is to display a loading (splash) screen while it is initializing. Building our Telerik Next conference application, we wanted to display such a screen. While trivial for iOS, it turned there is no built-in mechanism in Android for achieving this functionality.
(expect a newsletter every 4-8 weeks)
Ready to try NativeScript? Build your first cross-platform mobile app with our free and open source framework.
If you see an area for improvement or have an idea for a new feature, we'd love to have your help!