Comparison – SAP Fiori UI5 and Screen Personas : The Good, The Bad, and The Ugly
SAP provides two paths to a delightful user experience (UX)
SAP Fiori UI5 apps and SAP Screen Personas are two ways to achieve SAP Fiori user experience.
- Fiori UI5 UX strategy aims to transform the transactional operational model to a role-oriented one
- SAP Screen Personas simplifies scenarios not yet covered by Fiori applications or for your custom transactions
UI v/s UX
There is a distinction between User Interface (UI) and User experience (UX).
User interface deals with intuitive screen design, screen flow, buttons and colors.
User experience deals with how users feel when they interact with the technology. It includes integration between processes, people and technology
- Intuitive screen design to call a ride from your mobile phone > Great UI
- You can walk out of your ride without using your mobile phone > Great UX
SAP provided technologies (Fiori UI5, Personas) can be used to improve UI for screens as part of organization’s UX improvement initiative. Here is a perspective of each technology.
1. Fiori UI5 apps:
- Role based development
- Develop once, use on any device i.e. Mobile phone, tablet and desktop
- Develop based on your need (independent of existing SAP transactions)
- Leverage SAP Fiori Launchpad to personalize landing screen
- Fiori design is the future UI for all SAP products
- Dynamic search functionality
- Smart tiles with analytical annotation
- High cost of development
- Different approach for development compared to traditional development (Design thinking)
- Need to provide complete “end to end functionality” for designated roles otherwise users end up in two different user interface (Fiori and SAP GUI)
- High cost of change (develop once and develop right)
- Easy to deviate from SAP’s Fiori design guidelines
Great for complex business processes, high development cost, great UX improvement, long term approach aligned with SAP’s UX strategy
2. Screen Personas
- Modify existing transactions (standard and custom) > Keep existing business logic
- Easy to simplify > remove fields
- Relatively easy to beautify screens by applying themes
- Great for simplifying display transactions
- Can be integrated with Fiori Launchpad
- Limited to SAP GUI transactions (Very difficult to combine different edit transactions on one screen > It gets ugly pretty fast)
- Limited to fixed screen-size per theme (You need to create flavors for every screen size. Development time multiplies with every flavor)
- Every transaction needs flavor (i.e. Three flavors for MM01, MM02 and MM03). Multiple flavors if you are creating different variants for different users groups
- For edit transactions it gets ugly to merge fields from multiple tabs esp. grids
- It gets even uglier if you have mandatory fields on different tabs
- Numbers of scripts and flavors can get out of hand very quickly
- Screen can look like Fiori screen but will not provide intuitive fluid UI functionality available in Fiori UI5 screens
Great for simple transactions and linear business processes, limited development effort, limited UX improvement gain.
3. Hybrid approach:
Improve UX by implementing Fiori UI5 and SAP Screen Personas
- The man who chases two rabbits, catches neither. ~ Confucius
- If you “the organization” want to chase two rabbits, setup two different teams and send them to chase one rabbit each ~ Confucius 3.0
Also posted at : https://experience.sap.com/topic/perspective-two-paths-to-a-delightful-user-experience-ux/
Rajan - good post -- a couple of observations on the "Bad" of Fiori:
Peter Brasket, Mindset Consulting
Hello Rajan, Good post . I liked the chasing rabbits comparison .
Thanks for the update Clemens.
I have updated the article with this text: "One can also create flavors in SAP GUI for HTML and render in SAP GUI for Windows. Limitations are noted here: https://launchpad.support.sap.com/#/notes/0002080071"