In the mean time, i’m not using ionic anymore, i was almost able to jump to my implementation as a whole. I need to fix some virtual scroll stuff of mine (which has got two way scrolling and variable item height feature as default - server data decides, whether the feature will be activated automatically, no configuration), and drop the non-used ionic.
I have measured frequently the size of my app. I was coming from 2,5MB js size (minified --prod, i have checked what is causing it also with source-map-explorer). Unfortunately if you have big templates it’s increasing the size drastically (and the performance of your app is going down at first load - it seems to me similar how the jsp is working - load when it’s needed, at that time my dynamic form was frozen, second load time it was smooth - i have removed half of my template with more dynamic stuff, and voala, everything is smooth), so i’m not using the form and http from angular, i have some dynamic sophisticated one. I have used sprites, so it’s reduced the icon size and speed up the performance a lot.
Ionic has 400KB css minified even if you are not using them. My app now is about 800KB js, and some kb css.
Removing ionic, and reconfigure the angular (many times i had to use Renderer2 to hijack the angular 2, so a virtual dom system might be better for my expectations), i expect that my app is going to below 300KB + 100KB images. (we are not talking about user added photos, which is also controlled on upload, so i’m not saving the original image)
If i’m jumping to inferno instead of angular, at least i prepared for that scenario, i probably end up 100KB which is containing more advanced features than the ionic now. (not just virtual scroll and toggle with two handles)
I have announced that i will share the code in the past, but my app seems to me 95% reusable, so at the end i’m hesitating, probably not sharing the end result, until my app does not get traction.
I hadn’t that much problem with the images, as i had an approach in my mind, don’t go app store before test everything, so i’m asking the user first to add me to the home screen. (so i have time to bug fix, before i’m going to app store tedious procedure)
To be honest, as it’s a hybrid app, the main bottle neck not the size of apk, the main bottle neck is the size of your webpage. I think what i have done it’s a one year evolution, i have learnt a lot from ionic and angular, how to create my own system, but to use that technologies is a nightmare. Angular hasn’t got mature ideas, just some collection of ideas, and it’s just transforming always, and causing bugs.