android - Should i keep a local copy of remote database? -

android - Should i keep a local copy of remote database? -

i working on application will, basically, allow people create, bring together , manage groups of other people. people within groups can message each other.

i have been wondering path better:

keep remote database information, including messages sent , users. , have app query server every time needs information. info has seen before.

keep remote database information, including messages sent , users. maintain local re-create of remote database , maintain synced remote database. whenever app needs query information, query see if local table date. if not date, updates table , runs query on local table. way maintain local re-create , app have fast queries when there not update remote table.

what done mobile applications , remote databases? would "bad practice" if did number 1?

my base of operations response maintain info in 1 place , access remotely unless there major reason maintain locally. there have extenuating circumstances mandate maintain re-create of info locally. create sure queries accurate , concise. don't pull on more info need to.however, can have subset of info kept locally. items specific user (like messages), keeping info not relevant adds overhead , bloat.

android mysql database sqlite mobile