Working 😎
Just about to get started with some coding soon, and thought it was a good opportunity to address some points that were mentioned a while ago regarding limiting some functions of the online-only version of the MOOVPAD apps and the reasons for these. So here's one of those awesome Chill Music Lab vibes for us all to enjoy while we take a look 🙂
Why Limit Features?
In some cases where MOOVPAD Web App features are limited, it's a matter of policy choice for things like user privacy, cost effectiveness (especially during the early stages), and app security. For example, the minimisation of data stored about users, or the planned limits around messaging storage, as well as the use of a single page to contain all the session code.
There are also situations where practical/technical limits are the cause. Examples of these include the manual entry of parameters during the testing phase and for educational purposes, limitations on how much data can be collected from wearables due to API restrictions with web apps generally, as well as other development issues centred around development time and potential security risks for users (seen with other apps and devices) that MOOVPAD will work to avoid wherever possible.
So as we can see, there are quite a few reasons why some functions may be limited initially, with other limits planned to be part of standard practice for MOOVPAD apps.
Have a great day ahead, and catch up again soon 🙂
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.
