SAP Build is a great tool for building high fidelity Fiori UI5 prototypes. Here are the main features I learned while developing with this prototype app.

  1. Low cost of changes (no programming)
  2. What you see is what you get
  3. Interactive prototype with screens, process and data
  4. Fiori compatible (get a jump start on Fiori development)

Not all prototypes are created equal

Mock-ups (low fidelity prototypes) can go only so far in the user experience improvement journey. In order to succeed, you will need to develop a high fidelity working prototype. This will reduce your risk of delivering yet another sub-optimal user interface (UI) to the end-users.

Low-fidelity prototype:

  • Process map with sticky notes: You can visualize process, but not enough screen details
  • Screen mock-ups: You can visualize screens, but not enough understanding of process
  • Limited visibility on data

High-fidelity prototype:

  • Visualize: screens, processes, and data

Elements of high fidelity prototype:

  1. End-to-end process with all screens and fields
  2. Interactive elements (where users can engage meaningfully with the UI)
  3. Realistic data

You can use this prototype to explore all the features listed below.

Try Prototype: End-to-end business scenario and data:

Clone prototype: (Google Chrome works better)

Slide deck:

Link to the prototype slide deck

8 Build features:

1. Page map and Pages: Build end-to-end business scenarios:

  • Great tool to combine process and screen
  • No need to rely on Visio or PowerPoint mock-ups
  • You can add page and navigation options
  • Great visualization with navigational arrows on “page map”

There are mainly five types of screen available with predefined controls. For example: “Worklist” page, and it will provide all building blocks for developing functioning work list e.g. Tabs, Table controls, Search bar, etc.

2. Fiori controls:

  • Simple drag and drop interface.
  • Easy to visualize and arrange different controls on a page

There are eight types of controls:

  1. Action: Button, breadcrumb, menu, etc.
  2. Tile: Tile, Tile content, etc.
  3. Containers: Tab, tab bar, etc.
  4. Display: Bar, Image, Item attribute, etc.
  5. Layouts: Form, Grid, Box, etc.
  6. List: Tables, feeds, etc.
  7. User inputs: text, buttons, drop downs, etc.
  8. Charts: Bar-chart, Line charts, Micro chart, etc.

You can manipulate the control parameters on the right section of this screen

3. Realistic data:

Bring your own data from a spreadsheet or create a model and populate the data on your own. You can bring many types of data and build relationships. You can find many sample data models from the Build library as well.

Edit sample data on the fly or update data with spreadsheet (download/upload) functions. This is a really easy to use interface. You can also create data relationships.

4. Images: Branding, icons and visualization

You can upload your own images. You can upload custom icons and use them for your app. Images can be used for branding (e.g. logo) or as a part of an app. e.g. product image. You can use file options in the Project Workspace to manage these images.

5. Collaborate

Share your project with you team/users. Your team members can edit the project, add comments, etc. It’s easy and intuitive.

The team can collaborate in the development cycle, testing cycle and getting feedback. This discussion allows everyone to be on the same page.

I wish there was a notification feature or indicator that someone added a comment. (Like Google docs)

6. Study/Feedback

Create your own study and invite users to explore the prototype and have a meaningful interaction. Users will provide you with realistic feedback and you can also measure users’ interaction with the prototype. Example features: Heat-map, statistics and user flow.

Create study: Perfect way to coordinate with the team. Let users play around and have a feel for the solution. If you have to explain a lot, then you didn’t do a good job in designing the user experience.

7. Personas

Personas is a great feature to understand users and it helps keep focused on them throughout the project. This can be integrated as a part of your change management and/or training efforts.

8. Export to SAP WebIDE

When you are ready to start development, simply download the prototype using the “Share” function. The downloaded file includes all screen elements.

Voila! You can design a functioning prototype without writing a single line of code.

A few bumps:

  1. Understanding the data object and relations is not intuitive. Especially when users like me want to build very complex, life-size data structure. Suggestion: Think through your data model esp. hierarchical (e.g. header and item data) relationship between tables and fields before you start assigning data to fields.
  2. No versioning. It’s hard to go back once everything is saved. Suggestion: Create a copy or use download functionality to create back-ups.
  3. Only five projects per free account. If you want to work on more projects, contact your SAP representative.

There are many more features and functionalities available in Build, but the above highlighted features will help you take the first steps in your long and fun-filled user experience (UX) journey.

I look forward for your feedback and new tips and tricks through community.

Have fun!

Also posted at:

Not logged in
  • Anonymous   3 years ago

    And it has a LOT of weakness:
    1) WYSWYG editor needs improvement because it’s realy painfull to access to deep component
    2) Prototype get often buggy. And you can’t fix it (copy the page doesn’t change anything). I had to edit a page without seeing it on WYSWYG editor, by refreshing the preview
    3) You can’t edit xml prototypes files in order to fix the buggy projet
    4) You have to choose a projet type without knowing the concequences
    5) You can’t copy a page out of your projet to re-use it in an other projet
    6) Not all (major) Fiori component is avaliable
    7) Navigation on prototype’s data is not clear and/or not working
    8) You can’t see pop-up or dialog windows wihtout knowing where they are used
    9) You can’t delete pop-up or dialogu windows if it not used
    10) Manys other weakness I can’t remember…
    SAP fix that and could really be an master piece on Fiori adoption….

  • Thomas DUBREUIL   3 years ago

    Hi Taryck,

    Thank you for the feedback. All these issues are being addressed with highest priority by the BUILD development team.
    If you have further feedback , we would appreciate that you also send a copy to us directly so that we can answer in a timely manner.
    our mailbox:

    Best regards

  • Anonymous   2 years ago

    Greetings, fellow UX Experts!

    I’m very delighted to use SAP Build. It helped me in many UXDs I propose to my clients but most of them expect me to give a “better” UXD. This is where I find SAP Build to lack.

    True, it was designed to be compliant to the Fiori standards but I find the tool limited in many aspects. I cannot create certain combinations of UI controls that are compliant to the standards also.

    There were times that the client wish to have a grid table for an app that is meant for a desktop only; I cannot see this option in Build.

    There are scenarios when we need to show a page scrollable downwards or upwards but, somehow, the Build seem to lack this rendering effect (or was it a bug?).

    Needless to say, I look forward (in the near future, like this year?) that SAP Build can simulate all possible combinations of SAPUI5 controls.

    After all, we need to show to a client what an app will look like exactly how it will be rendered if it’s already built using SAPUI5, right?