Hardcoded vs Downloadable
With all of the focus lately on the MOOVPAD server-side systems, it has been a while since I updated the Blog regarding the progress on the apps themselves and planned work ahead. I've been weighing up the option of introducing the template MOOVs that will be available to general users as downloadable content pulled from a database, rather than hardcoding these into the MOOVPAD apps.
The reasoning for hardcoding these initially was to have this content installed locally on the user devices during setup, thereby reducing the need for large downloads. However I've since learned more about just how much data will be pulled from the wide range of databases through normal app use. And in-light of that, the relatively small amount of data that is required to build these template MOOVs should not pose too much of a problem. This approach also allows general users to download and store only the MOOVs they want, rather than having to deal with content they don't need or won't use.
It also allows MOOVPAD the flexibility to continue expanding the library as time goes on. There will also be the option for general users to customise their own MOOVs and store those locally on their devices, and for MOOVPAD Pro users to build their own as well. Since MOOVs and the training aspects of the apps are obviously the main focus, these levels of flexibility will remain important.
The work... it never ends dammit 🙂
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.