Why Calendar Control Matters
I thought I should explain why I'm taking so much time to develop the calendar control for MOOVPAD Apps, since I believe it will likely take longer than originally planned to get this built right. In short, the main take-away idea is client-side processing focus. Here's the general idea... the MOOVPAD apps will use key pillars to help focus as much processing as possible on the client-side.
Examples of those already well established in the code are session and user contexts. Each of these will enable the storage and processing of relevant data on the client device once retrieved from the servers. This helps minimise the amount of data actually stored in databases, alleviating some of the load there long-term. It also helps speed up data processing to improve UX. And the calendar control will further help achieve this goal by providing links to all the important information in a coordinated (date-relative) way.
I've already developed the basic elements of this UI Interop class over the past couple of days. But the reason I'm spending more time than originally planned on developing this set of objects is to avoid re-work later, and to ensure that it works well for all the MOOVPAD general and pro user apps. And that's quite a big ask, given the different operating contexts of each app and user type.
Or I'm just making excuses. Whatevs lol 🙂
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.