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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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

View full review »

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. View full review »