Any difference between HTML app and QML with webview
I am doing some experiment with an offline Ionic-Angular HTML app.
I can see two options. Create an HTML app and copy the files to www folder or create a QML app and use webview to load index.html. Is there any particular advantage of using QML-Webview path?
It will depend on where you want to go.
A QML app will allow you to add features to the existing app, for example you can create menus or add gesture using QML.
While the webapp will remain a webapp fully based on the html based code.
QML IMO allows a better UX more consistent with the system.
But if you don't plan on doing much improvement on this app, the webapp is absolutely the easiest.
@AppLee If I opt for QML webview path, do I need to build it separately for different platforms?. like 32/64 bit arch
I guess at the moment, the webapp is build with 'all' arch support
Pure QML code is available for all arch so no need for that.
You will have to build for separate architectures only if you add some arch dependent code or library.
While creating offline web app using Ionic + Angular, I observed that the animations which Ionic provide are not so fluid in UT. I have OnePlus One with me and its not too low end hardware. The animations were much better in desktop Chrome browser. Is it because of the lack of hardware acceleration in UT browser?
The idea of creating pure native app is really nice. But I am a web developer and don't have any knowledge in c/c++. Moreover Ionic gives lots of cool designs and layout so that I don't have to do a lot in design area. So I thought sticking with web technologies would be better choice for me to kick-start app development.
Is it because of the lack of hardware acceleration in UT browser?
I'm not a web developer and I know it's a complete different job. And from my experience web is moving fast and technology become obsolete very quickly that's something I don't like: the lack of stability.
Maybe you can try using less "cool" "fancy" stuff because it's really resources hungry.
IMO QML is not so hard to learn (at least the basics) you can give it a shot maybe it'll solve your performance issue.
BTW UT uses QT 5.9, not the latest release, so be careful while reading the online doc.
@AppLee I did some experiments with Felgo. but didn't get much idea how to create a click package out of Felgo project. Is there any template available to create click package from Felgo project?
The weather app published by felgo looks good. They have lots of nicely designed components.
I don't know what Felgo is.
To create a click package I use clickable, that's the easiest way to produce it and it provides templates for various languages.
The Felgo SDK includes all the components you need to develop professional cross-platform apps and games.
Ok, then I guess you'll have to build Felgo's libraries for arm and integrate them using clickable to get a click.
If Felgo is pure QML then you'll have only to put it within your project so clickable can include it to the click package.