Deployed Data Structure & API's
Although basic data structures have been built for local device storage for MOOVPAD users, needed to progress with the app development so far, the picture changes completely when looking at remote data storage on distributed servers with many webAPI's and databases. Not only do the data structures and API's change, but processes too.
MOOVPAD apps will aim to store as much of the data as possible on user devices (e.g. using SQLite), but there will still be a huge amount of data stored temporarily (e.g. for user-initiated data sync operations) as well as long term (e.g. publicly shared data for social and/or business functions, research-related data. etc) on MOOVPAD servers.
Meanwhile, I am no longer certain I am not in nerd hell 🙂
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, 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.