Felgo vs. Flutter by Google

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.

Flutter is well known for native app development, if you have android studio installed on your system, you can quickly start using it. This might not be the best choice for you if you do not wish to learn a new language, i.e. Dart and you do not know it already.

Incentivized

• 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.

Incentivized

• It is powered by Google, so a great technical community is backing it.
• The development of native apps is an easy process using Flutter.
• As it is an open-source tool, we can use it without paying anything.
• It provides nice UI options.

Incentivized

• QML component / C++ code with hot reload feature.

• Occasionally updates to the Flutter SDK result in wide-sweeping changes that seem to not be thoroughly tested and considered. Flutter sometimes evolves too fast for its own good.
• While the 3rd-party Flutter package ecosystem is vast and rich, 1st-party support for basic things (audio/video playback, battery information, Bluetooth services, etc.) are lacking. You are occasionally forced to rely on an open-source package for use-cases that other platforms have native support for.
• Documentation, particularly around testing, is lacking. While there are some great docs, like the Dart Style Guide, many Flutter-focused support documents are lacking in quality and real-world usability.
• Flutter allows you to architect an app however you want. While this is a great feature, it also adds complexity and leads to the current state of Flutter's state management, where there are 50+ options on how to organize your app, with very little official guidance or recommendations from the Flutter team. For a beginner, this can create decision paralysis.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

I have experience with react and React Native. I would say that the idea behind all those frameworks are quite similar. However, I found the javascript-based frameworks a bit more accessible as you could utilise your javascript knowledge. Here, Flutter works with its own language. This has advantages and disadvantages sometimes. I found the community around javascript frameworks bigger and therefore sometimes more helpful. However, Flutter does a good job here as well. I think the main argument for Flutter is its usability for less experienced developers. If you do not have knowledge in javascript or other programming languages then I think it is much easier to start with Flutter than with another framework like react. I think the package that you get form scratch is better than in the other frameworks were you have to set up and learn a lot more before you can start.

Incentivized

• Development cost became low
• Easy to learn
• created well performed cross platform application

• The rapid development capabilities of Flutter allow us to build apps we could not have previously considered commercially viable, opening new revenue streams.
• Free and open licensing made adoption very easy (ie. free/low cost!).
• In comparison to Qt, our time spent arguing with build tools and perfecting development environments has decreased substantially.

Incentivized