Revisited from the Foresaw archive. The argument and structure have been updated for this edition.
Mobile access can make business systems useful closer to the work: receiving goods, checking an order, or approving a request away from a desk. But exposing the desktop interface on a phone rarely produces a good mobile experience.
The strongest starting point is a specific task with a clear reason to happen on a mobile device.
Choose the workflow before the screen
Ask what the person needs to accomplish, what information they already have, and what interrupts the task. A warehouse receipt and an invoice approval have different requirements even when both update the same ERP.
Keep the mobile path focused. Show the context needed for the decision, make the action explicit, and confirm the result in language the user understands.
Be honest about connectivity
If the workflow must tolerate a weak connection, decide what can be read or changed offline. Cached information needs a visible freshness state. Changes waiting to synchronize need an equally clear status.
Conflicts are a product decision as well as a technical one. Define what happens when two users update the same record before relying on background synchronization.
Preserve the system’s boundaries
Mobile convenience should not create a second set of permissions or business rules. Keep authorization and validation aligned with the underlying system. Minimize the sensitive information stored on the device.
Test in the place of use
Try the workflow on the devices and connections people actually use. Watch the complete task, including mistakes and recovery. A successful mobile integration makes the work easier while keeping its state understandable.
Adapted from “Achieving Mobile Accessibility in ERP Integrations.”
First published on Foresaw. Reworked for this edition.