With the recent release of SAP Screen Personas 3.0 SP6 and the Slipstream Engine for mobile rendering, we have been hearing lots of excitement from customers, partners, and colleagues, along with questions about what’s next in our roadmap. In this blog, I will cover the current state of SAP Screen Personas, the latest status about SAP S/4HANA, SAP Fiori, and SAP Screen Personas, and our development plans going forward.
In December 2017, we released the Slipstream Engine component, which allows SAP Screen Personas to render flavors on phones and tablets, as well as the desktop. This had been a long-standing request from many customers, which explains the large number of downloads since the release. Now, SAP Screen Personas is a fast and easy to deliver Fiori-inspired mobile apps with minimal coding. In addition, we have many Fiori-inspired flavors in our Flavor Gallery, to further accelerate app development.
SAP Screen Personas, SAP Fiori UX, and SAP S/4HANA
You already know that SAP Fiori is the user experience for SAP S/4HANA. What you also need to know is that a significant and growing percentage of SAP S/4HANA customers use SAP Screen Personas to simplify their classic screens. One global system integrator told me that SAP Screen Personas is now a part of almost every SAP S/4HANA migration project they sell.
There are several ways to achieve the Fiori UX.
- Download the Fiori apps you want from the Fiori App Reference Library.
- Use a classic screen rendered with the Belize theme (SAP Fiori theme for SAP S/4HANA)
- Simplify a classic screen with SAP Screen Personas
- Start with an SAP Screen Personas flavor from the Flavor Gallery
A question came up in a recent meeting with the CIO of a large consumer product company about why, if SAP Screen Personas is so critical to SAP S/4HANA, is it not included with S/4HANA? The answer has to do with development and release schedules. Each of the respective solutions has its own development timeline, dependencies, and internal and external stakeholders. While we align our efforts closely with the SAP S/4HANA team, each of us will continue with our own release schedule and SAP Screen Personas will remain an add-on.
One area of very tight alignment is our support commitment. We now support SAP Screen Personas for five years from the latest service pack, which is the same as the SAP S/4HANA support commitment. So, you can move forward with your UX transformation with the confidence that SAP will support your complete environment, even if you use several different SAP solutions.
As always, we prioritize our product roadmap based on feedback from customers that rely on SAP Screen Personas to simplify the way access their SAP screens. We also integrate feedback from partners, many of who have experience implementing SAP Screen Personas in dozens of clients. In some cases, we also consider input from companies that want to use SAP Screen Personas but do not, because it lacks some key capability that they need (mobile is one example).
Our main focus area for the coming year are:
- Making the mobile rendering more robust to handle more transactions
- Adding the SAP Screen Personas editor to the Slipstream Engine, so you can have a full “what you see is what you get” development environment for mobile flavor development.
- Including a preview for different mobile devices into the SAP Screen Personas editor
- Exploring a cloud deployment model to reduce the back-end dependencies
In 2018, we are planning to release two service packs. The functionality is largely set for SP7, but we are still looking for your ideas on what you would like to see in SP8, beyond what we have stated on our roadmap slide. We will share more details at SAPPHIRE and TechEd this year.
See the complete SAP Fiori roadmap (SAP Screen Personas appears on pages 91-93).
Download SAP Screen Personas 3.0 SP6, including the Slipstream Engine
Some resources to help you on your way
* This blog and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.