This Week in Fiori (2014-40)
Another week, another set of Fiori links. Let’s get to it!
Fiori App Reference Library app, via Luis Felipe Lanz Well it was bound to happen, and I’m celebrating that. Luis tweeted a link to a lovely Fiori app, the Fiori App Reference Library, which contains details on the 300+ Fiori apps so far. Of course, the original meta Fiori app, the SAP Fiori App Analysis application (which I mentioned in TWIF 2014-31) is still going strong – find out more about this in this 5 min video “The SAP Fiori App Analysis application“.
But what about this new app from SAP (rather than from me)? Well, there are a couple of parts of the URL (https://boma0d717969.hana.ondemand.com/sap/fix/externalViewer/) that suggest to me that it’s possibly temporary, or still in development (there are some active debugger statements in there too), but apart from that, it’s a fine example of a classic Fiori app and uses a 1.24 runtime of UI5. I’m tempted to dig in right now and start exploring how it’s put together, but I’ll leave that for another time. I’ll just point out that the data it uses is from a proper OData service which is in itself more useful than you might think – an official machine-readable detailed list of Fiori apps from SAP. Let a thousand consumer apps bloom!
SAP CodeJam on RDE at Ciber NL organised by Wim Snoep SAP River RDE, or to give it its new name SAP Web IDE (hopefully it won’t change again :-) is an important topic to understand in the world of Fiori. It’s what many developers (although not all) will be using to manage Fiori apps from a creation and extension point of view. RDE has been a long time in gestation but today’s incarnation is very accomplished and those looking to understand what SAP’s approach to software management in the Fiori age is, need to spend some time investigating this.
One of the “Dutch SAP Mafia” members Wim organised an SAP CodeJam on RDE which looked to be a great success. The developer ecosystem is not just about the languages (say, JavaScript) and frameworks[^n] (UI5) but also about the tools and environments within which one works. So this CodeJam was ideally suited to learning more about SAP’s environment. The day saw developers build Fiori applications in RDE, and I was happy to see that our TechEd hands-on session content CD168 Building SAP Fiori-like UIs with SAPUI5 — which was created for last year’s SAP TechEd events but has seen action ever since — was put to good use for this event too.
[^n]:actually one should refer to UI5 as a toolkit rather than a framework, for reasons too long and detailed to go into here :-)
Introduction to SAP Fiori UX by SAP I’ve written about this course from Open SAP before, most recently in the previous TWIF episode TWIF 2014-39. Well, I thought I’d give a quick update on my perspective … to say that I’ve abandoned the course. Fiori is a huge topic, and one can’t expect a single course to cover everything. But I did expect some UX content, as it’s an incredibly important aspect of the Fiori experience. Unfortunately I didn’t find any, and I noted that I wasn’t alone in this regard either.
With the combination of this issue and the as yet unresolved issues from Week 2, I decided that give up on the course and I’d devote the time I’d allocated for study to other more UX/UI related matters, in particular by studying further the SAP Fiori Design Guidelines that I wrote about in TWIF 2014-28 along with details of the latest responsive controls in the UI5 toolkit. Whether you’re following the Open SAP course or not, I’d encourage you to do the same, too.
I must say that I’ve not given up on Open SAP as a whole – in fact I’m eagerly awaiting the next Fiori related course … now that Fiori installation and configuration is out of the way with this first course, it could be full steam ahead for the UX part!
Update 20 Oct 2014: Since this post, there has been some discussion internally, on various email threads and also publically here and on Twitter. And today SAP posted “Help Shape the Next SAP Fiori Course” which acknowledges the issues with the lack of UX content and solicits input to determine the content for the next course. Well done Open SAP! This is a conversation in action. I’d encourage you to go over to the survey and add your thoughts.
Until next time, share & enjoy!