Overview
ProductRatingMost Used ByProduct SummaryStarting Price
NativeScript
Score 4.8 out of 10
N/A
NativeScript is an open source framework that allows you to create native iOS and Android apps, with one codebase, using ​the web skills you already have (JavaScript and CSS) and ​the libraries you already love​.N/A
SALTO Systems
Score 8.5 out of 10
N/A
SALTO Systems, in Oiartzun, offers electronic locking solutions and SDKs for entities in hospitality, and Salto KS, an API they state does not only preserve a brand but creates a completely customized access control solution.N/A
Xamarin
Score 6.0 out of 10
N/A
N/AN/A
Pricing
NativeScriptSALTO SystemsXamarin
Editions & Modules
No answers on this topic
No answers on this topic
Xamarin
Free
Offerings
Pricing Offerings
NativeScriptSALTO SystemsXamarin
Free Trial
YesNoNo
Free/Freemium Version
YesNoYes
Premium Consulting/Integration Services
NoNoNo
Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
Additional DetailsThe NativeScript framework and CLI are completely free and open source. NativeScript Sidekick is a free download to improve developer productivity with optional paid tiers for power users.
More Pricing Information
Community Pulse
NativeScriptSALTO SystemsXamarin
Considered Multiple Products
NativeScript
Chose NativeScript
NativeScript was indeed a better experience at first than Ionic. But the real game-changer in 2022 for cross-platform applications is Flutter now. We changed to it shorty after NativeScript, as it is much more stable, more widely supported, has a ton of extra features, and does …
Chose NativeScript
First and foremost, the codebase on which the project application was developed in NativeScript on 90% can be shared with React Native framework. Moreover, the documentation of the framework is extensive in a manner to allow developers the easy low-level entrance for the …
Chose NativeScript
I have use AngularJS and Angular for many years, and when it came time to build a mobile app, I was asked to use Android Studio. I did not have any trouble in developing apps separately with these two technologies. By trying to combine web app development and Android app …
Chose NativeScript
I have several hybrid alternatives like Cordova + jQuery Mobile and ionic (which uses Cordova and angular). These alternatives always let you down in the long run because the performance and "feel" is never comparable to a true native app. Especially when the app's complexity …
Chose NativeScript
Ionic
Ionic is an excellent Angular-based framework for mobile, and it does give a lot of access to the native device api's. However, the technology is based on Cordova, which means the apps being built are just webviews, with html, css and JS all running on the UI thread, and …
Chose NativeScript
We have previously evaluated Xamarin, and the time it took us to get started, install all of the software, license it, learn Xamarin, and create a app that runs and debugs on connected mobile devices was painful. With NativeScript and the Playground, we're able to get started …
Chose NativeScript
I've looked into and worked with multiple frame works such as Phonegap/Cordova, Ionic, and React Native. While they all allowed developers to create multi-platform applications easily, with different degrees of performance, I found them all to fall short in once you reached a …
Chose NativeScript
Unlike its competitors, NativeScript offers its users 4 architectural choices. It shines in the area of offering 100% day zero Native API access. The development experience is great and feels like you are home, if you are a web developer coming from Angular or Vue background, …
Chose NativeScript
I was once a user of Ionic Framework which operates on Apache Cordova. At the time, Ionic was the obvious choice because it was lightyears ahead of the other cross platform frameworks. However, because Ionic Framework and Apache Cordova require a WebView component to function, …
Chose NativeScript
Ionic is based on an embedded WebView running an app looking website in the background. It has been around for a couple years, but it does not compare well to real native applications. In most cases the UI just doesn't have the feel of a real native app, and performance is …
Chose NativeScript
The direct native API access without having to write any Java or ObjC was the ultimate decision for us. We can drop in a native Android/Ios library and instantly code against that SDK without any special work. Whereas with Ionic or RN, you have to write some Java/ObjC (or …
Chose NativeScript
Ionic and Apache Cordova are hybrid tools, both based on Webview which is ok for mobile offline data apps but for high-performance enterprise apps that is the limit. NativeScript can go where the number of rules and processing required force us to gain access to the native …
Chose NativeScript
NativeScript is superior in every way:
Vibrant community - there is an open slack channel where you can get advice and talk to other nativescript developers
Active development team - The NativeScript development team reaches out to their user base consistently for feature …
SALTO Systems
Xamarin
Chose Xamarin
Android Studio and IOS SDK are some of the competing programming methods for mobile development that competes with Xamarin. However, these utilize other programming languages like Java, or Objective C. In addition, these methods may be used more directly with Android or IOS …
Chose Xamarin
We use both Xamarin and React Native to create cross-platform applications fast. React Native is relatively new at our company and few developers have embraced coding in it as compared to developers building in Xamarin. I have noticed developers have it easy jumping from coding …
Chose Xamarin
Xamarin allows us to natively code against IOS and Android as opposed to just putting a Skin over it. Because of this native code stack the performance on Xamarin is off the charts better. You can really see the performance when you are using native phone features like GPS, …
Chose Xamarin
As I said before: Code sharing and using existing skills was the most important factor to choose Xamarin. With phonegap code sharing exists but business logic must be written in JS.
Chose Xamarin
Coming from a .NET background I always wanted to like Xamarin. Now that Microsoft bought them and made the product available to all, it's a no brainer.
Chose Xamarin
In Native app development we need to employ specialized developers solving some business problems in different technologies. Xamarin solves that problem to some extent delivering a native application experience. Hybrid has the same code base but suffers from lack of performance.
Chose Xamarin
Xamarin runs natively on MacOS, and the debugger and other integration and auto-complete tools are far better than Eclipse for C# .NET. It also carries much of the plugin/add-on capabilities that are so desirable on Atom. Eclipse is a better for generalized software …
Chose Xamarin
None of the HTML-based cross-platform solutions can easily provide a native look and feel like Xamarin can. I've had to rescue multiple organizations that went down this path only to be disappointed with the results.
Chose Xamarin
Apache Cordova is nothing more than a HTML Web VIew App. I've built an app using Cordova and it was a mess. With Xamarin, you get the platform level capabilities, which make the performance, in theory, no different than real native development. Cordova is not suitable for any …
Chose Xamarin
Xamarin is a good platform compared to Cordova, as it gives better API access, documentation and customer support as well as a robust community. It allows you to develop code using native Visual Studio and helps the developer to reuse the codebase for different platforms, …
Best Alternatives
NativeScriptSALTO SystemsXamarin
Small Businesses
Visual Studio
Visual Studio
Score 8.8 out of 10

No answers on this topic

Swiftify
Swiftify
Score 9.0 out of 10
Medium-sized Companies
Visual Studio
Visual Studio
Score 8.8 out of 10

No answers on this topic

Swiftify
Swiftify
Score 9.0 out of 10
Enterprises
Visual Studio
Visual Studio
Score 8.8 out of 10

No answers on this topic

Swiftify
Swiftify
Score 9.0 out of 10
All AlternativesView all alternativesView all alternativesView all alternatives
User Ratings
NativeScriptSALTO SystemsXamarin
Likelihood to Recommend
4.8
(0 ratings)
8.0
(0 ratings)
7.0
(0 ratings)
Likelihood to Renew
8.0
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Usability
-
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Support Rating
1.0
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
Implementation Rating
-
(0 ratings)
-
(0 ratings)
10.0
(0 ratings)
User Testimonials
NativeScriptSALTO SystemsXamarin
Likelihood to Recommend
NativeScript allows to easily integrate with native APIs by threading models. Moreover, the framework itself can be integrated with Angular, VueJS and JavaScript due to the fact that it was built on based on these frameworks. It allows you to easily maintain if you projects are based on these frameworks. Therefore, for the development of cross-platform applications it can be very handy!
Read full review
With the responsibility of securing a hospital, SALTO performs well. We have all but one public entrance completely secured by badge access only. This eliminates a lot of threats to our employees, our patients, and visitors to Republic County Hospital. SALTO helps provide peace of mind.
Read full review
Xamarin is well suited for several reasons. The first, it allows companies to share code across platforms. If the app has a lot of business logic and a fairly simple UI, Xamarin is great for this use case. Xamarin also works well if the developers who will work on the app are already fluent in .NET. Xamarin is less appropriate if the company has a lot of developers. If there are plenty of resources to develop apps natively then the headache of dealing with Xamarin's issues are not worth the effort. If the UI is very complex and has difficult animations it's difficult to debug visual/performance issues in Xamarin.
Read full review
Pros
  • 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.
Read full review
  • Security
  • Access tracking
  • Data storage
Read full review
  • We save development time with Xamarin, because we use Xamarin Forms an so we can share most of the code over 3 platforms.
  • We can use our C# knowledge to develop iOS and Android Apps.
  • Xamarin's integration into Visual Studio is very good and became even better during the last releases of Visual Studio.
Read full review
Cons
  • 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)
Read full review
  • I don't have any negative experiences with SALTO.
  • I have no suggestions for improvement.
  • I can't think of any recommendations for change.
Read full review
  • Having also done a lot of native mobile development, some of the IDE's features need to emulator their native counterparts. For example, trying to extract a string resource on Android in Xamarin Studio is painful. There are many useful tools in Android Studio that Xamarin should implement.
  • Xamarin will always be behind on native platform features. They must catch up when Apple and Google release new platform versions.
  • The biggest pain point is the random issues Xamarin continues to have. Having a large code base on top of a native platform makes it very difficult to debug issues. Every developer must decide if its an issue with Xamarin or the native platform. Bugs don't get fixed very quickly. Hopefully that will change with the Microsoft acquisition.
Read full review
Likelihood to Renew
The hybrid is ok but native is better for performance and the right use case I want to go for is the performance without dealing with too many development tools.
Read full review
No answers on this topic
Xamarin has been great for developing different projects efficiently and effectively. It's nice to reuse the core business logic across different platforms so that there are less to maintain and little replications are needed. The biggest benefit is that C# programmers do not have to learn a different language to do mobile development.
Read full review
Usability
No answers on this topic
No answers on this topic
If you are required to develop applications that are cross-platformed, Xamarin is a great tool to use. It will help save time and efforts from your development team to be able to build applications seamlessly for android, IOS, windows, and web on a single platform instead of requiring multiple tools to get the job done
Read full review
Support Rating
My focus has been, and must remain, with obtaining support from web resources over that of paid support programs. Many companies, including those of government agencies, do not have a budget sufficient for paying large sums of money to other organizations to answer questions. Even in cases where an organization did purchase support programs, developers often found that the delays in obtaining responses to development issues was excessive. I give NativeScript the lowest possible rating, due to the fact that their website content is severely outdated and of little use to a developer in a crunch. The NativeScript environment may be far better than I have been able to report, but held back from excelling due to poor support content. Being that I am often asked to push the boundaries in various areas, improper documentation is highly detrimental to a development team, and thuss a review. I would be more than happy to improve this review as the content of the support documentation provided by the NativeScript team makes its way to their website in the form of real-world examples which are applicable to all versions, or at least the most recent versions, of their product.
Read full review
No answers on this topic
I never had to contact support for any help. Most of the problems we ran into, we were able to identify and use peer support through blogs and other internet sources to resolve the problems. There are plenty of sources online which provide tutorials, discuss problems, etc. Example: StackOverflow
Read full review
Implementation Rating
No answers on this topic
No answers on this topic
Just with any programming tasks, have a plan first. Design out the system, spend time to build it correctly the first time and have plenty of testing and user acceptance opportunities. Xamarin was easy to implement for a C# programmer. However, you need to do tutorials to realize the platform's capabilities.
Read full review
Alternatives Considered
NativeScript was indeed a better experience at first than Ionic. But the real game-changer in 2022 for cross-platform applications is Flutter now. We changed to it shorty after NativeScript, as it is much more stable, more widely supported, has a ton of extra features, and does not rely on JavaScript and Android knowledge as much as NativeScript.
Read full review
No answers on this topic
Xamarin runs natively on MacOS, and the debugger and other integration and auto-complete tools are far better than Eclipse for C# .NET. It also carries much of the plugin/add-on capabilities that are so desirable on Atom. Eclipse is a better for generalized software development, provided a developer is comfortable switching between the IDE the command line for certain parts of their workflow, like building, package management, or debugging. But for C# .NET development on MacOS specifically, Xamarin is the best product I've used for the job.
Read full review
Return on Investment
  • We had built this particular app once already, during a 6 month time frame, using Ionic. When we hit the wall, we chose NativeScript, and built the whole app from scratch. We estimated another 6 months, but completed the work in 4 months due to the ease of use.
  • We have found collaboration with our client much easier because of the simplicity of releases and speed of development.
  • Having a tool like NativeScript has allowed us to make competitive quotes for mobile app development contracts, where previously that would have been closed to us due to our lack of native development experience. Being able to build iOS apps without a Swift-code expert has opened those doors for us.
Read full review
  • N/A
  • N/A
  • N/A
Read full review
  • Code Sharing - We were able to launch an Android implementation of our app within weeks after finishing iOS. The amount of time taken to develop a new platform is very small.
  • Monetization - not the best, but definitely getting better. We've had issues with finding suitable ad networks that work with Xamarin.
Read full review
ScreenShots

NativeScript Screenshots

Screenshot of Example of a styled NativeScript list viewScreenshot of Charts and graphs available as part of NativeScript UIScreenshot of Groceries – the app you build as part of the getting started tutorialScreenshot of Leverage native mapping systems with NativeScript