Ondrej Holzman Apple on Thursday concluded another significant collaboration in the field of enterprise software. He will now collaborate with the German company SAP on the creation of new developer tools and iOS applications that will use the SAP HANA cloud platform.
In addition to the new SDKs, the new design language SAP Fiori for iOS will also appear, as well as the SAP Academy for iOS, which will provide the necessary tools and training. All news should be launched by the end of 2016.
The German company SAP, which deals with enterprise resource planning, is going to develop a native iOS application for running companies, using the Swift programming language and the aforementioned Fiori interface.
Looking forward to working with @BillRMcDermott @SAP on new iPhone & iPad apps. https://t.co/7QcMCEiPKY pic.twitter.com/iRZzEZ3EPR
- Tim Cook (@tim_cook) May 5, 2016
"This partnership will transform the way iPhones and iPads are used in businesses, as they serve the innovation and security of iOS with SAP's deep knowledge of enterprise software," said Apple CEO Tim Cook, who said SAP is an ideal partner with its prominent position in the enterprise space.
God I'm at a loss for words :-( I'll try to summarize because this would be a long shot…
First, they could modify SAPGui to not use ActiveX elements on Windows and unify this frontend for all platforms, and then play with Fiori (which are apps written using SAPUI5, which is kind of like JQuery/Node.js). The truth is that the manager sees and reacts more to the graphic on the mobile than the fact that the developer has to spend X hours developing in today's unsatisfactory development environment for that stupid graphic...
Furthermore, they could release elements for the design of Fiori applications, for example, for Sketch or other programs, because designing an application in PowerPoint, as they demonstrated during one course on open.sap.com, is laughable...
Update: I'm currently working on PDF forms in SAP again (after a long time) and remembered how the collaboration between Adobe and SAP turned out...
You are practically editing something in an editor connected via "OLE2", where it can happen at any time that the WYSIWYG editor can spoil the resulting XML and the whole form is... Right there... (Even in version 10.4, I'm currently looking, version 11.0 SP2 was released this March, I'll try push it to customers and we'll see what has improved)..
The JavaScript editor is laughable, occasionally able to highlight key commands, but that's about it. The debugger is only accessible when using the full Adobe Acrobat, which no one buys for me to work with, so I have to dump variable values via messageBox (the fact that no one buys it for me is not Adobe's problem, on the other hand, if I'm developing a form, the debugger should be present in the tool, in which I develop it).
Shall I continue?
No, I don't want to complain, despite the above I think that PDF forms are a step forward, I'm just demonstrating my experience of how such cooperation with SAP turns out :-(
But in connection with support.sap.com moving to Fiori Launchpad, I might expect it to finally start working under Safari, which in test mode worked beautifully and after the "official" launch I won't do anything there :-/