Felgo provides components, tools and professional services for developing apps on Mobile, Desktop and Embedded platforms. The Felgo framework extends Qt with 200+ APIs. Among them is support for 3rd party SDK integrations like push notification or analytics, native iOS styling, Qt Quick Controls extensions for native look & feel on Android & iOS, density independence and responsive layout support. Felgo also provides features like AR (Augmented Reality) and Machine Learning integrations…
N/A
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
Xamarin
Score 6.0 out of 10
N/A
N/A
N/A
Pricing
Felgo
NativeScript
Xamarin
Editions & Modules
No answers on this topic
No answers on this topic
Xamarin
Free
Offerings
Pricing Offerings
Felgo
NativeScript
Xamarin
Free Trial
Yes
Yes
No
Free/Freemium Version
Yes
Yes
Yes
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
$850 seats
No setup fee
No setup fee
Additional Details
—
The 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.
Felgo has the shortest learning curve making the teams productive almost from week 1. It also has easy tooling with fast iterations without having long compile and deployment times. So far, we believe that this product was a good fit to our current talent and resources.
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 …
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 …
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, …
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, …
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 …
Felgo shines in rapid prototype development and fast iterations. It also has a very short learning curve compared to many other technologies that promise "code once, deploy everywhere." It is not appropriate if you are not willing to mess with the licensing related to Qt but I am still waiting for a clear answer on my doubts from the Felgo team.
I gotta be honest, after a PoC period, we choose to rewrite the whole application in a different cross-platform app. Our developers had to invest a lot of time and effort to debug a lot of plugin-related issues, which we needed to utilize the android mobile phone capabilities. QR reader, special visualizations, and fine-tuning were really hard and often resulted in writing native Android code instead of using the shared Angular code. In the end, we think that writing a standalone Android app and an Angular app would have been a better alternative, as the shared code base was so unreliable that it did not save us any time.
If you are required to develop applications that are cross-platformed, Xamarin is a great tool to use. It will help save time and effort 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.
Ready available solutions for all platform mobile app development.
Live hot reloading of UI and other advance controls by Felgo implemented in Qt.
Using Qt underneath provides an opportunity to developers to use it in all kind of sectors like embedded devices, mobile apps, desktop apps, games etc.
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.
Xamarin allows you to write cross platform code. This allows companies to build apps more quickly by writing less code. Having code abstracted and reused across multiple platforms allows for more testing and less issues overall.
The ability to use Visual Studio is a huge plus. Visual Studio is one of the best IDE's available and being able to write cross platforms apps while in a great IDE makes everything less painful.
Xamarin is now free with a large company backing. This means that bugs on the platform get fixed more quickly and there is a large community of developers.
I am happy with the constant feedback that I am receiving from the team. Although most of it is marketing related, there are some interesting and valuable materials that they have been pushing to ease my learning.
The quality of the documentation and the ease of use may be some important values to take into account.
We believe that the agility that we have acquired until now for developing apps for our business cases give this framework an important lead.
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.
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.
As with any product, Felgo has some edges to it, but from our past experiences evaluating "code once, deploy everywhere" platforms, we were really surprised at how fast the team went from exploring, into playing and presenting prototypes in very little time.
The dev cycle is really fast as I can get an almost instantaneous feedback on the changes that I make. And it is refreshing to see how I am able to target several platforms at once.
The javascript plus QML combination made it really easy to pick up for me and I am certain sure that many devs can migrate from Web only into multi-platform in a fast manner.
And there is also the possibility to implement C++ code if the need arises to support and bridge native libraries.
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
The community support is excellent. They have a slack community as well as a discourse forum forum.nativescript.org Both of these offer community driven support. The forum is more for a threaded discussion. The slack community is more for a quick talk.
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
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.
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 potentially creating very slow experiences for users. NativeScript is a truly native solution, and so provides a faster user experience. ReactNative We evaluate ReactNative, and found it much the same as NativeScript. The main difference is that your JS is all written with React, while NativeScript lets you choose between normal JS, Angular, and Vue. For our team, Angular was the most appropriate choice.
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.
The poor quality of NativeScript documentation has the potential to weigh heavily on development timelines, budgets, and QA resources in a NEGATIVE manner.
The poor interoperability of NativeScript plugins can significantly increase development time.
The need to seek out professional instruction to learn how to use NativeScript effectively may become a burden on your budget.
The number of breaking changes between versions of NativeScript, may cause your development efforts to lag further behind the most recent releases of NativeScript and your other chosen environments than you are accustomed to.
NativeScript still does not support the latest major version of Angular. Any significant changes to the other environment components of your systems may hold you back even further while NativeScript plays catch-up.
