Client is updating a legacy Windows application in phases, moving toward a browser based system. The first phase is a redesign to a customer manager where users update and delete customer information. This customer manager is currently used by all existing system workflows.
What they want is that when another process requires the customer manager, it will launch a web browser version where the user can input the information. Once complete the information, and user, will flow back to the desktop application to continue the process.
An example of this might be:
- User creates a new customer bank account in the windows shell.
- When creating a customer, the windows shell launches customer manager in the browser.
- User creates the customer information in the browser
- When the customer information is saved the system launches the windows shell application sharing the customer information and the bank account process continues.
Obviously the user experience is impacted since this is a move away from a unified interface.
Does anyone have experience/insights/tips they can share on improving the experience in non-unified systems, specifically workflows between desktop and browser applications?