Recent Articles

  • Get text completion with AutoCompleteTextView (Beta)

    In the era of mobile devices, most of the user interactions with the device happen without additional hardware keyboards involved. This is comfortable for mobility purposes. However, the software keyboard is not always your best typing friend. To address the loss of tactile keyboards, most software keyboards offer some means for predictive completion. Often, the application developer would like the application user to choose from a defined set of choices. For example, the choices may be a list of origin airports serviced by an airplane company, or possibly a list of your friends in a social app context. In this case, the AutoCompleteTextView for NativeScript will be your best friend. Let’s dive in a little deeper into the useful features that the control provides.

  • Angular 2 support and new features for RadDataForm

    With the latest and greatest release of nativescript-telerik-ui/pro the UI and feature rich components continue to grow. With 1.5.0 the RadDataForm is receiving new features and more examples that will ease its usage in common scenarios. Last, but not least it's getting Angular 2 support. Let's get straight to the features and enhancements.

  • DataForm is now official

    About a month ago, we released a Beta of DataForm for NativeScript. After adding some more features, and addressing the issues we found, we are happy to announce the official DataForm for NativeScript, which is a part of UI for NativeScript Pro

  • Introducing DataForm (Beta) for NativeScript

    While each fiil-in form on mobile is different, the overall concept of presenting properties according to a specific data type, ensuring validation rules are respected, and saving the information follows a consistent and regular form. Wouldn’t you like to have an easy to use component that provides the end-user with the ability to enter all this data in a user-friendly and convenient way? Introducing the DataForm for NativeScript!

  • 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.

  • Monetize your NativeScript apps with AdMob (part 1 - iOS)

    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.

  • Using CocoaPods is a piece of cake with NativeScript 1.3.0

    NativeScript 1.3.0 is already here packed and stacked with a bunch of improvements. One of these improvements is the ease of use of CocoaPods. For those of you who don’t know CocoaPods, ​it is the dependency manager for Swift and Objective-C project. It allows you to easily take an open source GitHub repo and add a reference to the library that it produces.

    With NativeScript 1.3.0, you can easily take a pod and use it for the iOS part of your NativeScript projects working only with the NativeScript CLI, without touching Xcode. What it more, a pod can be easily turned into a NativeScript npm plugin.

  • Making a Today widget in iOS with NativeScript and UI for NativeScript

    Since iOS 8, Apple has made various aspects of the iOS available for 3rd-party developers to plug into. Those include plugging your own custom keyboard for your apps, or creating a widget for the iOS notification center.

    Today, we will go through the steps needed to create a Today widget in the iOS notification center, but since we will be using the NativeScript framework to do so, it will be all in JavaScript, rather than in Swift/Objective-C.


  • Deep-linking your NativeScript apps with iOS 9 User Activity and Core Spotlight APIs

    One of the biggest and greatest enhancements that arrived in iOS 9 (if not the biggest!) undisputedly is the deep-linking capabilities now open to the developers. Using the Spotlight search, your end-users can now search the contents of your app even if your app is not installed on their devices, granted that other users are already your app and browse the same content. Or, you can set some of the app contents to be private and available in the search only for the respective users.

    Of course, these search APIs are available in NativeScript, and today we are going to implement a NativeScript app that provides deep-linking capabilities​. Read on to learn how to do this.

  • How to analyze the app package and native visual UI tree of a NativeScript application

    And what’s in there actually?

    Applications written with web means such as JavaScript and CSS are usually taken as web or hybrid. With NativeScript we enable these web means allowing you to write in your favorite language (JavaScript or TypeScript - the choice is yours) achieving great, fast-performing native apps. But, in the dawn of NativeScript and even now when it’s v1, we have been encountering non-believers who wonder “Are the NativeScript apps real native apps as they execute on the device? Or, they are hybrid after all :)”

    With this blog post I would like to reveal the truth for the non-believers by dissecting a NativeScript app at runtime and displaying what objects are actually created and executed on iOS and Android. Well, I can tell you from now - ​these objects are the native UI components of the respective platform. But if you still don’t believe me, read on.

  • Take your selfie with NativeScript and its cross-platform camera API

    The camera sensor finds its place in more and more scenarios today. It’s not really just about taking the popular selfies or photos with friends, but also about serious business scenarios.

    Today, I would like to introduce you to the cross-platform Camera API and demonstrate how you can effortlessly take photos with both Android and iOS devices using a single shared JavaScript code base.

  • Using 3rd-party iOS Frameworks in your NativeScript Apps

    The NativeScript framework already provides a fairly comprehensive set of standard UI controls that you need to build an app. But what if you want to build an app with the NativeScript framework using a 3rd-party library? We’ve got you covered. With the NativeScript framework you can effortlessly take a native iOS or Android library and start using it with JavaScript. As an example, let’s look at how to build a simple Seismograph app with the NativeScript framework and Telerik Chart for iOS. Here’s what the final result looks like:


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