Central cloud system has different master data sets with different Expected Time to Live (ETL). Synchronizing these data between mobile devices and cloud could not handle with traditional sequential methods of data synchronization. To handle this requirement in a more effective and efficient manner, a special caching methodology was introduced. Further a background and on-demand data synchronization capabilities were introduced to enhance the usability of the apps.
Additional measures were taken to track application activities. Popular analytics frameworks were not an option as these applications should work on local area networks (LANs). Developers implemented activity tracking, logging and transmitting modules to investigate user behaviour within the application.
iCloud platform usually get deployed to multiple different private clouds. Each cloud could have its own version of iCloud to handle site specific solution requirements. These differences could be additional or less attributes for an entity or an attribute being required or being optional based on the business case. Even with these variations, it was required to use a single mobile app to handle all different versions of the cloud app. This introduced significant challenges in implementation of the solution and even serious challenges when it comes to quality assuring and commissioning apps for production use. Additional type checking and exception handling in the code and use of web service API tools to detect differences in data outputs from Web APIs help the delivery team to establish the reliability of the applications.