Afternoon Prep 😎
Over the last few days, I turned my attention to the issues around synchronising data between devices and the different types of synchronising that might be required. Hope you guys enjoy this latest Chill Music Lab release while we take a quick look at what I mean 🙂
Data Considerations
The first category of data will be things that will basically remain online unless removed by the user (e.g. MOOV shares). This data will be somewhat limited at least initially. The second form of data will be normal sync requirements (e.g. a MOOV completed on one device needs to be passed on to other devices, like from mobile to desktop).
The third category of data transfer will involve a user transferring their data to a new device (e.g. a new mobile). In both of the latter cases, I'm currently thinking of using a separate set of tables for temporary data storage where entries will be cleared once data transfer is complete. These measures should ensure that server-side data storage load is minimised (which also helps improve user data security) and that user data is primarily stored on their own devices where their security and privacy settings can be managed directly by them. And at this stage, I believe SQLite might be the best solution for on-device storage (whether mobile devices or desktop).
All the best until we catch up again 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, links to the science and research at the core of MOOVPAD, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.