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?

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?