no need to resync permamently

[enaisoc]

1. try to sync after a delay of a minute - or 5 minutes or so, if sync fails (not permanently).
2. if there is a need to sync after the app was restarted sync then - everything else should be saved meanwhile on the mobile.
3. just sycn while app is running in foreground - there is nothing saved one the mobile and nothing to view on the mobile if the app is in background and not in use. (this is not a fancy social media app where everyone needs to get information out of the background - we would to it with pushnotifications or something like that...)

[joerx]

Hi,

the background sync was my idea. The reasoning is to sync whenever the
device is online, so the data is available when the user needs it. If used
correctly, the sync adapter should enable the platform to optimize the data
sync, possibly bundle it with other apps that need to sync, and make sure
it happens whenever a network connection is available.

So it's not about notifications or fancy social media stuff. We're just
following the recommendations by
http://developer.android.com/training/sync-adapters/index.html

The sync setting may need to be checked and maybe optimized, but please do
not disable background sync.

On Jul 29, 2014 4:28 PM, "enaisoc" notifications@github.com wrote:

1. try to sync after a delay of a minute - or 5 minutes or so, if sync
   fails (not permanently).
2. if there is a need to sync after the app was restarted sync then -
   everything else should be saved meanwhile on the mobile.
3. just sycn while app is running in foreground - there is nothing
   saved one the mobile and nothing to view on the mobile if the app is in
   background and not in use. (this is not a fancy social media app where
   everyone needs to get information out of the background - we would to it
   with pushnotifications or something like that...)

—
Reply to this email directly or view it on GitHub
#16.