IMHO that's the best approach to, but this approach has some problem.

1) The task have a ID. It's created by server. What ID should be created on device? We create 2 ids? One local and other for server?

2) How do I know the task is not synchronized? Use a new field timestamp?

3) If i change task on my device and you change same task on your device or on server. What do we do?

-- 
Daniel Passos

On Friday, September 7, 2012 at 5:54 AM, Marko Strukelj wrote:

For a mobile application it's definitely better to try and be as independent of the server as possible. Also you normally want to save all the user input immediately, as user may switch to another task and then return to the app - which has to appear in the same state user left it, even though an OS maybe shut down app's process, and started it afresh later. The need to save data locally is therefore inevitable for good user experience - I would even call it reliability.

This all goes in favor of 'save locally, and sync to the server' approach. And you also need to sync from the server to learn about tasks created via other devices. Local storage should be considered a cache of server side data + some locally created data that has not yet been synced to server. And there may of course be some data that specifically relates to client device and doesn't have to be stored on the server - like application settings maybe ...

IMHO that's the best approach to this type of application.

- marko


----- Original Message -----


Hi Guys


I'm working on a little poc of Android TODO project. I'm Thinking
about save and sync tasks on mobile apps. Which best approach? Save
all tasks local and sync them of server?


What approach you used in iOS TODO project? What you think about sync
tasks?




Att,
Daniel Passos