Follow these best practices and tips outlined by Ameya Pimpalgaonkar if you are planning to execute an SAPUI5 project. See how an SAPUI5 project differs from a traditional project and why the design process is essential if you want to avoid technical errors.
After reading this article, you will be able to understand:
- The implementation difference between a desktop application and a mobile SAPUI5 application
- The technical aspects of an SAPUI5 project execution such as user experience (UX), wireframes, and design
- The different UX strategies for different implementation approaches (desktop and mobile)
- Key technical challenges that must be accounted for before starting an SAPUI5 project
- The importance of developing device-agnostic applications
- How deployment of SAPUI5 applications works for different mobile platforms, if required by the project
- The role of mobile middleware in delivering SAPUI5 applications
It is essential that all SAPUI5 projects begin with a user-centered design of application wireframes. Wireframes should always be the starting point that roughly captures an application’s structure. Based on approvals, a high fidelity prototype must be developed capturing color schemes, design, and look and feel, including the navigation structure.
I recently had a chance to talk to a few people who have worked on SAPUI5 implementation projects. When asked about execution of their projects and whether they were any different from traditional SAP projects, they all said their projects were run and executed exactly the same as a traditional SAP project.
However, in my opinion, traditional project execution does not apply to SAPUI5. Not developing an SAPUI5 project strategy for execution can cause problems in the build and delivery phases. The bottom line is that SAPUI5 projects must not be planned and executed on the same line as that of other SAP projects. Therefore, I decided to write this article to provide clear guidelines for organizations that are planning an SAPUI5 implementation project.