banner image

The perks of prototyping in Build

Ensure your app meets user needs

  • Arne Goudeseune
    Arne Goudeseune

As explained in the first blog of this series, Build is a comprehensive set of tools that helps you create better software applications by learning, prototyping and gathering inspiration and feedback. In this blogpost, we explain how prototyping in Build works. 

Why prototype?

A prototype is a draft version of your application that allows you to explore the feasibility of your ideas and show the intention behind a new design concept. It can be a sketch, a wireframe or even a fully functioning site. Prototypes enable you to gather feedback during the design process, before you invest time and money in the actual development of your application. 

Low-fidelity prototyping

After you’ve generated ideas about how your application should work, it can be very useful to visualize them. Build provides you with printable templates for different devices, so that you can easily draw a sketched design of your prototype. Once you’ve finished, simply scan your sketches and import them into Build.

Creating low-fidelity prototypes enables you to:

  • provide a draft version of your designs
  • get fast results
  • create a first user test
  • gain in-app feedback from your team

High-fidelity prototyping

Once you’re ready to finetune the user experience of your application, use Build for high fidelity prototyping. With the SAP Fiori look and feel, developing the layout becomes a breeze for your designers. Alternatively, use one of the various templates to convert an existing prototype into your own design and to import company data into your prototype. 

The next step: feedback

Throughout your project, you can easily invite team members or end users to view, test, and add notes to your prototypes. Gathering feedback helps you verify whether your focus is wide enough, and whether your design actually addresses the users’ needs. A useful feature for this is the heatmap, which allows you to track the places where team members or end-users click. This information serves as a starting point for discussing why they tried to click certain places in your design, and adapt it to be more effective. 

Straight to development

Build generated the code behind high-fidelity prototypes, so you can easily share it with developers through the Web IDE tool. But even sharing a low-fidelity prototype, which doesn’t have any code, can prove very useful: it gives developers a perfectly outlined idea of how the application should work. In this way, Build supports your design thinking and doing process. 

Looking for more information on Build? Our experts are glad to help.

We are happy to share our knowledge with you

Be the first to read how Flexso tackles real-life scenarios and make the most of our tips based on experience and practical cases.