Closed sojharo closed 7 years ago
Let's do a design review of this before we work on it
I thought on this task and created a design document on how we would sync between desktop and mobile application. This is high level design and both iOS and Android needs to agree on this first before we go down into data structures. As iOS is having background restriction, therefore, I recommend that @sumairasaeed reads this design document and let me know if there is any problem. I have just put the document on google drive.
https://docs.google.com/document/d/1ZYDuyg_Uo1WcZT9HiV9OWu6_PFH4ATz5WUhj8XqBi4c/edit
@Assadbintahir FYI.
Had missed the comment. Looking at it now and will update.
I have reviewed the document and added few comments regarding where we need Voip push for iOS. As discussed, desktop app should send a Voip push to awake iOS app so it gets connected back if it was in background and then data can be transferred.
I have now completed the design document. I have taken the concerns of iOS into consideration as well.
We can create sub tasks.
I am confused on the scope or the objective of this work.
Is this task about Mobile Sync? I thought we have already implemented. I tried reading the attached document and Do not understand what problem we are trying to solve.
I have revised the document and described problem statement and objective and solution. The mobile sync with server is already implemented . This document is about how the desktop and mobile application should sync with each other. I have just revisited the mobile sync logic in document to remember how we are syncing with server and how we would sync between mobile and desktop.
https://docs.google.com/document/d/1ZYDuyg_Uo1WcZT9HiV9OWu6_PFH4ATz5WUhj8XqBi4c/edit
We will open sub tasks from design document for this task.
If mobile and desktop got disconnected for sometime then we would check to see if we need to do sync again.