I’m really sorry to start this topic anyway. But in the moment I’m quite lost. Everything started so promising…
Back in late '15, I was looking for a cross platform framework, basically for Android and Windows. iOS is 2. prio. I never liked the idea of writing a two natives apps for Android and Windows, one in Java, one in C++ (maybe Java as well) - on top I don’t like Java.
First tests with ionic 1 were good, but not amazing. So I took the early ionic 2 and Angular 2. That seemed to be the way to go! 2016 passed. My playground app got bigger, refactored multiple times due to Angular/Ionic changes and here we are:
Actual starting time is about 10 seconds with crosswalk on a Moto G2. Production built. All optimizations done. But startup time is a key to my app. Up to 10 sec are a complete no go! Plus a lot of other unsolved issues like keyboard handling, virtual scroll issues, unsnappy button handling etc.
After every release I --prod --aot --fulloptimize built the conference app for Android and put it on my phone. Startup times got worse over the time - not better.
Ionic team did a lot of work to use tree shaking to get the application size small. But at the end of the day tree shaking just removes dead/unused code. Good for a “hello world”, but if the app gets little more complex and uses more parts of the framework, tree shaking might not bring the desired effects, IMHO.
As discussed in the final 2.0.0 annoncement thread I am really concerned now about using the right framework for the next years. In the end of 2016 all framework developers seems to have other tasks. There’s just Brandy who fixes issues, but in the last two month I couldn’t notice any significant progress. What about Adam and Manu or even other developers?
I totally understand that Ionic is a company which has to earn money and has to invent tools, services and ecosytem around the framework. So the framework is the core. But the framework has too many issues right now - at least for me.
I started evaluating other frameworks on Cordova like Framework7 with vue.js. Startup time is about 1(!) second. Everthing in the demo app is snappy - so it’s not about Cordova or crosswalk or the phone.
Next is an Onsen UI evaluation. (But I still like ionic most).
@mhartington can you please explain a litte more, what’s going on behind the scenes? Is @brandyshea really the only framework developer right now?
Will there be significant progress again on https://github.com/driftyco/ionic ?
This is important to get an impression what can be expected from ionic 2 this year.
Is someone out there with me? What alternatives did you try? Which way do you go?