Request a New Feature
Design Services / Request a New Feature
Intro
We continuously enhance SAP Fiori for Android and iOS to meet the needs of SAP mobile apps and keep up with the latest updates on the respective operating systems. Do you have a new design requirement for the design system? We are looking forward to your request. In the following, we explain the journey of an initial mobile design request to an implemented component, design system guideline, and UI kit.
Step 01: Request
Do you have a design requirement you need for your application which is not yet supported by the SAP Design System? It’s just one simple step to raise a feature.
- Create a new Feature Request in MOBILEREQUEST Jira and fill out the form.
- Make sure to select the Component/s: “Fiori Design System” and “BTP SDK for Android” or “BTP SDK for iOS”.
We will get back to you within 2 weeks – your request status will change with comments.
Request form for new features or components
Step 02: Discovery
Once your request is in Status “Author Action” or “In Discovery”, Fiori Mobile & SDK representatives will contact you to refine your requirement and discover solutions together. Depending on the complexity and priority of the request, this will include different touch points:
- Call for Requirements: We will contact the requester to understand the use case and requirement in detail. We might ask for additional missing information to help evaluate the request.
- 1:1 Interviews: If your request has a higher complexity, we would like to schedule an interview with you. We will prepare an interview guide or a workshop board to understand the requirement in detail.
- Discovery Workshop: Your request might address a topic which is important to multiple app teams and use cases. In a Discovery Workshop we bring various stakeholders together to evaluate the requirements from all angles. Keep in mind: We are building a general component for SAP and not an app or LoB-specific solution.
At the end of the Discovery, the status of your request changes to “Accepted” or “Rejected”.
Keep in mind:
Once a request is accepted, the priority of delivery is defined based on the priority of this request amongst all requests at SAP.
Call for Requirement
Interview Session
Discovery Workshop
Step 03: Delivery
Once your request is “Accepted”, we will prioritize the issue in our backlog. Based on our ranking criteria, it will be pulled into a design and development sprint.
-
Soft Commit for Release: Once tagged with an estimated fix version, we plan to design and develop it for the respective release. Depending on priorities, it might change due to unforeseen reasons.
-
Scoping before Design Sprint Start: Before we plan it for a Design Sprint, we will share with you our scope and solution proposal. You can review and sign off on the requirement(s).
-
Design/Dev Sprint: In the Design and Development Sprints, we will reach out to you to validate our design and/or prototypes.
- Co-Design: In the Design Sprint, we will work closely with your designers to incorporate your user research findings and design ideas.
- Sneak Preview for New Components: Based on general interest for a new component, we offer sneak previews to get our design reviewed by stakeholders across SAP. We are looking for feedback and your use case for the respective component.