TechEd recap of SAP's mobile strategy + my critical view

20
TechEd recap of SAP's mobile strategy + my critical view dr. Tamas Szirtes Director Innovation & Technology SOA People NL

Transcript of TechEd recap of SAP's mobile strategy + my critical view

Page 1: TechEd recap of SAP's mobile strategy + my critical view

TechEd recap of

SAP's mobile strategy

+ my critical view

dr. Tamas Szirtes

Director Innovation & Technology

SOA People NL

Page 2: TechEd recap of SAP's mobile strategy + my critical view
Page 3: TechEd recap of SAP's mobile strategy + my critical view

SAP Build

Page 4: TechEd recap of SAP's mobile strategy + my critical view

SAP Build

Page 5: TechEd recap of SAP's mobile strategy + my critical view
Page 6: TechEd recap of SAP's mobile strategy + my critical view
Page 7: TechEd recap of SAP's mobile strategy + my critical view
Page 8: TechEd recap of SAP's mobile strategy + my critical view

Previously called SAP Enterprise App Modeler

Page 9: TechEd recap of SAP's mobile strategy + my critical view
Page 10: TechEd recap of SAP's mobile strategy + my critical view
Page 11: TechEd recap of SAP's mobile strategy + my critical view
Page 12: TechEd recap of SAP's mobile strategy + my critical view
Page 13: TechEd recap of SAP's mobile strategy + my critical view
Page 14: TechEd recap of SAP's mobile strategy + my critical view
Page 15: TechEd recap of SAP's mobile strategy + my critical view
Page 16: TechEd recap of SAP's mobile strategy + my critical view
Page 17: TechEd recap of SAP's mobile strategy + my critical view

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

Page 18: TechEd recap of SAP's mobile strategy + my critical view

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

Page 19: TechEd recap of SAP's mobile strategy + my critical view

Q&A

Page 20: TechEd recap of SAP's mobile strategy + my critical view

THANK YOU

www.soapeople.com | [email protected]

t:

m:

e:

dr. Tamas Szirtes

Director Innovation & Technology SOA People NL

m : +31621106317

e : [email protected]

t : @tamas_szirtes