Mobile Apps & Remote Data
I finally managed to find a learning resource that relates to the same scenario as that being used in the MOOVPAD Mobile App to link the app to a remote SQL server. And I'm very glad I did for many reasons. Not only is the required approach something I would never have reached on my own, but it also introduced some important code that will be useful for other functions and features later.
So the screenshots here show the relatively simple example of developing a model for a data object in the MOOVPAD webAPI, then the interface object, followed by the "concrete" object that calls on the actual data handling methods of the controller in the webAPI, and then finally registering the interface object on the MainPage. Of course I now need to develop a lot more objects to be able to link to the other controllers and tables for all the data in the webAPI. But I now have a good starting point to guide the rest of the development process.
And with all of that now sorted, happy face 🙂
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.