Migrate Win32 #apps with complex user interfaces to #mobile apps where each screen is focused on a single task or idea.
The 90s was a time where many developers did their best to create NASA mission control screens. If an app performed ten different functions, they’d see if all those activities could be performed on a single screen. No one ever considered there might be a correlation between those complex screens and the mountain of training manuals and classroom instruction required to make employees productive. A lack of empathy for app users left many employees confused and intimidated by technology. Complexity kills.
You now have a second chance to kill this complexity. In the same way that I want you to break up your large, monolithic Win32 apps into multiple apps, I also want you to do the same for individual screens. Take a look at how many different tasks are accomplished on your complex screens and break them apart into their own screens. Once you’ve created multiple, mobile screens for each discrete function area of a complex Win32 screen, focus on which UI elements you can eliminate. You may find sub-tasks on your new mobile screens that can be further broken out into their own screens. Some designers call this Progressive Reduction. Keep iterating on this process until each screen is easy to understand and has the minimum number of UI elements needed to accomplish a single task.
Improve user productivity by breaking complex screens into multiple, simplified screens to reduce expenses and training requirements by making apps faster and easier to use. What is your company doing to make corporate apps easier to use for employees?