We used NativeScript as per customer requests to implement mobile and web-based cross-platform applications used in the customer service …
In an effort to move from having separate projects for Angular web development and Android Studio for Andriod app development, I have been …
We are testing NativeScript to see if it will be a good fit for the next version of our app. We have an e-learning education platform …
We are using NativeScript on a single mobile project at the moment. It is the framework which supports development of this entire project …
We are a consulting company and use NativeScript for apps internally and externally for customers. We chose to use NativeScript as a …
I currently use NativeScript for multiple applications that are in various stages of development. In my opinion, NativeScript is one of …
I work at a fitness based startup. Our app, "AnyGo" is built entirely using NativeScript. I was the one who proposed to the team, to use …
As a very small development shop, NativeScript allows us to create cross platform "native" mobile applications for Android and iOS while …
Our organization uses NativeScript to build different mobile applications for clients with different needs. NativeScript has been a great …
At nStudio, LLC. we use it as our suggested application framework to clients for developing iOS and Android applications that integrate …
NativeScript is the main tool to develop mobile apps for internal and external projects. The main feature is the capacity to develop one …
I use NativeScript as the primary platform for developing native mobile applications. We have a native mobile app called Daily Nanny …
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of NativeScript, and make your voice heard!
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.nativescript.org/nativescri…
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
- Supported: Extensive code sharing between mobile platforms (including UI) and web apps (when used with Angular)
- Supported: Deliver high-quality mobile apps to multiple platforms faster, using web developers you already have
This spring and summer have been full of new NativeScript features, tooling options, and improvements. NativeScript is evolving into something more than just an open source framework. In this webinar, we'll talk about all the new goodies for you and show you how you can crush it in mobile app development
- Visual Studio Code
- Visual Studio 2015/2017 Coming Soon
|Operating Systems||Windows, Linux, Mac|
|Mobile Application||Apple iOS, Android|
Xamarin are common alternatives for NativeScript.
Reviewers rate Support Rating highest, with a score of 1.
The most common users of NativeScript are from Small Businesses (1-50 employees) and the Computer Software industry.
Companies can't remove reviews or game the system. Here's why
- Teach the basics of the framework
- Integrate to existing Angular project
- Lots of bugs in the android build, visual and interface wise as well.
- Android functions were missing which was crucial
- Poor plugin support, buggy plugins
- Low response time to new android features
- Access to the entire native API
- Support for native iOS and Android libraries
- Cross-platform declarative UI and source code
- Powerful data visualization with native UI tools provided
- The need to know the native Android and iOS APIs to access device hardware and other platform-specific functionality
- Not all user interface components are available for free
- NativeScript has no HTML and DOM, which requires some deep knowledge of different UI tools to be implemented instead
- Executes really fast compared to other alternatives
- Compiles down to native code and runs as a native app
- Provides a way to split custom content, including CSS styles, into separate files per target platform
- The ABSOLUTE WORST documentation I have ever seen for an environment which advertises direct involvement with Google and other vendors. Their website content appears to be written once as a version comes out, and then is never updated again as follow-on versions with significant changes are released.
- Examples provided are often written from an expert's view, making far too many assumptions, and containing too much outdated content, to be useful to any developer who is just learning the environment.
- Some areas of considerable interest, such as the development of composite plugins (draw on the use of existing components as opposed to new native components), are void of ANY useful support.
- Support is left up to the use of stackoverflow.com questions and answers, and several of those who respond frequently, do so with language which comes across in an arrogant manner, and only serves to help in a specific instance, not in a global manner which would be useful to all.
- The description of the environment is misleading. One is often led to believe that use of NativeScript will significantly reduce development effort and time. I would venture to guess that in most cases, this is untrue. A lot of effort is spent trying to keep the web app and the mobile apps at the same level of development, because the NativeScript components DO NOT support web pages. The user interface of a web app is still almost entirely new development.
- The appearance of an Android mobile app is only like that of an iOS mobile app about 90% of the time. You cannot develop an app in NativeScript for an Android device, and expect it to look the same for iOS apps. Organizations who read about NativeScript, are misled into believing that the will be able to reduce staff by eliminating all Android developers or all iOS developers. To do so, is unwise, and in most cases, I believe that organizations will find it easier to develop for one mobile platform and then have the other mobile platform follow one version behind.
- NativeScript advertises that it provides great support for Angular and other environments. While I cannot speak directly to those other environments, I can say that the integration between NativeScript and Angular is CLUNKY and PROBLEMATIC! What is easily accomplished in Angular, is a headache in NativeScript, and ends up degrading the quality of use within Angular. For example, Angular allows for developers to very easily develop components which reduce code duplication. Developing a NativeScript UI plugin (aka composite plugin) is made so difficult through the abundance of BAD information on the NativeScript website and manual operations to get it to work within Angular, that it defeats the purpose of building them. I see developers spending more time trying to fix the integration of a UI plugin than they spend in actually using the plugin.
- True native app. The app uses native components and that is quite noticeable in the overall performance of the app. NativeScript is also awesome in the way we can access the native APIs, so we are never really constrained by the framework. If we need, we can just dive into the native APIs without leaving our environment and language (JS).
- Cross-platform. Builds for Android and iOS. It deals with the platforms differences very well.
- Support for Vue.js. Even though it is just a community effort, the NativeScript-Vue plugin is the best alternative to build native Apps with Vue.js. That was a major factor to go with NativeScript.
- Web build. It is still hard to share code with a web build. In our case, we want to build a web app with pretty much the same functionality. Other frameworks are stronger at this point.
- No hot-reload. It still takes a couple of seconds to test an app. React Native does it better... With NS-Vue, the live-reload is even more fragile...
- Tooling. Overall, NS could use better tooling. Again, RN does it better.
- Better NS-Vue support. It is improving very well, considering it is a community effort. I see NS organization 100% supporting NS-Vue, but it is still not at the same level as NS-Ng, for instance.
- It is very quick to get started using NativeScript. We can generally onboard a new developer into the project in just a day or two.
- The open source community surrounding NativeScript allows our team to find solutions to open issues quickly, as well as give back by fixing some issues ourselves. Work can progress quicker with the plugins other developers have already built.
- The frequency of updates can make it hard to stay fixed to a common version. I found that there were so many improvements happening that it was worth bumping versions and adjusting the code at least every 3 months. This added extra development time, which also added stress. The benefit is worth it, but it's important to keep in mind that sometimes even a bugfix version bump will require some code changes.
- We also found the fractured dependencies hard to keep up with at times. The nativesript-cli, tns-android, tns-ios and nativescript-angular dependencies all have their own release cycles that are close together, but not tied together, and that has downsides when prioritising upgrades during a release cycle. Again, the benefit to upgrading is worth it, but staggered releases do add additional complications.
- Documentation is good, but could be better. Over the past year, this has been greatly improved, but there is still a delay between the adding or refactoring of features and the updates to the documentation.
- The plugin ecosystem is open source, which is good, but as with your own project, the authors of these plugins also have to keep up to date with the changes in the repos, and that isn't always done in a timely fashion.
- The NativeScript Playground sets NativeScript apart from other technologies. The NativeScript Playground is a browser-based environment for developing simple NativeScript apps. It’s a great place to get started learning NativeScript, as you can develop apps without needing to install the various SDKs and tools needed for native iOS and Android development. All you need is your browser, and an Android or iOS mobile device connected to the internet to get started. We use the NativeScript Playground to quickly prototype apps. It's an extremely powerful tool.
- There are dozens of online resources for getting started, troubleshooting, and staying up-to-date with NativeScript: forums, slack channel, twitter, online docs, NativeScript snacks, NativeScripting, blogs, etc. The community has been very strong, and continues to be a shining star NativeScript.
- If users jump directly into NativeScript Angular and are not familiar with NativeScript or Angular yet, it can be difficult to understand where NativeScript ends and Angular begins. This can be confusing.
- Code Reuse - With NativeScript you can share code between Native and Mobile Applications.
- Ease of use - NativeScript SideKick makes working with NativeScript a breeze and allows us to get an application set up for development in a few minutes.
- Occasionally there are inconsistencies when it comes to styling and layouts between Android and iOS, this can be frustrating especially in the beginning because you are usually working with one platform and then switch to the other only to have layout issues.
- New releases sometimes are buggy.
- NativeScript has a large repository of plugins at market.nativescript.org for the times when you want to boost your development speed.
- NativeScript gives you 100% day zero Native API access.
- NativeScript doesn't use any webview to render the UI. So you get Native UI, and therefore better performance, when compared to things like ionic or phone gap.
- Nativescript runs everything on a single thread. i.e., the UI thread. If you want to offload some processing, you have to use web workers. This experience can be improved in the future releases.
- Currently NativeScript only have hot reload when you change the UI file or Css file. There is no hot reload when you change Js/Ts file, unlike Google's Flutter. This is also something which NativeScript will get in the future releases.
- In current version of NativeScript, there is no livesync when building with webpack. This feature will be added with NativeScript 4.x. (an RC version for 4.x is already available)
- Native mobile applications built with NativeScript that do not rely on a WebView component result in extremely fast performance and a happy user experience.
- NativeScript has a lot of plugins for features such as charting that would otherwise be very complicated to implement in iOS and Android if not using NativeScript.
- The documentation could be improved to be more consistent across all supported frameworks like Angular, Vue.js, and Core.
- The application binary size could be reduced to be more in line with pure native and other similar frameworks.
- Easy to use abstactions for common elements such as action bars, tab views etc.
- There is no real hot module replacement, where changes made to the source code reflect on the device instantly.
- There are no ready-made UI collections, so applications have to be built using the default UI elements, and then styled manually.
- The CLI for development workflow is very great. The livesync option for fast dev iteration works really well.
- Styling native apps is not easy but NativeScript provides an abstraction of CSS to easily style native apps similar to how web apps are styled.
- The one area we are wanting to see is Hot Module Reloading, this is supposedly in the works but we anxiously awaiting it to be implemented. While the livesync is great it sometimes can be a hinderance to the work flow when the app has to restart for code changes, where HMR would allow instant code changes without an app restart.
- The layouts could use some better "guessing" on what the developers are trying to do if they are not sure of how to do things, the learning curve for layouts can be rough for new devs.
- The fastest transition from prototype to final product
- Native performance, you can exploit the hardware better than hybrid tools
- If you come from the nodejs world, you will have to sacrifice some ways to deal with data. For example, we had to sacrifice PouchDB for offline data
- The final size for Android could be huge compared with hybrid tools or the sameNativeScriptt for iOS
- Some native development is required in order to exploit all the components
- Sometimes web development experience is not enough. Even with Angular you need to learn some new concepts. Once dominated, you can rock native mobile apps
- Native Performance: NativeScript apps are entirely Native. They are not hybrid apps, each UI element is from each platform's UI library, so the performance is that of an application developed in Java for Android or Xcode/Swift for iOS.
- Plugins: The NativeScript community is a vibrant contributor to the plugin marketplace. You can find a plugin for almost any functionality.
- Access to Native APIs: With the way the NativeScript is built, you have access to all Native APIs as soon as they are available on the device, NativeScript does not need to expose access. So as soon as a new feature comes out in the OS, you can utilize it in your NativeScript app.
- Documentation Clarity: Due to the many different ways you can write NativeScript apps (Vanilla JS, TypeScript, Angular, Vue, Webpack), the documentation is not always accurate.