Skip to Content
avatar image

I am worried about SAP's mobile strategy

As if it was not already confusing enough, at least to me, with the SAP Cloud Platform SDK for iOS, Agentry and the Kapsel and Cordova Plugins for SAP Fiori Client, now we also got SAP Enterprise App Modeler (SEAM). I asked Lisa how those to my mind disparate mobile solutions work together and will share any insights as soon as I receive them.

* Please Login or Register to Comment on or Follow discussions.

6 Comments

  • May 25, 2017 at 02:52 PM

    Frank - as a PM in the mobile organization, let me give you my perspective. I was at SAPPHIRE last week presenting many topics, including SEAM as well as ContentToGo. I said this phrase multiple times - if all you have is a hammer, everything looks like a nail. What I meant by that phrase is this - the mobile landscape is diverse. There are many different technologies that one can use, under the right circumstances, and be successful. If you only provide one technological approach, then you you are compelled to fit the technology into the scenario. Ideally it'd be the other way around. I want you to focus on the scenario that you are trying to support, knowing in confidence that SAP can provide to you the right mobile technology to best solve the problem. Does your scenario only require iOS Support? The SAP SDK for iOS is likely your best choice. We also provide an Android and Windows SDK for those operating systems. Looking to build microapps or even get mobile without any development work? ContentToGo can serve your needs. Need the app to run on desktop as well as mobile, hybrid web is a good option. And lastly, if you are an SAP Asset Manager customer and need to customize the experience? Well, for many reasons SAP Asset Manager needs to be a native experience on iOS, so the SAP SDK for iOS is naturally part of the solution. But we don't want you to have to write Swift code in order to customize the experience, we want to make it simpler. Hence the metadata driven model fits the bill. Once you are finished with your customizations, SAP, using embedded technologies transform that metadata into native SAP SDK for iOS controls and deliver the native experience. SAP wants to provide you with a full range of capabilities to enable your mobile journey, and to do that we need to support multiple client technologies and architectural approaches. I hope that makes sense, and feel free to reach out to me directly if it doesn't!

    • May 25, 2017 at 05:40 PM

      Britt, I'm not a mobile developer but I can understand where Frank is coming from. I also agree with your point that we need more than just a hammer. But when SAP offerings are abundant frequently clear and concise information about them is not, especially when it comes to comparing one thing to another..

      I'd encourage your team to post on SCN information in the format similar to what Julie Palmer did in her blog about NWBC. Very simple "if... then..." (like in your comment here) with clear comparison between different offerings can steer SAP practitioners towards best choices.

      Thank you.

      • May 25, 2017 at 09:11 PM

        Jelena - thank you for the feedback. I was speaking to someone internally about this topic. She said something very similar. If I can paraphrase, it'd be good for SAP to create a blog (or something) that describes the various mobile app development options, and in which scenarios they make the most sense? Basically a side-by-side, scenario driven explanation of the options along with recommendations?

    • Jun 26, 2017 at 01:44 PM

      @Frank - have you seen this blog? https://blogs.sap.com/2017/06/21/sap-cloud-platform-mobile-services-development-options/? I'm curious how close this comes to answering your original question?

  • Add comment
    10|10000 characters needed characters exceeded