End of Road for sap.ui.commons Library !!!
With the latest version of SAPUI5 1.38, SAP has punched out a shocker. If you are not aware yet, the entire sap.ui.commons, sap.ui.ux3, and few other libraries are marked as deprecated. Here is the snapshot of the announcement from the release notes of 1.38
That might mean, these libraries will not receive any further improvements and will be removed from the SAPUI5 Runtime sometime soon. It’s been hardly 4 years since it came out and its already deprecated!!! Wow, this is some agility. Now the question – When these libraries will be removed and what will happen to the applications which were built using sap.ui.commons library? The speed at which SAPUI5 versions are updated, my personal feeling is that the commons, ux3 library might be removed by end of this year.
During the later part of 2012 and early 2013 – when SAPUI5 was still evolving and sap.m library was still maturing, many of the clients went for sap.ui.commons based applications. I am sure some of you may be in a similar situation. These applications were mostly meant for Desktop, had multiple screens, lot of information and they did their job perfectly.
Now what’s the future of these applications? Do these applications need to be re-developed using sap.m controls? If yes, then the planning for the re-build has to start sooner than later. I think SAP needs to answer by when these commons, ux3 libraries will be removed from the packages.
One of my client regularly update their SAPUI5 version on the Gateway server, so as to get the latest features. So I do not really want them to see one fine morning that these applications are not working anymore. We need an answer from SAP on the future of these libraries. WHEN??? So that we can inform our clients and can start the mitigation plan.
What happened to the commitment from SAP that they will keep providing 2 separate libraries? I understand maintaining/developing 2 separate libraries may be an overhead but <4 years is too low a shelf life.
Will the same thing happen with sap.m libraries 🙂 It does not look like, but especially the announcement of SDK for iOS Fiori has convoluted the things. What’s next – I keep guessing.
Can you really recommend a Front-End road-map for your clients for the next 3-4 years? Go for sap.m based fiori type applications, no wait there is a Fiori iOS SDK coming up. No Wait…
P.S. – I absolutely love the sap.m controls, they are fantastic and are the way to go forward. But I would like to know by when these will be removed.
Your feedback, inputs are always welcome.