The NativeScript blog is your source for timely and interesting news about NativeScript. If you would like to guest post on our blog, please let us know.
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.
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.
A new component joins the Telerik UI for NativeScript party: welcome RadListView and its powerful set of features directly coming from the native Telerik UI for iOS and Telerik UI for Android counterparts.
NativeScript 1.4 is here. Please read the upgrade instructions.
What sets this release apart from the previous ones is that it reflects more than ever the way we think about the product. Once we deliver a certain set of functionality, we focus on perfecting the existing framework. You will not see new features baked into the latest version. Instead we polished many functionalities in response to users feedback. This is the result of working with a lot of developers and helping them deliver apps to their clients. Listening and responding to real developer feedback was always a core value for Telerik as a company and I’m sure you will be happy to work with this latest version of NativeScript. NativeScript is now more stable, more polished and battle tested framework. You can use NativeScript 1.4 in your production environment for building applications.
(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!