4 ms·

I 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 wou

I 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 ago
Right. > 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.

hliyan 11y ago

Right. > 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.