Qt Widgets for Mobile development. Is it OK?
-
Hello all!
I am researching ability to develop mobile application on pure Qt/C++ without QML. Is it OK to develop on Qt Widgets for mobile? What is advantage or disadvantage of this approach in developing? All that I found about this topic a little outdated +2-4 years old, since this post Qt moved forward a lot. I need information about current state in case of developing on Qt Widgets for mobile. -
Hello all!
I am researching ability to develop mobile application on pure Qt/C++ without QML. Is it OK to develop on Qt Widgets for mobile? What is advantage or disadvantage of this approach in developing? All that I found about this topic a little outdated +2-4 years old, since this post Qt moved forward a lot. I need information about current state in case of developing on Qt Widgets for mobile. -
Hello all!
I am researching ability to develop mobile application on pure Qt/C++ without QML. Is it OK to develop on Qt Widgets for mobile? What is advantage or disadvantage of this approach in developing? All that I found about this topic a little outdated +2-4 years old, since this post Qt moved forward a lot. I need information about current state in case of developing on Qt Widgets for mobile.@bogong said in Qt Widgets for Mobile development. Is it OK?:
Is it OK to develop on Qt Widgets for mobile?
Yes. Widgets work on mobile platforms.
What is advantage or disadvantage of this approach in developing?
Advantages:
- all QtWidgets advantages in general: a complete set of widgets (with table view, tree view etc.), everything is compiled and optimized, no JS engine overhead, no QML engine overhead, no need to include anything via QRC
Disadvantages:
- widgets look horrible on mobile platforms
- making fluid, animated UIs is much harder in widgets
- mobiles are less tested with widgets, so potentially there can be more bugs
All that I found about this topic a little outdated +2-4 years old, since this post Qt moved forward a lot. I need information about current state in case of developing on Qt Widgets for mobile.
Qt has indeed, but QtWidgets have not developed a lot in that time, so the information you have seen is probably still valid.
-
@bogong QML is better suited for mobile. It is more flexible and uses graphics acceleration (QWidgets are rendered on CPU).
-
@bogong said in Qt Widgets for Mobile development. Is it OK?:
Is it OK to develop on Qt Widgets for mobile?
Yes. Widgets work on mobile platforms.
What is advantage or disadvantage of this approach in developing?
Advantages:
- all QtWidgets advantages in general: a complete set of widgets (with table view, tree view etc.), everything is compiled and optimized, no JS engine overhead, no QML engine overhead, no need to include anything via QRC
Disadvantages:
- widgets look horrible on mobile platforms
- making fluid, animated UIs is much harder in widgets
- mobiles are less tested with widgets, so potentially there can be more bugs
All that I found about this topic a little outdated +2-4 years old, since this post Qt moved forward a lot. I need information about current state in case of developing on Qt Widgets for mobile.
Qt has indeed, but QtWidgets have not developed a lot in that time, so the information you have seen is probably still valid.
-
@sierdzio All that I got from experience of developing on Qt - it's really better to follow latest LTS release. In other way might be not so simple to develop.
@bogong said in Qt Widgets for Mobile development. Is it OK?:
@sierdzio All that I got from experience of developing on Qt - it's really better to follow latest LTS release. In other way might be not so simple to develop.
Indeed. And even with LTS, the usual rule of "don't use .0 releases" (like 5.12.0, 5.13.0) still holds. Initial releases tend to be very buggy.
-
@bogong said in Qt Widgets for Mobile development. Is it OK?:
@sierdzio All that I got from experience of developing on Qt - it's really better to follow latest LTS release. In other way might be not so simple to develop.
Indeed. And even with LTS, the usual rule of "don't use .0 releases" (like 5.12.0, 5.13.0) still holds. Initial releases tend to be very buggy.
