5 ms·
I tried Cordova three weeks ago, on my Nexus 10 (Android 5.1.1). I wanted to have a native UI, so I tested angular-material and Polymer. I wasn't too happy with
by andresmanz 11y ago
I tried Cordova three weeks ago, on my Nexus 10 (Android 5.1.1). I wanted to have a native UI, so I tested angular-material and Polymer. I wasn't too happy with the result, due to stuttering animations kind of ruining the UX.
Having a shared C++ code base and the respective native UI code works perfectly fine for me, so I wouldn't use Cordova again. I don't see why I should. I'm just as productive there as I am with the web stuff, with the difference that I get a truly native look and feel, without having to watch performance all the time. I'm sure that, if you want to take the time, you can get perfectly well running apps. But for me, it isn't worth the trouble.
I also tried Qt and it was nice, but the app took ages to load on an actual devices (because of QML) and their licenses get more and more messed up.
- hliyan 11y ago> I wanted to have a native UI, so I tested angular-material and Polymer Aren't Web Components still heavily polyfilled in most mobile browsers? I'm wondering how much of the problem was due to the Polymer library than Cordova proper.
- andresmanz 11y agoI thought that would make sense, too. But I found them to be working OK in Chrome on Android, so I thought I could give it a try. I should have said that I wouldn't create any hybrid mobile apps anymore, not just Cordova. That's not because I don't like it - it's simply because the other options work just as good for me. At least for now - can't say anything about the future.
- hliyan 11y agoRight. > I should have said that I wouldn't create any hybrid mobile apps anymore, not just Cordova I must admit, I'm still quite enamored with them, if only for development time and maintainability. I'd rather not develop 3 different apps for desktop (browser), Android and iOS. As I said elsewhere, I'm waiting to rely on App Cache instead of Cordova in the future.
- andresmanz 11y ago> I must admit, I'm still quite enamored with them, if only for development time and maintainability. That's a very good reason for many developers. My UI code is usually rather small, with the C++ code being the biggest part. I really like C++ and Java, and Objective-C is OK. I'm pretty sure if I didn't, I would take a different route. I'm still pissed off because loading in Qt apps can take very long. Writing the apps in QML, JavaScript and C++ was a lot of fun, but I couldn't recommend anything that destroys the UX so much.
- squeaky-clean 11y ago> But I found them to be working OK in Chrome on Android, so I thought I could give it a try. They probably would have run well with the Crosswalk browser plugin, then. It's basically bundling the latest version of Chrome within your app, so all your users have a consistent and up-to-date WebView, instead of whatever the OEM decided to lock it at. Of course, that doesn't fix every issue, and adds a few more of its own. But really, any non-Crosswalk benchmarks/performances tests on Android can be simplified to: It's slow as hell.
- pjmlp 11y agoI do the same approach for my mobile OS hobby coding, between Android and WP. I guess C++ scares the web devs to go native and prefer to stay in their little sandbox. Also tried to play around with Qt, but got disappointed that their story is more about bringing C++ apps into mobile not much the license, than a full cross-platform support like Xamarin. Even the new 5.5. still requires a lot of manually wrapping code across all mobile OSes. However if I would be doing this commercially, Xamarin might be the way to go, as I wouldn't be willing to write glue code all the time.
- basch 11y agoreact canvas renders at 60fps https://github.com/Flipboard/react-canvas https://github.com/Flipboard/react-canvas