Felgo Reviews & Product Details

We like: the power and versatility of Qt, the Felgo library of ultra-productive components, the Felgo plugins, the Felgo doc, the Felgo cloud builds service, the always responsive and efficient Felgo support, and of course the efficiency and ease of use of the QML language coupled with Javascript (while being able to call on C++ as reinforcement in complex cases).

With my company AppliStudio and its label Kovalia we have been trusting Felgo for years. We have successfully and satisfactorily developed a dozen applications (mobile, desktop, embedded, etc.) for our customers and our in-house productions. We sometimes use other development frameworks, but when we have the choice, we prefer Felgo for its great possibilities, efficiency and versatility. Review collected by and hosted on G2.com.

As with all development tools, we encounter some small bugs in some libraries and some small errors in the doc, but nothing abnormal! And since the support responds well and patches always arrive pretty quickly, there's not much we don't like about Felgo. Review collected by and hosted on G2.com.

how it can help testing visuals very quickly. Review collected by and hosted on G2.com.

Installation is diffcult and time consuming. Review collected by and hosted on G2.com.

Live Code Reloading, easy for building across different platform Review collected by and hosted on G2.com.

Smaller community, performance overhead with huge size of install files Review collected by and hosted on G2.com.

For any C++/Qt developers looking to make mobile applications, I'd highly recommend Felgo. For me, QML is a familiar and effective way to create user interfaces. Felgo allows me to easily create mobile applications that look native. Just like Qt, the documentation is great. There are a good amount of examples as well. With the Felgo Live client, it is easy to test your apps on different devices, and it even has a hot reload capability. Review collected by and hosted on G2.com.

I had a few hiccups getting started. I had some issues trying to deploy to my mobile device for testing, but I I was able to resolve them by reading through the console errors I was getting (ended up being related to the version of the JDK I had installed). Review collected by and hosted on G2.com.

The framework is easy to learn, with the documentation & training materials.

The easy use of QML and the best C++ libraries as a back-end.

The helpful, responsive customer support Review collected by and hosted on G2.com.

Nothing I have found as of now.

Experimenting all the things to get best out of it. Review collected by and hosted on G2.com.

It has all the models you need to create your mobile applications. Applications automatically generated for Android and Apple and therefore no need for multiple codebases. Review collected by and hosted on G2.com.

To create your hardcoded other than the scripted application you will need to use C++ which has a tough learning curve. The tool is also embedded into Qt IDE instead of having its own custom installation for Felgo only. Review collected by and hosted on G2.com.

Significantly increased development speed due to out-of-the-box APIs & integrations that allow reusing code across platforms. Review collected by and hosted on G2.com.

Lack of online teaching material on the web, due to its unpopularity. Review collected by and hosted on G2.com.

- Ease of use.

- Multiplatform support.

- Lots of high level functionalities.

- No need to reivent the wheel. Review collected by and hosted on G2.com.

- The "Live" window that pops up all the time. Review collected by and hosted on G2.com.

I was first attracted into getting to the "code once, deploy everywhere" paradigm that is part of their attention grabber.

But I got really in love into the fast development cycle experience that I discovered.

I thought at first that my learning curve would be a lengthy one. But I am really surprised at how fast the development cycle is and how far I have gotten into creating prototypes in just a week after downloading and installing it. It reminds me of the way I was used to creating fast and attractive apps when I developed under Adobe Flash.

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.

I am also 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. Review collected by and hosted on G2.com.

I believe that some points that are not so clear to me might be laying in the way that the Qt and QML related licensing models could intertwine with the projects that I am creating.

It is not clear to me if there are additional fees or open-source licensing related constraints that must be taken into account to avoid compliance with the Qt licensing model.

Of course, there are the many contact routes and emails that the team has sent to me and I am right now expecting for a more human-understandable way of approaching to licensing.

There is also the way that the initial Splash Screen and loading phase that make the apps created feel like running in a container and not a real native experience. Although having this container framework seems to be true, I believe that a more sophisticated splash would help to better this odd feeling while the app loads. I am proud of having the Felgo logo starting my apps, but a more elegant solution would be in place. Or maybe there is something I must learn to change the way the app starts. Of course, there is the paid option where you can even remove the splash screen, but I don’t think this to be the real solution. Review collected by and hosted on G2.com.

Not much. Lots of pieces are almost great, but every piece has at least one big weakness. One of the support developers was really helpful. He's the only thing about Felgo that was worth it. Review collected by and hosted on G2.com.

Sales - Starting with the sales process - I was sold an Enterprise package with 5 hours/month. Then after a month they changed it to 5 hours total. And additional support hours were incredibly expensive. Most companies I've dealth with would at least attempt to correct the situation. Felgo did nothing. If you're a North American developer used to a straightforward sales process, stay away from these guys. They're a bait and switch operation.

Tooling - The tooling is almost good. The quick turnaround from code to screen makes the initial development pretty quick. However, there are massive differences between what you see during the dev process and then what you get when you actually build the app.

Cross-Platform - Similarly, the "cross-platform" features are almost great, but the flaws make it terrible. You'll wind up spending more time on the last little bit than you did on getting the app to Beta. Really, the widgets don't stay where they're supposed to, and there are lots of eccentricities that you can only learn if you pay for support. I just want to reiterate this is NOT a true cross-platform development platform.

Documentation - the documentation is terrible. It looks great on the surface, but when you actually get into the details, much of the documentation is actually wrong. And there are significant pieces of documentation that are just missing. The documentation refers to the previous version of the tool -VPlay Engine - which should have been an obvious clue.

Plugins - Having worked with 1/2 dozen other cross-platform mobile development frameworks, I expected the plugins to be "install and forget." However, many of the plugins require you to selectively copy and past dozens of files and directories by hand, then go into the project files and edit a number of configurations. It's the kind of thing I expect in an early stage, free, open-source project, but feels amateur in a product that carries a premium price.

Cloud Build - They sell their Cloud Build process as a simple plug-and-play system. I love the idea, and some of the architecture ideas are great. However, in practice it's hard to use except in the simplest use cases. Push Notifications, for example, can't be built in to an OSX build. You wind up having to import the project into XCode, enabling Push Notifications, rebuilding etc. etc. So it's easier to just build in XCode from the start.

Comparisons - compared to NativeScript, React Native, Flutter, and the other cross-platform frameworks I've used, I found Felgo to be a distant last. Parts of it are shiny and nice, but on the whole it was a huge disappointment. Review collected by and hosted on G2.com.