Fiori Key Principle and what they mean in custom development
Since its inception, a lot of changed in Fiori but its key principle for design has always remain the same. By now, most are aware of them and they are as follows:
What they really mean in custom app development.
Role Based: Quite simply, do not try to mimic SAP transactions. Create separate app for different roles. Example – if there is a requirement that some fields should appear in the app for a specific role, then perhaps it is better be a different app.
Simple: Show the data only what is necessary and it is needed. If a rare business scenario in a requirement is adding a lot of complexity in design and a way around exist (for example GUI transaction), then perhaps the app can skip that business scenario.
Coherent: Try to use Fiori Template and Fiori Element as much as possible especially with S4. S4 has a lot of standard apps which users are going to use and if the custom apps look and feel the same as standard then it will be easier for user to learn.
Delightful: The app should show correct and short messages. The app should fail graciously in case of exceptions and should always focus on the most important or most used business scenario.
This is just a brief description and much can be written about it. What do you think about these principles. Are they just words or something which really drive your design. Please share your thoughts in the comment section.
