Skip to Content
Product Information
Author's profile photo Murali Shanmugham

Build native mobile apps using SAP Cloud Platform SDK for iOS 3.0 and Android 1.0

There have been plenty of announcements in Cloud Platform Mobile services the week before SAP TechED. Martin Grasshoff has summarized this in his latest blog post “Introducing Additional Mobile App Development Tools“.

One of the key announcement is the availability of SDK for iOS 3.0 version. I had used the SDK when it was initially launched and since then there has been lot of capabilities added to it. Andreas Schlosser has summarized all the new capabilities of SDK for iOS 3.0 version in his blog post What’s new in the SAP Cloud Platform SDK for iOS 3.0

I spent some time over the weekend upgrading my iOS SDK to try out the new version. I have recorded a video showing how easy it is to use the new iOS Assistant to create native iOS apps.

Another key announcement was the general availability of the SDK for Android by Britt Womelsdorf in his blog post “The SAP Cloud Platform SDK for Android is GA“. I also managed to setup my Android Studio on my macbook to try out this SDK and captured the steps in the below video.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Luke Phelan
      Luke Phelan

      Thanks Murali.

      For destinations in mobile services, should they point to a single OData service?

      E.g. if in SAP Cloud Platform I have a destination for cloud gateway, and there are multiple OData services available, in Mobile Services should I have a destination for each OData service that my apps consume?

      Author's profile photo Murali Shanmugham
      Murali Shanmugham
      Blog Post Author

      Hi Luke,

      In one of the previous Implementations, there was a need to use multiple (existing) OData services in a single mobile app. Individual Mobile Platform destinations were created for this and the iOS SDK was used to add those multiple destinations.

      I haven't tried using a destination for example which points to the catalog service - http://<server>:<port>/sap/opu/odata/IWFND/CATALOGSERVICE;v=2 of the Gateway system. It should still work, but I guess it would involve additional work on the model definition.