Designing With R&D: Offline, Sync, and the Legacy Constraint

In enterprise mobile, the hardest design decisions are engineering decisions — which is why I bring R&D in early, not at handoff. When I design for field employees, Offline Mode isn't a feature toggle; it's an architecture commitment with conflict resolution, sync queues and stale-data rules baked in. A CTO shouldn't learn about that from a finished mockup. I work the way that respects your constraints. The legacy HR and payroll integrations have rules I don't get to wish away — sync windows, record locks, fields that can't change. So I co-design the data model and the offline contract with your engineers before I polish a single screen. We agree on what a 'pending' state means, what happens when a clock-in syncs late, how the camera and GPS payloads degrade gracefully. This keeps design honest and estimates real. Your team isn't reverse-engineering intent or absorbing scope creep disguised as 'just a small interaction.' You get designs that map to feasible architecture, with the expensive edge cases — conflict, latency, partial sync — already decided together. Collaboration up front is cheaper than rework after sprint planning.