User talk:SaVaMu

Edit request

Please update this article as it contains outdated and wrong information. Please change to text below, your feedback and changes are highly appreciated:

SAP Fiori

SAP Fiori is the design language for SAP products, and has received a number of Red Dot Design Awards. SAP Fiori provides a comprehensive set of guidelines and tools to design enterprise software for various platforms (such as Web and iOS). These guidelines and tools are not only used in SAP products but are also made available to SAP’s vast ecosystem of customers and partners. SAP Fiori is a design language that reflects the qualities required by enterprises, such as accessibility, responsiveness, theming, and extensibility, and wraps them in an award-winning design that is elegant and as simple as the use cases allow. SAP Fiori also intends to put design into the lead meaning that personas and use cases are a precondition to any development and that high design quality is a precondition for any shipment (Design-led Development). SAP Fiori is based on the following design principles that guide the application design as well as the evolution of the design language:

• Role-based: Designed for you, your needs, and how you work
• Adaptive: Adapts to multiple use cases and devices
• Simple: Includes only what is necessary
• Coherent: Provides one fluid, intuitive experience
• Delightful: Makes an emotional connection

The design for SAP Fiori was inspired by the blue shades of the Caribbean coast of Belize, after which it was named. Belize comes in two flavors – one is light and calm, the other is a dark and intense theme called Belize Deep. Customers can adapt the Belize theme to meet their needs, for example, to apply their corporate identity by changing the colors or placing a company logo on the screen. SAP Fiori in its Web implementation based on SAP’s SAPUI5 technology comes with extensive accessibility features in accordance with the Web Content Accessibility Guidelines (WCAG) 2.0. In the SAP Fiori for iOS implementation, the iOS standards and best practices for native accessibility support are followed. A first step towards supporting the SAP Fiori user experience for existing Web-enabled applications is to apply the SAP Fiori theme to them, so that a coherent overall visual impression is achieved when they are used together with SAP Fiori apps.

One of the landmark design traits of SAP Fiori is embodied by the SAP Fiori launchpad which offers a single point of access to all SAP and non-SAP applications from a simple and personalized home page. Applications that are relevant to a specific business role can be assigned and delivered using the catalog and AppFinder. The SAP Fiori launchpad provides services for navigation, notifications, personalization, single sign-on, and system settings. Search can be used to search for business objects as well as SAP Fiori apps. SAP Fiori can be implemented through various UI technologies and platforms. The predominant client technologies supporting SAP Fiori today are the HTML5 and JavaScript based SAPUI5, and the open-source version OpenUI5, allowing SAP Fiori to run on desktop computers, tablets, and smartphones. The SAP Fiori for iOS design language allows developers to provide a user experience optimized for Apple iOS mobile devices, for which SAP provides a software development kit (SDK). Apps built using the above technologies access the back-end system via OData services.

History

SAP Fiori was announced on May 15, 2013 as a framework for the porting of applications on mobile devices (1). The initial release had few applications to start with and gradually increased over time, focusing on most-used areas of the SAP Business Suite. As of 2014, SAP Fiori is included within underlying licenses of SAP software(2). SAP Fiori 2.0 was conceived in 2015 as a next big step in the design to allow SAP Fiori to cater for power users at their desktop in addition to the previous, predominantly mobile use cases. It received the Red Dot Design Award in the category Design Concept in 2015. An extension to the design, to cover embedded analytics, received the Red Dot Design Award in the category Design Concept in 2016. In September 2016, SAP S/4HANA Cloud, and then on October 31, 2016, SAP S/4HANA became the first SAP products to fully embrace SAP Fiori, providing many new SAP Fiori apps as well as applying the SAP Fiori visual theme Belize to existing apps. On May 6, 2016, Apple & SAP announced a partnership to deliver new iOS apps and an SDK (3); the first version of the SDK was made available to customers in the first quarter of 2017. In 2017, SAP received the Red Dot Design Award (4) in the category Communication Design for its new typeface “72”, which is named after the founding of the company in 1972.

Technologies for developing SAP Fiori apps

SAP provides several products and technologies for developing SAP Fiori apps; this list mentions the main ones and does not claim to be a complete list of all relevant technologies.

Front-end technologies – independent of the back-end used

SAP Build is an integrated cloud-based solution supporting the Discovery and Design phases of software development, allowing designers and developers to collaboratively design and develop prototypes, engage end users for feedback, and at the same time learn the design process. SAP Web IDE (Integrated Development Environment) is a Web-based tool with which developers can rapidly create and extend SAP Fiori apps. It simplifies the end-to-end application lifecycle: prototyping, development, packaging, deployment, and customer extensions. It allows users to leverage wizards, templates, sample applications, drag and drop tools, and code editors. SAPUI5 and OpenUI5 are JavaScript libraries designed to build cross-platform, responsive, enterprise-ready applications, in particular for building SAP Fiori apps. The article on OpenUI5 provides more details. SAP Fiori elements increase developer efficiency, user experience consistency, and quality by applying a metadata-driven approach to application development, while allowing freestyle development where needed. These are provided to developers as templates in the SAP Web IDE. Examples of such templates are the Overview Page, the Object Page, and the List Report. Further templates are planned along the SAP Fiori road map. In addition to reducing the development effort for building UIs, SAP Fiori elements foster design consistency and help keep apps up-to-date with evolving design guidelines. SAP Cloud Platform SDK for iOS lets developers build, extend, and run native iOS apps that integrate with SAP and 3rd party systems. It provides developers the tools they need to build native apps in Swift using Xcode, and to leverage the SAP Fiori for iOS design guidelines.

Back-end specific technologies

For SAP S/4HANA, several technologies are provided to make it easier to develop the necessary OData services for SAP Fiori apps. This starts with the Restful ABAP programming model and includes integration technology such as SAP Gateway to provision OData services as well as frameworks for developing analytical apps such as SAP Smart Business or SAP Analytical Path Framework.

References

(1) (2) (3) (4)

References

External links

SaVaMu (talk) 15:50, 31 August 2017 (UTC)

Reformatting and refactoring this edit request. This in no way implies approval of your submission, but is merely for my own benefit to make the draft legible. Altamel (talk) 02:20, 2 September 2017 (UTC)

Hi @SaVaMu: Which article are you referring to? SAP Fiori does not exist on the English Wikipedia, and never has. Would you like to propose a new article? Cheers, Daylen (talk) 03:29, 16 September 2017 (UTC)

Hi @Daylen: This is somehow confusing, there has been an article on SAP Fiori, I have screenshots of it and I based on this article I proposed the changes. However, it seems to be gone. In this case, I would like to propose a new article. Do I need to do some extra steps todo so? Thanks!

I am going to procedural decline this request. New article requests should be made at WP:RA. jd22292 (Jalen D. Folf) (talk) 00:17, 22 September 2017 (UTC)