I see this other thread about load time, but it does not seem to address my problem. My app is taking a full minute to load on Android, 25 seconds on iOS. I wonder if anyone has any ideas for me that weren’t covered in the other thread.
It seems like my load time is coming from the number of pages in my app. It has 63 pages (plus 19 pipes and services files). The app size is reasonable, 4.5MB for the .ipa, 4.3MB for the .apk. My iPhone says it is using 23MB when it is loaded, which seems good compared to other apps in the phone. If I strip the app down to 1 page (leaving in the 19 pipes and services files), I see a reasonable 5 second iOS load time, with a 3.9MB .ipa and seeing 19.3MB in the iPhone.
So I guess the app is loading or doing something with all of my pages before it starts up. If so, is there a way to lazy-load the pages or …?
I’m running 2.0.0 and I was seeing the same thing with RC4. I am using the --prod flag (though android seems to also need the --release flag). I do not have crosswalk, and there are very few image assets.
I don’t have any solution for you, but I’m wondering the same thing. Mine is quite a bit smaller at 19 pages, 4 pipes, 14 providers, 3 custom components, but it’s also pretty slow on android. Not 1 minute slow, but sluggish enough that it’s noticeable that you’re sitting there staring at a splash screen for longer than you should.
I am using crosswalk, I haven’t done any with/without comparisons, I started with it - but I think it’s supposed to help.
The --prod flag is working well with some and is not with others, which is really strange.
Mine got reduced from almost 40 sec to 2 sec using --prod flag.
I’ve the same problem since I upgrade from rc2 to 2.0.0 final, the load time has increased at least in Android, even using the --prod flag. When splash screen disappear, no even the headbar is loaded…
I don’t know if is an ionic issue or something that it’s making my app slower. I’m using the last ionic version:
Interesting, I didn’t realize that was a no-no. I’ll have to check mine for such occurrences, is there a best practice for something like that? How did you get around it?
use ngOnInit() most of the times where you think u need constructor(). keep constructor only to construct models etc. all api/service related should go ngOnInit()
I can confirm that moving a lot of stuff from the constructor to lifecycle events (particularly ngOnInit on the app.component, ionViewDidEnter for pages) made a huge difference in startup time.
Is good to check all providers that you linked in app.component constructor, because all the code inside every provider constructor loads before that your app.component code. As nylex said, is a good idea use ngOnInit() or as you say ionViewDidEnter.
hi , I am also having the same problem with loading time… i managed to make it 3.5 seconds…but the first you install the app it takes 6 seconds… 3.5 seconds is still a lot of time… does having some plugins inside platform.ready in the app.component affect loading time? for example, I have an operation (contact plugins) inside platform.ready in app.component where it gets contacts info and puts it in storage.
my point is, should I reduce such things in app.component for better loading time, or it does not really affect the loading time… Also, I didnt really get what you said about provider with a platform ready in constructor… do all code in the constructor of the pages load at once when you start the app, and if so then that is the problem i think !! I would be so grateful if you can explain more… I dont have much things in the app yet and it take 3.5 seconds after the splashscreen to load… its a disaster