Gaining user adoption for your mobile apps integrating with JD Edwards can be challenging. Users tend to be very demanding in terms of the number of screens, navigation steps and the density of information. On the other hand, they are seeking cycles of interaction that provide feedback. Designing apps with appealing feedback loops can be a challenge. Here are a few of the issues you need to consider when designing your mobile app that integrates with Oracle JD Edwards ERP systems:
Design Style. Consider using a modern design style. Flat design and material design are currently in vogue with Apple iOS and Google Android users respectively. While some suggest a hybrid between the two, I think those may simply be people who think its necessary to use a single skin approach. Personally, I see no reason not to design apps specifically for each platform.
Responsive Design. Regardless of the style, skins or templates you adopt, your design needs to be responsive and adaptive to the device being used by the app consumer. If the app is viewed in a browser, browser windows can also change in size and aspect ratios. But even when an app is designed for native app containers, the app needs to be responsive to the many various device sizes and resolutions.
Form and Function. The old adage that form follows function is expressed differently by today’s UX designers. Apple calls it “aesthetic integrity.” It is basically the idea that the interactions need to be true to the purpose of the app.
Editability. If users want to change what they see and that is intended by the app, then direct manipulation ought to be allowed. This extends beyond text field editing to include gestures that allow for rotating, scaling, moving and sliding.
Native integrity. The user interface ought to be aligned with the expectations of the users community for the device and the app. Things ought to work the way people expect them to. Don’t reinvent the wheel.
For Full Story, Please click here.