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.
This post will go through the process of creating an Android jar library which will then be referenced from within a custom NativeScript plugin.
It’s been an exciting release cycle for the NativeScript team. We just published our first official release in May and since then there has been an insane amount of community activity. There are now more than 4k stars on Github, over 300 issues, 260+ forum threads, and more than 20 plugins have been created by the community. Did I mentioned the new G+ NativeScript group? We are already working with the first companies to prepare their apps on the app stores. If you are working on an app - please let us know - we are eager to see what you are building!
Telerik UI for NativeScript is suite of native UI components that adds a lot of advanced features on top of the default UI components we are shipping in the NativeScript framework. Telerik as a company has a long history of delivering such UI components that range from Lists, Data Visualization, Data Input for various development platforms. For NativeScript the ambitious goal is to provide the same rich range of components that will make your app look professional and will enable you to stand-out from your competitors by providing the best UX and performance. It is important to note that this suite comes with professional support and 24 hour guaranteed response time and unlimited support tickets.
Between npm modules and NativeScript plugins, which are nothing more than npm modules with the ability to use native code and libraries, you have now have a large collection of modules and libraries that you can leverage in your NativeScript apps. In this article you'll see several examples of how to make this happen.
And what’s in there actually?
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.
Two weeks ago we kicked off the Summer of NativeScript, our program to get the development community excited about NativeScript, and adorned in some stylish NativeScript t-shirts.
And excited you are. In the last two weeks we've seen well over a dozen meetups scheduled spanning seven countries and five continents. (I'm looking at you Asia and Antarctica).
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.
Summer is a great time to get excited about building apps with NativeScript. Why this summer? Because if you run a NativeScript meetup in July, August, or September and let us know about it, we'll send you a NativeScript t-shirt and a pack of NativeScript stickers.
NativeScript 1.1 bits are live and you can start using them immediately! If you are updating from 1.0 - please read the update instructions. With this release we delivered three new fundamental featurenpms for the NativeScript framework - support for npmmodules, support for native iOS libraries and the initial version of NativeScript plugins. We also delivered a number of enhancements and bug fixes to the core framework - NativeScript is now more stable and faster.
(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!