Process Timings & MTMT
I've been going over the loading times for the calendar control in the MOOVPAD Web App. It's important to remember that the conditions for the downloadable versions for desktop and mobile devices are very different, since the processes aren't restricted to a single thread on those platforms. The main screenshot below shows some of these timings to the left.
The most important ones are the second and third times, with an approximate 8s between them. While making changes to the UI Interop layer objects to optimise them for the other versions (meaning that the UI for the web app now also needs updates - see the code in the screenshot to the right, for explanation of missing day images in the main screenshot), I've been keeping an eye on how these changes impact the loading of the calendar UI Interop object in memory, and how this might impact performance on devices with slower processors. Using the main-thread multi-tasking (MTMT) approach I developed around 18 months ago should hopefully reduce these times, but I'll need to hook the current version up to the old API to start testing this later (user session needs to be created after login, and other processes launching, etc).
I can hear my mentals yelling at me 🙂
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.