SAP Mobile Platform Reviews

It was basically for branchless banking and mobile wallet. There are multiple use cases built on top of that including agent banking, wallet transactions, fund transfers, merchant payments, and all related functionality.

I think it was a good platform. I am still curious why SAP ended the SNP 3.0 and why they ended the support. It was a fantastic platform and there is still demand in the industry. We actually signed a royalty agreement that would allow us to sell it to customers. However, when the principal company marked that as end-of-support, nobody is going to take it.

There was no reporting functionality in the version we used. It all had to be done by another BI or reporting platform, so we used to actually migrate data from SAP Mobile Platform to that platform.

Inherently, that product at that time had no reporting capabilities. It had to be done through some other platform.

The only issue arose when SAP actually marked it as end-of-support. Otherwise, as a platform, it was fantastic. I don't think there was any major concern we had with the product itself. But when you mark any platform as end-of-support and we, being the OEM partners, it definitely created significant challenges for us.

We started working on SAP Mobile Platform in 2016.

There were no issues with the on-premise solution. Especially in the financial sector, SAP should have both options available: on-premises and cloud.

When it comes to cloud, it was not typically through managed services, so banks used to manage it through their data centers for on-premises deployments. It wasn't particularly difficult because SAP used to give very clear guidelines on the number of transactions and the processing of the CPUs when you hit certain amounts of threshold of TPS, and how you would be able to scale up and enhance the hardware. With several customers we worked with, it performed effectively. We didn't have any serious concerns about scalability.

The performance was consistently good.

A couple of our customers are using SAP Mobile Platform. We are not the end users but rather the OEM partners of SAP, and we used to implement SAP Mobile Platform for our customers. Due to SAP declaring it as end-of-support in 2021, one customer has moved from SAP to another solution. They haven't migrated the whole system yet, but they are planning to. Another customer is also planning to migrate because of the end of support.

We have integrated with several renowned international core banking systems such as Temenos and Oracle.

The pricing was based on the number of wallets, and I think it was reasonable. I don't have many concerns over the pricing. Unfortunately, we can't use it anymore.

I have personally worked on SAP Mobile Platform for the past 15 years. Ericsson is still working in Pakistan, running one of the biggest mobile wallet platforms in the country. If SAP hadn't marked it as end-of-life, we could have penetrated this market for at least two to three more customers.

In this market where we are working, there is still significant potential, especially with digital banks emerging with digital licenses and e-money licenses in the country. The challenge in Pakistan and this region is that statutory regulations do not allow financial institutions to host their applications on clouds outside Pakistan.

We were the OEM partners, not resellers. This particular agreement ended in 2023.

On a scale of 1-10, I rate SAP Mobile Platform a nine.

Over the years, I have seen benefits from using SAP Mobile Platform and now mobile services, and I think SAP keeps improving the capabilities around SDKs or system. This has made it more developer-friendly and it's not that complex to build mobile services.

I find them valuable because a lot of our enterprise customers started moving towards handheld devices for their day-to-day process. Rather than going down the rabbit hole of developing the applications on native apps, specifically for Android or iOS, SAP Mobile Services came up with an SDK so you can just build it once and then roll it out for any device.

I could share metrics on improved operational efficiency or workforce productivity since starting to use SAP Mobile Platform or mobile services. With our customers, we would run an exercise after going live, asking them how their old process compared to the new one with mobile services. We've received good feedback because a lot of the old process was on paper and pen, noting it down, coming back, and then feeding them into the system, which takes quite a long time for people to do. In cases where people lose the paper they've noted, they have to redo the same thing again. With mobile services, they just carry the mobile phone with them, do it straight on the device, and it updates the SAP system, saving quite a lot of time for the end users.

I would suggest improving the reporting by having more details around connection times. I think it is good, and I'm happy with what it is right now. Apart from that, if integrating to third-party systems can be made easier, this can be made into an app which can connect not just to SAP systems, but also to any third-party systems.

Based on my experience within the last 12 months with technical support, I would rate them a nine out of 10, where 10 would be the best support.

Positive

We do use the offline data management feature. The integration of mobile services with enterprise systems such as SAP S/4HANA is something we have done. We use RESTful services to integrate, and it's all embedded in the mobile services application that we build, so it's all connected to whatever back-end system it is.

My impression on the pricing and licensing of SAP Mobile services is that's something that's always interesting when it comes to SAP pricing. In recent days, I'm not much involved in terms of sales aspects for services.

For my company, what made me choose SAP is that they update regularly and they are up to date; I would recommend SAP to my customers over other vendors of a similar nature.

I rate this solution 8 out of 10.

I use the solution in my company for our customers' sites. I worked for a consulting company previously, which was until last year or a couple of months ago, but I will say my experience on the mobile development platform of SAP was always at the customer site. In the past, the tool was used if you were talking about approval for a purchase order, confirmation of some request, or inquiry for a summary service.

If we work with the mobile extension of the ERP platform, we save time. We follow the customer and give better service by focusing on their needs. We have different topics, and as we know, the mobile area is strategic for an extension of the digital revolution in a company.

For a couple of years, SAP deployment and updates were not fair and simple. After the last evolution of mobile development in SAP, I need to check the latest features of the tool. At the company where I work, we are not deploying a new mobile platform or mobile solution at the moment. We are implementing a new group model for the organization, which is why we are not focused on the mobile development platform at the moment. I used the SAP Mobile Platform in 2022 for a project in my previous company, where I worked for eight years and used it until the end of last year, which is December 2023.

The product should offer an easy way to deploy the application that can be deployed for a user, not only on SAP Fiori or GUI, along with the key features we need to have on a mobile platform, like the extension for SAP EVM. I see areas like SAP EVM for some mobile evolution, and it is not simple when we have something like it in the middle of the solution. We have to investigate if it is possible to have another way to manage the warehouse management or a simple way to have a key menu on the front end of the mobile platform. At the moment, we have to make some updates to the tool, and it is not simple.

I have been using SAP Mobile Platform for more than ten years.

Stability-wise, I rate the solution a seven out of ten.

Scalability-wise, I rate the solution a six out of ten.

I rate the support a six out of ten. It takes the support team a long time to respond to some queries.

Neutral

For SAP Fiori's interface in the past, Neptune Software was strategic for the speedy deployment of the solution, while Fiori itself was not very useful. Neptune Software was absolutely a speedy concept, and we used ABAP coding for Neptune Software's interface. For sure, SAP Fiori was used in the past, but Neptune Software was a good platform.

The tool is expensive. I rate the tool's price as an eight or nine out of ten.

The tool is not easy or simple to integrate with other infrastructures. In the past, the concept of an MDM platform was strategic to understand how to deploy applications between different mobile solutions, like iPhones or Androids, and also based on the time zones.

I am looking at SAP BTP, which is strategic for mobile development, but in the past, I worked with MuleSoft. Not only have I worked with MuleSoft for the integration but also with SAP PI/PO for integration and some other integration suites. I have also used a platform to deploy new applications as per SAP Fiori's concept.

I rate the tool a seven out of ten.

In our mobile app development, we use SAP Mobile Platform primarily for building apps with SAP UI5. SAP provides a convenient build process, making it easy to develop based on business requirements. We integrate seamlessly with their integration suite, ensuring connectivity with SAP and other systems. Ultimately, our users access the app via a browser on their mobile devices, connecting to SAP for efficient use.

One valuable feature of SAP Mobile Platform is its enterprise-grade standard and maintained APIs, available out of the box for easy integration with various systems. While there might be charges for cloud usage, on-premises deployment is free with available services. Customization options allow tweaking of standard features for specific needs, making it widely accepted and enabling mobile access to all enterprise applications.

One drawback is that SAP Mobile Platform apps are only available through the browser, making offline capability more challenging to implement. This limitation hinders usage in industries like oil and gas, where offline access is crucial due to safety concerns. Enabling native app support with built-in offline capabilities would greatly enhance its usability and cater to various scenarios where connectivity is limited or prohibited.

I have been using SAP Mobile Platform for almost nine years.

While SAP Mobile Platform is generally stable, occasional glitches and bugs may arise. However, SAP provides prompt responses and solutions when issues are reported.

SAP Mobile Platform is highly scalable.

I would rate the technical support as an eight out of ten. It could improve by providing quicker and more accurate responses.

Positive

Besides SAP, I have worked with vendors like Informatica.

The complexity of deploying SAP Mobile Platform varies depending on whether it is on-premises or in the cloud. On-premises deployment is straightforward but requires third-party tools for native SAP support. Cloud deployment involves dealing with scattered documentation and steps, lacking a comprehensive user guide for easy reference. Simplifying deployment instructions and consolidating information would greatly improve user-friendliness.

For SAP Mobile Platform, pricing varies based on usage and deployment options. There are no charges for on-premises deployment, but for cloud usage, costs depend on usage levels. There are two modes: creating your own APIs or using SAP's API management, each with different pricing structures.

In a recent project, we integrated SAP Mobile Platform with various SAP systems. Most companies store their data on-premises or in SAP systems. Our task was to sync this data with the mobile platform hosted in the cloud. We used integration tools to connect seamlessly with these on-premises systems, ensuring data synchronization. Additionally, we connected to satellite systems like Jira for specific functionalities such as ticket management, requiring robust integration capabilities.

The security model of SAP Mobile Platform has positively impacted our mobile applications by addressing initial reluctance and highlighting its suitability for certain tasks like approvals and on-site data entry, especially for industries like oil and gas, utilities, and manufacturing. This enables remote approval processes and real-time data entry, improving efficiency and accessibility for users who are not always at their desks.

SAP Mobile Platform supports our cross-platform mobile app development needs by enabling the conversion of SAP transaction codes into mobile-friendly interfaces. This allows users to access SAP functionalities from their mobile devices, increasing flexibility and productivity, especially for departments like sales who need to input data on the go. 

Overall, I would rate SAP Mobile Platform as an eight out of ten.

It's a wonderful solution from a design perspective and from a scalability perspective. We haven't actually found any performance-related issues for the past five years and a couple of implementations.

The only thing which basically is bothering us now is that SAP has announced that they'll be ending the support on the SAP platform. That said, we are one of the original partners for SAP, and we are selling it with the name of AutoMWALLET for branchless banking for mobile wallet solutions in Pakistan. The end of support would make it difficult for us to sell the solution to clients.

We have been working on the solution for almost five years.

There are a couple of times we had to get back to SAP support to ask them about an issue. Otherwise, it's pretty stable.

We haven't actually haven’t received any scalability issues for the past five years.

It's not that difficult to set up. SAP has provided the complete installation and configuration scripts, and there's ample documentation available. Implementing it is not an issue.

If you are just talking about installing the standalone SAP Mobile Platform, that won't take more than two to three hours. The problem is that when you have multiple integrated third-party integrations, it can be longer. In that case, the deployment really depends on how you actually do it, as, in a financial institution, there is a lot of middleware and other third-party systems that are also integrated with your system. We have a complete set of APIs exposed to different partners, and how everything goes together depends on what type of integrations are there and how complex they are.

That said, it should not take more than three to four hours when it comes to only the standalone SMP.

We have a team who implements the SAP Mobile Platform. We already implemented it in a couple of banks here in Pakistan.

It's a per account license, a per wallet license, so the cost really depends on the number of users. The market has changed in the past six or seven years.

I was working for another company in 2013 and there, I was actually also working on the SAP platform. There were three different implementations at that time and the cost was higher. However, at that time, in the market, there was no other competitor as well.

You would be able to sell $2 a wallet very quickly, however, now, the competition is more comprehensive and the cost is higher. From the AutoSoft Dynamics perspective, we have some inventory licenses. We have already purchased from SAP at a much better cost. We can get good pricing.

We are one of the partners of SAP Mobile Platform. We have implemented it in a couple of banks in Pakistan.

We use the on-premises deployments. In Pakistan, the local regulations of the Central Bank require that they do not post solutions on public cloud. You can only do it on the local cloud within Pakistan, not outside Pakistan.

I’d rate the solution nine out of ten.

It's an excellent system and very, very flexible with a very, very good design for the database. However, SAP has ended its support for the SMP mobile platform. They have probably moved it to a cloud-based solution, which they are offering, yet, from the on-prem perspective, they have ended the support for SMP, which they used to call SMP 3.0 3.1. That is a problem.

I am currently working with SAP, specifically on implementing the SAP Mobile Platform for energy modeling.

We use the SAP Mobile Platform to implement numerous models, including CRM, billing, and logistics. We have successfully configured and deployed these models as part of this project.

I haven't used the model platform extensively due to its low adoption rate. However, I have raised tickets on the platform and received support.

Both platforms, the SAP Mobile Platform, and SAP, are highly valuable for our company because they facilitate integration, which can be expensive.

It's very convenient to connect and create billing accounts through the SAP Mobile Platform. 

The SAP Mobile Platform is user-friendly, and we can easily add new features to adapt to our company's needs.

As part of this project, we are upgrading the SAP Mobile Platform to SAP4HANA, which will be hosted on the cloud, specifically on Cloud.

The cost of the SAP Mobile Platform is high, and there is room for improvement in its pricing.

I have five years of experience working with the SAP Mobile Platform with the current project.

I began working on this project in 2016, and since then, we have collaborated on several new initiatives to implement a new commercial system for two companies in the state of Alagoas and PoE, affecting two million people.

I have collaborated with Accenture and other stakeholders who have supported me throughout the project.

I am not a developer but transitioning towards integration and designing architecture.

The support for SAP is excellent because we have a local representation in Brazil, through PRADA. Whenever we need to contact SAP, PRADA can assist us in solving problems or answering questions. This is crucial for us because PRADA provides support in Portuguese, our native language.

When we open a ticket on the SAP platform, we write it in Portuguese, but we rely on the support of external consultants to help us create the ticket.

I would rate the support a nine out of ten.

I am currently working with SAP, and our organization is planning to implement SAP4Hana.

I am the leader of technology in our organization.

The cost of SAP is extremely high, and it's not affordable for everyone.

I would rate SAP Mobile Platform an eight out of ten.

SAP mobile platform is not just for developing front end applications. It has many other components, like integration, middle layer management, and security.

Two of the very fascinating features that make SAP Mobile Platform stand out from other platforms are its offline capability and integration capability. It allows easy integration with SAP, whereas other platforms don't have very good coupling with SAP. This solution handles both SAP and non-SAP.

One convenience this platform provides is that it's an integration hub for web services, web APAs, and PIA services, or integration with SAP to RFP. 

There are many components within the solution. There is a development tool for developing apps, and there is an integration gateway facility, where you can integrate multiple buckets, depending on your front end.

You can also apply coding at the integration level itself. When you are reading the data, you can run data cleansing activities, or change it according to the user input. Improvement can also be done in the gateway, fortunately, through Google scripting language.

The toolkit to develop front end applications, especially native applications, is not that good. That is one of the drawbacks of the solution. 

The development toolkit is only good when we are developing SAP-related apps. When we have apps that need some extra integration for other environments, and have additional features, it's not that good. People prefer to use other non-SAP development platforms for app development, and then they use SAP as an integration layer to connect the app to the backend.

I would like native app development capabilities. We already have hybrid app capabilities, but I would prefer to have native app development studios integrated into the services. If they had a toolkit within the framework for developing applications, it would make it easy. 

Right now, we develop services in the backend. We generate the RS services, and then give the URL to the front end team. If plugins were allowed directly from our APS to our Java files, they could directly be integrated into any of the front end application studios. Currently, that framework is missing. I would like them to make it a bit more open-source, rather than restricting the data to SAP itself.

Also, there is limited support for different languages.

I have been using this solution for five years. I have seen drastic changes in the platform. It was an on-premise installation when it launched. Now, they introduced a SAP cloud platform, and renamed it BTP, Business Technology Platform. 

This is a stable solution.

When it was on-premise, it was up to the users to maintain the scalability. When they migrated to the cloud version, however, SAP became responsible for the scalability. It is a scalable solution. We have a team of 12 people within our organization who work with it. 

It's standard technical support. They have introduced different support models in the past two years, and now they have on-demand calls. Before, we would raise a ticket and wait for their response. Now, we can schedule an expert call with the team. All of the features are really helpful.

However, there are too many companies within their ship. It's not one single product, it's a complex structure, so when we raise a ticket, sometimes we end up selecting the wrong team. Then it takes a couple of days to get redirected to the right people. After that, we get our response. Considering that, I would rate the support between a three to four out of five. 

If you have some basic background, it's very easy to do the setup. I would rate the setup as a five out of five, because it's not a big challenge at all. 

If you already paying for an SAP license and have SAP products that you are using, the price for SAP Mobile Platform is negligible.

I would rate this solution as an eight out of ten. 

We have no less than 26 different applications on SAP Mobile Platform through the SAP app store. When corporate needs go up, we identify needs and find out where we can plug into them to fill those needs. 

The platform independence is great. I can use it across mobile devices. That's the best aspect of it.

It's stable.

Technical support is helpful.

If I have to go for hybrid development, it is still too complex of development, per se. If there would be something out of the box, a pre-packaged solution, which can help us with going no code or low code, that would be better. There is currently low code or no code being provided by some partner ecosystems of SAP, yet not by the SAP itself. If it was low code or no code it would be ideal.

I've used SAP for six or seven years. I've used the Mobile Platform for two years or so.

The way we use it is transaction dependant. It's used very often in logistics. However, if it is supporting us, it shows that it's good and reliable. 

I can recall one use case where we had 20,000 users on the solution. 

With my previous company, I was also involved in the release and support team. We handled support and were recognized globally for providing 100% support. We were so good at pinpointing issues, we rarely had to go directly to SAP. In the last three years, we only ever had to reach out maybe two or three times. SAP support is good, and we rarely need to reach out as SAP.com has most scenarios covered. They can be leveraged to help users problem solve. 

The initial setup is kind of moderate in terms of difficulty. It depends on what features or how many features we are going to leverage. Depending on that, it is not always simple, though it leans more towards simplicity than complexity.

The deployment length depends. It is not always that simple when deployment comes into play. The process is subjective. If it is only the requirement, it is quick, however, sometimes you need to worry about access control and other features also coming into play. If those are coming up, slightly more time is required, however, if it is just a component of mobility, then it is quick.

From the feedback I have received from clients, they are mostly okay with the main pricing scheme. However, when you go into CPI, the charges are hidden. While the Mobile Platform is pretty clear, other areas are murky and, since mobility won't work without CPI, and CPI is being unclear about the pricing, it can get confusing. Therefore, with just the Mobile Platform it's straightforward, and with other add-ons like CPI, it can get confusing and sometimes costly.

We are a partner and a customer. 

I'm not sure which version of the solution we're using.

We used to be on AWS on the public cloud. We are still on AWS and are now on a private cloud.

I'd rate the solution nine out of ten.

We have implemented SAP Mobile Platform into two to three banks. We are one of their OEM partners.

There are multiple types of customer onboarding. There are multichannel platforms like mobile apps, where you have an Agent and Salesforce app. From there, users can onboard the customer or the customers can do self-onboarding from ATM machines.

There are multiple types of transactions. We have mobile wallet transactions, including bill payments and telco-based top-ups, or we have QR code-based payments and we have integration with third-party agents as well. With the telco companies, the customers can walk into any of the telco agents and they can do cash-ins/outs.

SAP's Mobile Platform when has a lot of technical features, however, the way they have written the transaction processing is really smart and we're using it very successfully in terms of scalability and in terms of stability.

The initial setup is not overly complex.

The solution offers good scalability.

So far, the stability has been good.

We've found the technical support to be helpful.

There are multiple functionalities within the design however they're not, actually, a hundred percent available on the UI in SAP's platform. If they can work more on the UI platform or maybe they change the framework on which the UI is written. That would be great. Right now, it is older technology with older frameworks. It's not purely on microservices. They could transform it onto microservices in order to benefit us as a partner.

The licensing model is a bit dated.

We started working with the solution in 2015. AT this point, it's been six years. It's been a while.

The solution is stable. It doesn't crash or freeze. It doesn't have bugs or glitches. It's reliable.

The solution scales well. It's designed very smartly and can scale really well.

The solution works well for small, medium, or large organizations.

We have been getting support from SAP on the technical aspects, however, we don't normally require much technical support as our team is fully enabled now. That said, whenever we need it, we have our support agreement with SAP and they provide us with support for that product.

They have good technical support services for the most part. They have a very streamlined process and the support is good. The people in support know the product. Sometimes there are incidents where we have gotten the support we needed a little late, however, overall, it's good.

The initial setup is not overly complex. It's pretty straightforward. A company shouldn't have too much trouble with the process.

There are a lot of integrations involved when it comes to the deployment of the mobile wallet platform as it involves multiple integrations with central units, such as telcos, bill payment aggregators, and third-party agents.

When it comes to the maintenance, usually the maintenance is required on the integration part. Otherwise, from the engine point of view, there are a couple of queries every six months or so. We don't require support from SAP very often.

We provide implementation services to our clients. We are the OEM partners. We have bundled our products and integrated them with the SAP platform and we are selling it with our proprietary name. This is our product which is built on the SAP platform. We have also implemented SAP's platform to a couple of banks, as well, without bundling any module.

The industry has evolved now. In 2015, it wasn't that expensive. However, at this point in time, there is a lot of competition in the industry on the mobile wallet platform. There are multiple mobile platforms available and they are offering multiple pricing models. However, we are with SAP on their pricing model with a number of accounts.

It could be more competitive in the market if we could have different pricing models for the platforms. SAP needs to adjust how they license.

We are implementors. We have some partnerships with Microsoft. In terms of the technology stack, we are using Microsoft, Oracle, and SAP, not IBM.

For the local industry, we have done some customizations on the solution and that's how we are using it.

We have implementations on both cloud and on-premises currently. We are using on-premises deployments as the industry where we have implemented it - the central bank - doesn't allow cloud-based implementations at this point in time.

I'd rate the solution at a nine out of ten. We've mostly been quite satisfied with the capabilities of the platform.

Solid development platform that allows you to automate functions from different backend systems. It is a true MEAP.

Installation is extremely painful. Communication between Sybase, the required Relay Server and Afaria is very difficult and time consuming. The required products keeps changing as well, you may need to add NW Gateway into the mix as well. The "GUI" generation isn't to that point that you can eliminate the need for custom platform specific code for the user front-end. The long-term roadmap of SAP's mobility platform is very confusing (acquisition of Syclo, etc.)There isn't a big ecosystem of consulting partners, SAP consulting, etc. that have deep experience to help you hit the ground running.