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
Xamarin
Score 6.0 out of 10
N/A
N/A
N/A
Pricing
Felgo
Xamarin
Editions & Modules
No answers on this topic
Xamarin
Free
Offerings
Pricing Offerings
Felgo
Xamarin
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
$850 seats
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Felgo
Xamarin
Considered Both Products
Felgo
Verified User
Anonymous
Chose Felgo
The helpful, responsive customer support. In contrast to frameworks like Flutter, you can count on a professional team that can help you out if needed.
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.
We prefer to use Felgo because of the facility to use it, and because Felgo has friendly forums where core developers participate as well as fast & helpful email support. And more, we can use ready-made components to balance any of your game properties at runtime, so also on …
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.
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 …
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 …
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, …
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.
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.
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.
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 …
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.
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 …
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, …
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.
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.
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.
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.
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.
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
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.
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.
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.
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.