Sharing our implementation of an offline-first mobile learning platform for Workday that handles training completion tracking even without connectivity. Built using Workday Mobile framework with SQLite local storage and custom sync engine.
Architecture centers on offline-first design where all user interactions write to local SQLite database first. Implemented bidirectional sync engine that queues changes and reconciles with Workday REST API when connectivity returns. Key challenge was conflict resolution when same training record modified offline by user and online by admin.
Sync engine uses timestamp-based conflict detection with configurable resolution strategies. Training completion data syncs via Workday Learning API endpoints with retry logic and exponential backoff. Local SQLite schema mirrors core Workday learning objects with additional sync metadata columns.
Platform now supports 3,200 field workers completing mandatory training during site visits. Average sync time under 8 seconds for typical session. Conflict rate stayed below 2% with automated resolution handling 94% of cases.
How did you handle the conflict resolution strategies? We’ve struggled with this in other mobile implementations. Did you implement server-wins, client-wins, or something more sophisticated? And how do you surface conflicts that need manual intervention to users?
This is exactly what we need for our remote workforce. What REST API endpoints did you use for the sync operations? We’re evaluating whether to build custom or use Workday Mobile SDK capabilities. Also curious about your SQLite schema design decisions.
Critical question. For our implementation we used SQLCipher for transparent database encryption with AES-256. Encryption key derived from device keystore and user authentication token. Also implemented automatic database purge after 30 days of inactivity and immediate wipe on device unenrollment from MDM.
Additionally, local database only stores training metadata and completion status, never actual training content for sensitive materials. Content streams from Workday when online or caches temporarily in encrypted app sandbox with automatic expiration. PII in completion records limited to worker ID reference rather than full profile data.