Here‘sSAP‘s mobile portfolioat a high level. Blue indicates 3rd party/partnercomponents. Together with our ecosystem of partners, wedeliver innovative mobile appsthatspeedandtransformyourbusiness. Weprovide a mobile platformthatallowscompaniestocreate, extendandpersonalize mobile appssecurelyandcost-effectively. Wepartner with youtomobilizeyourbusiness, providingtheknowledgeandexpertisetoensure a clearpathtosuccess.
This is the why do you need the platform slide?Developer productivity – SDKs, tools, reusable components, flexibility in tools/frameworksIT manageability – enterprise services (debugging, tracing, policies, life cycle)
This is the why do you need the platform slide?Developer productivity – SDKs, tools, reusable components, flexibility in tools/frameworksIT manageability – enterprise services (debugging, tracing, policies, life cycle)
TK, RP
Integration Reduce TCOScalability Readiness for B2C/B2BData/Process Integration Flexibility & Agility, Analytics, HANAOpen Standards Interoperability & Extensibility, better apps, fasterCloud Speed of Deployment, TCO, cloud platform, cloud apps, afaria
OSGi basedNo State in middle tierCustom extensions supportedStandards based protocol (OData/HTTP/S)Single entry point Cross platform pushOne stop Admin portalSupport for most IDM providers (with custom extensions)Centralized App management
AppDesigner: You can design amazing mobile apps, drag and drop - outside of SMP, build app (pull details from the video & blog from Jens
OData makes our gateway much more than just a proxy for other services …examples:-- adds metadata model-- data paging (a must for "real" apps)-- data response reshaping-- both missing from plain-old-REST-- other adds, too
-- ability to openly operate/inter operate with other HTML5 authoring tools is huge-- having this be a web-based tool is a huge plus, provided that things like SCM and simulator integrations are done right-- application templates are a huge differentiator-- Although this is an HTML5 tool, let's talk about native application development; Kony will emphasize a single IDE, but it is a bogus story that can be defused
Key point to highlight here is around MBO. It’s not going away. It will always have its certain use cases, but it’ll be more and more of a corner case. We think most of our apps will move to the lower TCO/higher scalability Offline OData architecture (lower dotted blue lines). Some ISVs may want to reuse our extensiblity framework borrowed from Agenry (that’s an option too, but we think most will go Native or HTML5 using OData). BUT THIS IS CUSTOMER CHOICE. If they want to move to lower TCO, B2C-like scalability, but still have offline, look at Offline OData. With SMP 3.0.
Building the device resident application is the very tip of the iceberg. The bulk of the work and where home-grown projects get into trouble are the properly handling the tasks and features below the surface.With a platform – you can focus on the UI, data model and business logic, and leverage the platform services to handle the necessary but unsavory bitsThe ratio of above/below the water line shown is representative of a fairly complex mobile resident portion of the application. For simpler apps – the waterline would move up