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.
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.