Concept card

SAP Analytics Cloud Mobile

As of 2026-07-23

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP Analytics Cloud Mobile?

SAC Mobile only renders usefully if a Story was explicitly designed 'optimised for mobile' with its own layout — a desktop Story with 20 charts in a 4-column grid still loads on a phone, just illegibly.

What it is

SAP Analytics Cloud Mobile is the native iOS and Android client for SAC — the surface that lets executives and field operators consume Stories on their phone or tablet without launching a browser. It is not a separate product; it is the same SAC content rendered for a mobile form factor with mobile-specific affordances (offline cache, push notifications, biometric auth, Touch ID / Face ID).

What actually works on mobile and what doesn't: SAC Mobile renders Stories, but only Stories that were designed responsively. A desktop-only Story with 20 charts in a 4-column grid does not render usefully on a phone; it renders, but the chart text is unreadable. The Story designer must choose 'optimised for mobile' at design time and then provide a mobile-specific layout that reorganises the canvas for the small screen. Stories that lack a mobile layout still render but with a generic phone view that nobody uses twice.

Why it matters

Offline caching, push notifications, and biometric auth exist for executives on planes or field operators away from a desk, not for desk-bound analysts.
Analytic Applications need explicit `isPhoneScreen` checks in scripting to adapt widget visibility — mobile support isn't automatic even for interactive apps.
Design for mobile only when the audience opens dashboards more than twice a week — otherwise the investment in a mobile layout isn't worth it.

Key points

Same SAC content rendered for mobile — Stories require an explicit mobile layout at design time, otherwise a generic phone view nobody uses twice.
Offline cache — recently-viewed Stories available without connectivity; the plane / warehouse / field use case.
Push notifications — KPI threshold alerts and Story-update notifications without polling.
Biometric auth (Touch ID, Face ID, fingerprint) — replaces password entry per session.
Analytic Applications work on mobile but require `isPhoneScreen()` checks in scripting to adapt widget visibility.
SAP Analytics Cloud Mobile is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.

Terms used on this page

Mobile layout: A SAC Story canvas variant designed specifically for the phone form factor — fewer widgets, larger fonts, vertically stacked rather than grid-laid; the difference between a Story that renders on mobile and one that is actually used on mobile.
Offline cache: SAC Mobile's local store of recently-viewed Stories; lets users consult dashboards without connectivity; cache age limit governed by the SAC tenant administrator.
Push notification: An OS-level alert delivered to the user's device when a SAC KPI threshold is crossed or a subscribed Story is updated; opt-in per Story and per user.
isPhoneScreen(): The SAC scripting API helper that returns true on a phone form factor; lets Analytic Application scripts adapt widget visibility, layout, and behaviour to small screens.
Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.

SAP Analytics Cloud Dashboard Design: The Rules