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
Oracle Java SE
Score 8.8 out of 10
N/A
Oracle Java SE is a programming language and gives customers enterprise features that minimize the costs of deployment and maintenance of their Java-based IT environment.
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.
Oracle Java SE is well suited to long-running applications (e.g. servers). Java Swing (UI toolkit) is now rather outdated, lacking support for modern UI features. JavaFX, the potential replacement for Swing, has now been separated out of Java core. Ideally, there would be a path to migrate a large application incrementally from Swing to JavaFX, but due to different threading models and other aspects, it is difficult. At this point, it is probably better to use an embedded web browser (e.g. JxBrowser) to provide a modern UI in HTML/Javascript and keep just the business logic in Java.
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.
Since Java runs on a virtual machine, it's generally considered to be agnostic of the hardware it's running on. It allows for deployment across a mix of hardware setups with the same binary.
Lots of literature, third party libraries, support forums, and books have been devoted to Java in general, making it a great language to use to support the business.
Backwards compatibility has been an important strength of Java for us. Legacy code that isn't ready to be retired yet can still run on our newer setups despite using older versions of OJSE.
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.
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.
The language is fluent and has good support from a number of open source and commercial IDEs. Language features are added every 6 months, although long-term service releases are only available every 3 years. It would be nice if some of the older APIs were depreciated with more pressure to move to the new replacement APIs (e.g. File vs. Path), but transitions to new features are generally well implemented.
Java is such a mature product at this point that there is little support from the vendor that is needed. Various sources on the internet, and especially StackOverflow, provide a wealth of knowledge and advice. Areas that may benefit from support is when dealing with complex multithreading issues and security libraries.
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 choose Java as our system has multiple sub-applications that have different purposes and architecture including back-end applications, front-end UI, front-end Rest API, and Selenium Automation tests. They are deployed in Windows and Linux, communicate with each other using Rest API, RMI and Queue Message and need to support different deployment environment from Dev, Test, UAT to Production so using Java allows us to have a common standard from development, build and deployment for all applications.