Fiori Fundamentals & UX Strategy

A customer assumes SAP intends to eventually deliver every old transaction as a brand-new Fiori app. Which two of the four UX-strategy pillars show that's the wrong mental model — and what do customers do for screens that fall outside SAP's scope?

A team running fact sheet apps proposes a HANA-only (XS) landscape with no ABAP stack to keep it lightweight. Why does that break, and which half of the requirement does the HANA database alone NOT cover?

When a transactional Fiori app creates or approves a document, which server does the browser actually call, and over what protocol — and what's the common mistake about that endpoint?

A colleague says fact sheet apps are only reachable from launchpad search results. Which other launch entry points disprove that — and what design idea do they reveal about fact sheets?

A stakeholder asks to "buy and install the Fiori product." Why is that framing wrong, and what does treating Fiori as a paradigm (rather than a product) imply for adoption?

Which three perspectives must intersect for true design innovation, and what does omitting any one produce?

An architect plans classic analytical Fiori apps on a non-HANA Business Suite, reading KPIs straight off the transactional tables. What two things are wrong with that plan?

A user needs a complete 360° context view of a single business partner and then wants to jump to its related objects — which classic app type is that, and why not a transactional app?

Management pushes back: "nicer screens are a soft benefit, not a budget line." Which UX payoffs are framed in hard business terms, and which one matters most when adoption is the bottleneck?

On the ABAP front-end server, the transactional UI layer splits into product-specific and infrastructure components. Which group provides OData enablement, and why does losing that infrastructure group break every app, not just one?

A team on classic SAP Business Suite assumes Fiori 2.0 (with the viewport and renewed design) is reserved for S/4HANA. Are they right — and what's the practical takeaway?

Someone cites SAP Fiori's 2013 launch as proof it was a mature, broad app suite from day one. What does the initial release actually tell you, and why does that history matter for managing expectations today?

A project on a non-HANA Business Suite is told "Fiori needs HANA, so it's off the table." Is that true for all three classic app types, and what's the catch even where HANA isn't mandatory?

An interviewer asks you to classify an S/4HANA app as "transactional, fact sheet, or analytical." Why is that question a trap, and what replaced the fact sheet pattern?