The NativeScript blog is your source for timely and interesting news about NativeScript.
If you would like to guest post on our blog, please tweet us @NativeScript.

  • Why Become NativeScript's Tech Writer?

    Here is an opinionated top 10 of reasons why you should seriously consider becoming NativeScript's tech writer (and the member of a very elite group of technical writers at Telerik).

  • NativeScript in 2015: Top 6 Devs and {N} Groundswell

    2015 was big year for getting JavaScript on mobile devices. Nowadays, JavaScript developers can build highly performant native apps, in part thanks to NativeScript. With this post I wanted to say thanks to some top contributors in our community and to show off some of the NativeScript momentum we are taking into 2016.

  • Using Babel in NativeScript Apps

    The NativeScript 1.5 release introduced first-class support for languages which transpile to JavaScript. In plain English, if your language of choice generates JavaScript, it can now be used to create NativeScript apps. The NativeScript CLI has integrated support for TypeScript, Babel, and CoffeeScript (here’s the full list of languages we support), but if you want to use another language, just create a plugin following the template of the existing Babel one. The upcoming ES7 language edition has the async/await feature which makes the UI and networking code a breeze to write and support. I was very eager to experiment with async code in a NativeScript app, and decided to try it by implementing a simple app. I decided to mirror the cuteness sample. But my project was going for something more awesome, and that's why it follows /r/hardcoreaww sub-reddit instead.

  • Ignite your App Development with NativeScript and Firebase

    Learn how to connect a Firebase backend to your NativeScript app.

  • Telerik UI for NativeScript Preview 3 Release

    Telerik UI for NativeScript has just been updated introducing several major features in the Chart and ListView components, as well as numerous fixes and improvements. Here's a short list of what's inside the latest version of the plugin:

  • Monetize your NativeScript apps with AdMob (part 2 - Android)

    This is the second part of the Monetize your NativeScript apps with AdMob blog. In part one I discussed how you can easily access and use the native API of a native framework in JavaScript, taking the AdMob library for iOS as an example. To do that, you only needed the existing AdMob documentation in combination with a few simple rules to translate the Objective-C API calls to JavaScript. The popular mobile platforms, however, are two - iOS and Android. So, it would be fair if I cover Android as well. Moreover, further in this article as things get a more interesting and we are close to having a cross-platform AdMob usage, I will show you what’s the recommended way of separating and isolating the native API calls in a NativeScript project. So, let’s begin.

  • A QuickStart to Building Mobile Apps with NativeScript

    Get a jump start on your NativeScript iOS and Android mobile application development in a new quickstart course.

  • Using V8 code caching to minimize app load time on Android

    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.

  • Which versions of Node.js should you use today

    As we know, NativeScript CLI is a Node.js application. This brings the questions like "which versions of Node.js can and should I use" or "how long particular Node.js version is supported." To answer these questions, it is useful to know the life cycle of Node.js. Please, take a minute to check the project wiki which explains it in a single graphic. With it in mind, the NativeScript team decided to support the LTS branches and, if possible, the "current stable" branch.

  • Mobile app Best Practices - use Font instead of Image to show an icon

    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?

Sponsored by progress-logo-min
NativeScript is licensed under the Apache 2.0 license
© 2019 Progress Software Corporation. All Rights Reserved. Privacy Center