TechEd recap of
SAP's mobile strategy
+ my critical view
dr. Tamas Szirtes
Director Innovation & Technology
SOA People NL
SAP Build
SAP Build
Previously called SAP Enterprise App Modeler
TechnologyNative Native (metadata) Hybrid Web
Pros • Ultimate performance
• Ultimate UX
• Direct access to
peripherals
• Strong security
• Less expensive
• Only one technology to
learn as a developer
• Updates of the apps
are possible
• Design once deploy
many
• Massive development
community
• Large device support
• Updates can be pushed
into the app
• Updates are immediate
• Very large device
compatibility
• Massive development
community
• Low cost
Cons • Expensive to support
multiple platforms
• Specialized skills
• Rewrite for each device
type (not iOS)
• Updates require
redeploy
• Managing multiple
versions of the app
• Innovations can’t be
used immediately
• Suboptimal UX
• Updates of plugins
have to be managed
• Limited offline app
caching capabilities
• No built-in quality
assurance
• Limited access to some
peripherals
• No app store access
• Security
Good use case • UX very important
• Device specific design
• Process intensive apps
• Complex offline apps
• Complex apps with
multiple screens
• Lightweight workflow
apps
• Fiori-based apps
• B2C business apps
• Mobile version of
existing web content
• Lightweight apps
Bad use case • B2C oriented (cost) • Heavy process driven
apps with offline
requirements
• Apps heavy on CPU
• Apps requiring access
to peripherals
• Apps heavy on CPU
• Apps starting offline
The critical view
Write once deploy anywhere
• Desktop
• Tablet
• Smartphone
• All major browsers and
operating systems
My dream Current SAP strategy
Write UI5/Fiori for desktop
Write iOS in SAP CP SDK for
iOS
Write Android in Mobile Platform
SDK
Q&A
THANK YOU
www.soapeople.com | [email protected]
t:
m:
e:
dr. Tamas Szirtes
Director Innovation & Technology SOA People NL
m : +31621106317
t : @tamas_szirtes