Blog

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

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:

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.

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

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.

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.

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?

The whole world goes mobile, so are the software trends. But what’s the reason to create a mobile app after all? Well, surely, when things get serious, after the “it’s just for tests and fun” phase, it’s all about the money. You can create an app for the employees of your company or for the employees of somebody else (B2E, B2B). In this case your company benefits directly from the services you provide to its employees, or you take a commission for the app you create. But if your customers are the end-users (B2C) or if you create an app for a business customer (B2B) that will sell it to the masses, then you should surely be aware of the different app monetization methods where two of the main ones are in-app purchases and mobile ads. Today, we will talk about mobile ads and how you can enable them in your NativeScript application using the Google AdMob service and SDKs. This article will focus on iOS and in the next part we will cover the Android platform.

1.5 is a special release for NativeScript as it marks a major milestone - providing NativeScript developers with the tools to make them a lot more productive. There are several major and important features added in this release that will skyrocket your developer experience.

If you weren’t able to join us for our 1.4 release webinar, the video is now available on YouTube. The webinar includes demos of the latest features of our 1.3 and 1.4 releases, including animations, UI for NativeScript updates, Angular 2.0 support, and a whole lot more.