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
Pricing
Felgo
NativeScript
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Felgo
NativeScript
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
$850 seats
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.
It is a very good tool for making all types of mobile and web applications once you know how to use it. It allowed us to realize several application concepts, such as currency converter, pregnancy monitoring, QR code flash for product evaluation. No need for native SDKs, Build in and Install from Cloud with the Felgo Build Server.
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!
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.
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)
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.
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.
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.
As I was already a C++ and Qt developer, Felgo was obvious choice over other tools. Also its cross-platform solutions for mobile apps and Qt's ability to provide cross-platform tool for all other devices makes this perfect choice.
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.
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.
