Pillar · Digital Commerce, Apps & Experience
Enterprise Apps, Fiori & Mobile
Applications for customers and staff, cleanly separated from the logic they sit on.
What is at stake for the CIO
An app that knows its own rules becomes a second core — only without governance, without transports and without anyone operating it at night. Separating interface, business logic and backend is therefore not a matter of taste but the condition under which frontends are allowed to stay fast.
The question behind it
How does the interface stay agile without business logic migrating into it?
- 1Identity and role
- 2API contract
- 3Business logic in the backend
- 4Interface
Systems and processes
- Customer-facing and employee-facing applications
- Mobile store and retail processes
- SAP Fiori and UI5
- Extensions on SAP BTP
- API-based connection to backend systems
- Roles, authorisations, device context and identity, including Entra
- Offline capability and operational safety
Decisions that go wrong most often
- Authorisations are cut by screen rather than by task and grow uncontrolled.
- The app is given direct database access because the interface is not ready yet.
- Mobile processes are designed for the ideal case, not for the store with poor wifi.
- Identity is connected late and then retroactively dictates the role model.
Decisions FirstRetail prepares
- 1Which logic stays in the backend, which belongs in an extension, which may live in the interface.
- 2How roles, authorisations and device context are designed as one model.
- 3Which processes must work offline, and what happens to them afterwards.
- 4How Fiori applications and bespoke apps share one integration layer.
Where the experience comes from
Current architecture work on mobile Fiori and UI5 applications, with SAP BTP and Entra in a live programme context. Product and engineering leadership across distributed teams in Geneva, Lisbon and Cluj, covering UX/UI, development, testing and deployment.
Every name here stands for historical delivery experience from completed programmes. None of them is an endorsement or an indication of a current client relationship. I do not display logos; that would need a permission I do not have.
Other fields in this pillar
Commerce & Omnichannel
Online and store as one business — with one truth for product, price, availability and order.
CRM, Customer Service & Contact Center
One customer view across brands, countries and channels — and a service case that knows the order.
Digital Product & Platform Leadership
Platform rather than point solution — with roadmap, release governance and teams that deliver.