Native Android/iOS layouts + QML/JS manipulation. Possible? Makes sense?
-
Hi there
QtQuick controls and page transitions are quite different from native iOS and even Android ones. Controls style will undoubtedly improve, but it will take time and won't look 100% (or even 90%?) native anyway.
Both platforms, however, have native declarative UI languages, sort of similar to QWidget-based form files. Could it then be possible to define fully native Android and/or iOS UI using these native things, but then manipulate them via C++, JS and maybe even QML (exactly main app list could be done great with QML, but toolbar chrome and page transitions.. better be native). BlackBerry 10 went this way even further: they exposed native Cascades wrappers to QML and made it possible use QML for defining native layouts. You certainly look QML layouts power, but use QML data structures and a part of UI can still be rendered with QML (okay, this didn't work in BB10, but could have been implemented).
Could something like this be efficient in Android/iOS world as well?
I guess technically you could engineer a something like this already right now: load native form and expose it to QML Engine. Yet there is a bit of distance between technical possibility, a proof-of-concept demo project and maybe a roadmap to make it a primarily supported way.
What do you guys think? Would such a mix of native-QML make sense? Or is it better to hack QtQuick controls and page transitions to look native enough?
