Share your experience using Verivo Pyxis Platform

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.

On-premises

Other

It has impacted my mobile applications overall specific to the user's and customer's requirements. Some of our customers might not have network facilities within their warehouse, so instead of spending quite a lot of money on network around chilled and frozen areas, they wanted an offline capability of the app. They don't have to switch between multiple applications; just one application, whether they have a network or not, they can still keep using it.

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 have found push notifications and mobile-friendly access to the applications as the most valuable features of this solution.

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.

The analytics and reporting capabilities in SAP mobile systems have helped me understand my mobile strategy better because we don't have wider reporting capabilities within mobile services. There is some reporting functionality, which I would classify as very basic, just to indicate how many devices are being connected, but it's not that comprehensive in terms of reporting.

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.

I have been working with SAP Mobile Platform for a couple of years. To put things in detail, SAP Mobile Platform is outdated now and there's no more SAP Mobile Platform. It used to be there around five years back. Things got moved to SAP Mobile Services within SAP Cloud, so I'm also working in SAP Mobile Cloud services for about two and a half years now.

I could comment on the stability and reliability of this solution over the years of my experience and I find it wonderful.

I could comment on how scalable this solution is, and I think that's nice.

I often communicate with SAP's technical support and customer service for this tool. My interaction with them is wonderful; I find their skills and professionalism satisfactory and I'm happy with them in general.

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

Before SAP Mobile Platform, we used a different solution called Sybase. I understand why we decided to switch from Sybase to something else.

I could share my experience with the initial setup for SAP Mobile Platform and SAP Mobile Services by stating that the struggles that I faced are no longer present; the other users will no longer face them. It was in the past.

I have noticed a return on investment by saving resources. As mentioned, a lot of customers have had an older approach to doing things, and it has been a great commercial saving for the users and for the business.

Before choosing SAP, I did not evaluate other vendors, but since I work in the consulting industry of SAP, it was always SAP. There were some scenarios where customers specifically wanted to go with React Native development or Flutter development, getting out of SAP completely.

Utilizing mobile data synchronization in this solution helps my data consistency efforts because I don't have any specific concerns around data consistency so far; it is just ease of use.

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.

Public Cloud

Other