Q&A 4.png

As part of the SAP Integration and Certification Center, I have the opportunity to collaborate with various SAP partners and third-party vendors who enrich and contribute to the ever growing SAP Partner Ecosystem by integrating their solutions with SAP platforms.

This is especially true in the area of mobility with the recent launch of SMP 3.0, SAP’s flagship enterprise mobility platform. This release promised exciting new features to ease development and marked the arrival of a truly unified platform. Actually, many partners who have developed mobile apps on the Sybase Unwired Platform (SUP) or earlier versions of SMP have inquired about this new release in order to migrate their mobile solutions.

In an effort to shed some light on this, we have reached out to a few very early adopters of this new platform so they can share their mobile app development experience on SMP 3.0 with the broader SAP Community Network.

Here are a few excerpts from the first installments of this series:

What motivated you to jump onboard SMP 3.0?

As a professional, SMP 3.0 is a great fit for mobile-minded organizations: Mobile apps can be quickly designed, deployed, and managed using open standards and future-ready technologies.

As an enthusiast, the past few years of SAP products and direction have been historically exciting to say the least. REST APIs, OData, native apps, hybrid apps, and complete application lifecycle management? Yes, please.

I was further inspired to dig into SMP 3.0 and the related technologies from SCN content, openSAP courses, and SAP contests such as the SAP Game On contest. On SCN, John Wargo’s and Daniel Van Leeuwen’s content motivated me to dig into Kapsel, and DJ Adams inspired me to investigate a RESTful approach, SAPUI5, and my dim awareness the combination of two may be pretty powerful.

How would you compare your team’s experience developing mobile apps on this new version of SMP 3.0 versus the older one?

SMP 3.0 Native SDK is developer friendly to quickly enable integration with OData services compared with SMP 2.3 Native OData SDK. The build time with SMP 3.0 was reduced by around 20 % compared with SMP 2.3 Native OData SDK.

First impressions are the most lasting. With the positive comments we have received, it certainly looks like SMP 3.0  is off to a great start.

To read the complete Q&A session, please use the following links:

I hope you will enjoy reading about the partners’ experience. If you would like to see more blogs like this, please comment below. Or you can simply use the like button if the information presented here was of interest.

Thank you !

Quick links for the mobile app certification on SMP 3.0:

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply