I could not find information on this particular problem anywhere, although I know there are many questions and sqlite documentation, so sorry if this is a duplicate.
In any case, I am developing an application that registers the user and performs actions in the mysql database on my website through php scripts. But so that the user does not have to wait for a response on the network for each button, they press / each start of activity, I have a sqlite database attached to the application that stores live information when using the application (it uses GPS tracking so this data is saved as well as other things).
I suppose my question is: how much should I store locally for download later? Should I try to do everything locally after the user's initial login and just load / sync the data in the onPause () user profile or something else and use the life cycle? Or should I do the opposite and try to do everything live and completely get rid of the local sqlite database?
It’s just interesting if anyone has experience in such a situation and what conclusions they came to.
Thank you for your time,
Infinitifizz
source
share