We’re done building our first extension with SAP AppGyver. Let’s quickly recap what we did to build the app and then let’s take a look at where to go from here.
To build the app we started with putting the UI together in SAP AppGyver using components. We also touched on the powerful feature of customizing the default components.
Then we configured the OData API as a data resource, which enabled us to pull the data into SAP AppGyver. After that it was time to bind the data using text, formula, and repeat bindings to make our UI come alive.
Finally, we could see that everything was working by pulling data from the API and displaying it in a custom UI in an SAP AppGyver application.
This is of course just the beginning. In this unit we showed you an example using one single dataset from one single OData service, but in the real world we have many SAP systems each with it’s own API, and these enable all kinds of integrations and interactions to take place. The SAP Sales Cloud API itself contains a vast number of services that can be used for different purposes.
By the way, there’s a saying "there’s an API for that" and, as we’ve seen, that often holds true!
At SAP and for many other kinds of data across industries and around the world, the availability and number of APIs are growing at a rapid pace, so keep exploring as you learn to build your own apps.