Why The Structure Matters
So let's take the UI screen on the left for example, with the pre-exercise screening questions for users of the MOOVPAD Web App. If the user enters the details and then has to wait too long for this information to be uploaded, then the user experience is diminished. The same applies for retrieving the data from the database at any point in the future of course.
And so as I'm building the UI screens, I'm also going through and making sure that the relevant API's are structured correctly, and that the database linked to that API is also properly designed. All of this then needs to be linked back to the MOOVPAD management system so that all of this activity can be monitored to keep things flowing through the processes smoothly. That's why the work on the new version of the MOOVPAD Web App UI screens is taking a bit longer than the previous version.
And also why I am no longer arguing with my insanity 🙂
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.