Optimize sync time for Intial Payload
Budget: $30 – $250 USD
When the app user logs in for the first time it can take anywhere between 15mins to 60mins for the user to start using the app.
First time login on app install or reinstall involves following steps with approximate time required to perform the step,
Data1 from a .csv file with about 70K rows, is read and stored in Core Data (Approx. time – 2 mins)
Data2 are read from FM Database and stored in Core Data (Approx. time – 2 mins)
Request is sent to the API to download the initial payload (Approx. time – 1 to 2 mins)
Response payload is stored in Core Data (Anywhere from 5mins to 50mins)
Other problems, if the initial payload in #4 above is too big to handle the app might crash or freeze for few mins. If the app crashes we have to reduce payload size from the backend. If the app freezes, then closing and opening the app resolves the issue.
For offline storage we use Core Data with SQLite
First time login on app install or reinstall involves following steps with approximate time required to perform the step,
Data1 from a .csv file with about 70K rows, is read and stored in Core Data (Approx. time – 2 mins)
Data2 are read from FM Database and stored in Core Data (Approx. time – 2 mins)
Request is sent to the API to download the initial payload (Approx. time – 1 to 2 mins)
Response payload is stored in Core Data (Anywhere from 5mins to 50mins)
Other problems, if the initial payload in #4 above is too big to handle the app might crash or freeze for few mins. If the app crashes we have to reduce payload size from the backend. If the app freezes, then closing and opening the app resolves the issue.
For offline storage we use Core Data with SQLite