8 Comments

You must be Logged on to comment or reply to a post.

  1. Phil Cooley

    Thanks Lisa for providing more detail on this – especially like the architecture diagrams included so as to enable a deeper understanding for Consultants etc in this space. Much Appreciated. Will be staying tuned to the tutorials and demos. THANKS!

    (1) 
  2. Frank Schuler

    Thank you for sharing this interesting information, Lisa.

    However, I am confused how SEAM fits with SAP Cloud Platform SDK for iOS, Agentry and the Kapsel and Cordova Plugins for SAP Fiori Client.

    Is there a document that explains SAP’s mobile strategy and how those to my mind disparate mobile solutions work together?

    Many thanks in advance

    Frank

    (1) 
    1. Sue Berry

       

      Hi Frank,

      SEAM sits on top of SAP Cloud Platform SDK for iOS and uses it’s API and UI controls to make it easier for developers and technical business users to build new or customize existing applications.

      The Kapsel and Cordova Plugins for SAP Fiori Client is for customers looking to build HTML5/UI5 applications and specifically Fiori applications which are lighter/simple mobile applications. SEAM builds native applications and customizes specific SAP complex mobile applications such as SAP Asset Manager.  Unlike a Fiori mobile application, SAP Asset Manager has many screens and complex workflows and SEAM helps tailor SAP Asset Manager to exact business needs.

      For Agentry vs. SEAM. Most of the usecases for Agentry are specifically for customizing Agentry-based applications such as SAP Work Manager, SAP Services Manager, SAP Sales Manager, etc. SEAM is for customizing SAP Asset Manager and for building new native based on SAP Cloud Platform mobile services and the new SDK for iOS.

      I hope this helps.  Please let us know if you have additional questions about this.  I will look to see if there is a document that further helps clarify.

      Sue

      (0) 
      1. Frank Schuler

        Thank you for this explanation, Sue.

        Do I understand it correctly from Lisa’s blog that “The [SEAM] client applications run in native players […]” and that the currently available SEAM player for iOS “sits on top of SAP Cloud Platform SDK for iOS […]” as you mention above?

        Best regards

        Frank

        (0) 
        1. Christopher Asche

          Hey Frank,

          SEAM client applications are in fact full native apps (iOS). They consume UI controls and other important application components (oData, secure storage) from the available SAP Cloud Platform SDK for iOS.

          Chris

          (0) 
            1. Christopher Asche

              Hey Frank,

              The native player Lisa mentioned is just a synonym for the SEAM Client, which is a native application that “plays” the metadata.

              If it helps, you can think of it as a native-container, similar to Cordova, that contains and plays the metadata. Of course technically it is nothing like Cordova 🙂 but the concepts are similar.

              Chris

              (0) 
            2. Bill Froelich

              Frank,

              The native player that Lisa mentions is the SEAM client application.  This is a native iOS application that receives the metadata and interpets it to create the UI using the SAP Cloud Platform SDK for iOS controls.

              –Bill

              (0) 

Leave a Reply