What SAPUI5 and Fiori tells us about the future of UI development skills
SAPUI5, our HTML5 controls library, that SAP is using as the standard User Interface Control library in all their future applications that need a “consumer grade” User Experience
In fact, in SAP’s own User Interface Technologies Roadmap 2013, SAPUI5 is considered a viable UI technology in any scenarios irrespective of levels of usage or reach (although clearly Fiori apps currently target the higher usage or reach scenarios). If we assume then that once customers get a taste of Fiori apps, they will crave more over time, and expectations of “consumer grade” user experience will become more pervasive, what does that mean for the expectations of developer skills?
SAP gives us a hint with a table in the Appendix of the User Interfaces Roadmap 2013, where a comparison of Classic Dynpro, Web Dynpro ABAP, and SAPUI5 technologies is made. Here is what we see …
|UI Technology||Skills Required (per SAP UI Roadmap)|
ABAP & Dynpro
|Web Dynpro ABAP||ABAP OO, Web Dynpro ABAP, Floorplan Manager|
With this shift to SAPUI5 over time, I foresee some challenges in the SAP ecosystem …
Can SAP rely on the ABAP development community to upskill to SAPUI5?
Can SAP engage a new community of web developers to embrace SAPUI5, outside the traditional SAP ecosystem?
SAP’s software engineering teams have crafted a nice framework for SAP’s user interface future. But I’m wondering if we are heading for a skills sinkhole around SAPUI5, where inadequate numbers of traditional SAP developers move into this space, and non-SAP developers remain unengaged due to lack of visibility and licensing concerns. I’m hoping I’m wrong.