(Quick mention: this is a cross-post of an issue we posted on the meteor issue tracker)
While playing with different reload-on-resume and the new Reloader - Package, I now finally found out why none of those would fix our issue: They weren’t the ones causing the reloads on every task-switch - it was the Android OS, quickly ending (destroying?) (Android lifecycle docs) the app almost immediately after switching away from it to another slightly memory intensive app (eg. “Gmail” or something similar, or another Meteor Crosswalk App), thus forcing a restart when returning to our app.
Now the thing is, I understand the need for the OS to free the memory and everything. The thing is though: We’d like to allow the user to switch away for a few seconds, eg. to copy a password from an Email or something like this, and when coming back, not having the user to fill in his username again / navigate to the right place again because the app restarted immediately.
And also we’d prefer not to do a lot of lifecycle management ourselves inside of our app, as that seems to be a whole new can of worms we wouldn’t like to get into if it’s not necessary
Is there anything we can do? Some mobile-config.js - setting we could provide perhaps, or some Cordova-API we could use for this?
Actually that’s kind of a real problem for meteor apps I start thinking now, because the reload always takes some time with Meteor Apps anyway, and if we add another few seconds for something like Reloader - it quickly could become rather painful to build something the user would like to go back and forth to for some reason or another.
The device used for testing was mainly an LG G2 (32 GB / 2 GB Ram).
Thank you for your Feedback and Ideas.