In-App Interfaces & Repos
The main difference between the work I've done today on the core MOOVPAD WebAPI template project and previous webAPIs has got to be the implementation of the repository pattern and interfaces (refer to the larger screenshot below). This style is actually a requirement for the MOOVPAD Mobile app, but this isn't necessarily a strict requirement in general.
However by implementing this style of data parsing within the core webAPI template, it will make all future work standardised and easier to implement when its time to build the mobile apps. Next up: data validation within the webAPI, to reinforce validation techniques that are applied at the UI level to ensure that only appropriate data reaches the webAPIs and avoid some of the more common attack vectors.
Phew... time for a break, yeah? 🙂
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.