How MTMT Can Help
While the screenshot to the left shows the 8s load time for the full calendar UI Interop object in memory (shared earlier today), the two screenshots below show that this time is reduced to less than 2s if the calendar interop object is loaded up the the level of the 24hrs in each day, and just a couple of hundred milliseconds if loading just the days in each month.
So the MTMT can help this process by allowing the initial loading of the days when the app initially loads, and then the hours while the user enters login details, and finally the four slots per hour in each day while the user progresses with their usual activities with the app. And these can also be loaded only when needed, based on, for example, the user's MOOV program data, thereby streamlining the process even further.
And as for that one person out there who worked this out and understood what the MTMT did, ruining the suspense and showing me up for being my true "mid" self...
vendettttaaaaaaaa 🙂
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.