At the SAP User Conference in Orlando recently, SAP released an impressive set of applications ' Fiori ', based on SAP's new HTML5 framework (i.e. SAPUI5). SAPUI5 (based on Html/css/javascript, on top of jquery, etc.) has been around for more than a year, but last week the Fiori application released by SAP has shown that SAP is very serious about SAPUI5 as a tool set for future UI development. DJ Adams a year ago in his blog has foreseen the transfer of SAPUI5
SAPUI5, our HTML5 Control Library, SAP will be used as a standard user Interface control library for applications that require a "consumer grade" user experience.
In fact, within SAP's own UI Technology Roadmap 2013, SAPUI5 has been used as a UI presentation technology for any scenario. If we assume that users will need more of these applications once they have tried the Fiori application. The expectation of a "consumer grade" user experience becomes more common, meaning the expectation of developer skills.
SAP gives us some hints in the Appendix to UI Roadmap 2013, the following is a comparison of traditional Dynpro, Web dynpro abap,sapui5 Technology
UI Technology |
Skills Required (per SAP UI roadmap) |
Dynpro |
ABAP & Dynpro |
Web Dynpro ABAP |
ABAP OO, Web dynpro ABAP, floorplan Manager |
SAPUI5 |
Javascript, HTML5, CSS3, Gateway, OData |
If you look closely, you'll see a big shift in the technical requirements of SAP developers, just as SAP was trying to transform the user interface layer into Java 10 years ago. Using Sapui5,web developers to develop client Web applications using Html5/css/javascript, the ABAP developer focuses on the development of the business logic within the ABAP system and then exposes the interface to the Web application through the NetWeaver gateway. Further, the following table is available in SAP's guidance document on enhancing Fiori applications (based on SAPUI5):
With the transition to SAPUI5, I have a hunch about some of the challenges within the SAP ecosystem ...
SAP can rely on the ABAP development community to elevate the SAPUI5 skills of ABAP developers.
My point is that not many developers are going to change. Based on my observations, many developers still cannot easily switch to Web Dynpro ABAP development, as evidenced by the SAP technology Conference I attended in 1 August (when the Booked-out hands-on session was first introduced to the Web Dynpro ABAP). So if most ABAP developers need a lot of effort to cross over to the Web Dynpro ABAP (and its related concepts fpm and ABAP OO), I'm not hopeful that they will transform JavaScript, HTML5. Even so, ABAP developers still need to develop business logic under gateway services. Using SAPUI5 will present the Multi-develope scenario: the front-end developer of the Web app and the backend developer of the business logic. This is the same as in the Web Dynpro Java era, the business logic is developed by ABAP, and the foreground interface is developed by the Web Dynpro java. The concern is whether the customer is willing to accept this multi-developer scenario. In some places, it is not uncommon for front-end developers to be separated from the backend developers. Of course, there is a great demand for people with both technologies.
can SAP engage a new community outside of the traditional SAP ecosystem, allowing Web developers to accept SAPUI5.
I certainly hope so, though I think I can do more. My concern is that SAP's desire to build SAPUI5 into a proprietary HTML5 framework might prevent SAPUI5 's massive use. Looking back at another proprietary framework Web Dynpro JAVA,
I think most of the pure Java developers you meet on the street haven't heard of it, and it's not being used heavily.
SAPUI5 licensing is also problematic, and I understand that while the SAPUI5 trial is free, SAP development authorization (such as NetWeaver development license or Saphana Cloud) is required as a formal use. That's enough for most non-SAP developers to leave-they tend to use free open source or low-cost frameworks. In addition, the authorization means that the application is restricted to a large extent in the SAP platform scenario (like Web Dynpro JAVA), and most web developers entering the SAP scenario prefer to use more common libraries and frameworks-they have real-life experience and expertise, and are free or open source (such as Twitter Bootstrap). I personally think that SAP can do more to make SAPUI5 a lot of attention, open it up or promote it outside of the traditional SAP technology conference. I recently attended some developers and web developers meetings in Australia, and unfortunately there is no sap in these events. Currently, there is a fierce competition (eg) in what web frameworks or libraries should be used around Web developers within the Web ecosystem. All the various Javascript Mv*frameworks)-which are widely used in my mind is likely to succeed or have a longer life. For many web developers, SAPUI5 is not within their reach.
SAP's software engineers have designed a good framework for SAP's future user interface, but I'm looking to face SAPUI5 whether we're facing a technology sinkhole, not enough traditional SAP developers involved, and not that SAP developers don't come in because of transparency and licensing concerns, I hope I'm wrong.
Situ:
http://scn.sap.com/community/developer-center/front-end/blog/2013/05/22/ What-sapui5-and-fiori-tells-us-about-the-future-of-ui-development-for-abapers
Posted by John Moy 2013-5-22 9:10:28