I've been looking for a no-code solution to quickly build webapps on top of APIs exposed for mobile apps. I've been documenting OpenAPI specs[0], and evaluated most Nocode solutions in the market, trying out the "Rest API" integration in all of them.
Did the same for Budibase, and here's some feedback (on just the REST API integration):
2. Provide html input placeholders in all fields. Understanding whether "Url" field refers to the base URL, or a complete endpoint URL (different platforms treat this differently) is confusing. Even things like whether or not it needs a trailing slash. Having a placeholder with a standard API (such as OpenAPI Pets example) makes it easier.
3. The Jinja template format is great (I don't think any other platform came close to what this simple solution does) - but it isn't documented well enough. The API endpoint creation form should guide me to it as a possibility - without me having to look for it.
4. Really liked the auto-schema detection.
5. The forms really need to be more explanatory. ("Parameters" could refer to HTTP body parameters, or REST API parameters, but it's unclear)
6. Rough edges such as [1] should either be fixed, or automatically be disallowed.
As an aside, I'm curious why the entire nocode industry docs are on GitBooks.
We are actually currently planning work to greatly improve the experience of the REST API integration (including better docs) - due to it being such a fundamental part of building any software.
1) Good catch, we will fix that right away.
2) Great suggestion, this will definitely help guide the user.
3) Very valid - there will be a more wizard based experience for the REST connector soon. It's quite manual at the moment. Appreciate that you liked the handlebars templating experience!
4) This is a big feature for budibase - we try and auto generate as much as we can, to make the dev experience faster.
5) More docs and guidance around this is on the way with our "blocks" feature, which should make building forms a much more pleasant experience.
6) as above.
Gitbooks is a pretty nice platform - it takes a lot of the effort out of creating/designing docs and they recently updated their editor, so we are very happy with it!
Did the same for Budibase, and here's some feedback (on just the REST API integration):
1. Please link the (?) icon to the correct place in the docs. eg, if I'm on the REST screen, it makes more sense to send me to https://docs.budibase.com/quickstart-tutorials/crud-app-with..., instead of https://github.com/Budibase/budibase/discussions/
2. Provide html input placeholders in all fields. Understanding whether "Url" field refers to the base URL, or a complete endpoint URL (different platforms treat this differently) is confusing. Even things like whether or not it needs a trailing slash. Having a placeholder with a standard API (such as OpenAPI Pets example) makes it easier.
3. The Jinja template format is great (I don't think any other platform came close to what this simple solution does) - but it isn't documented well enough. The API endpoint creation form should guide me to it as a possibility - without me having to look for it.
4. Really liked the auto-schema detection.
5. The forms really need to be more explanatory. ("Parameters" could refer to HTTP body parameters, or REST API parameters, but it's unclear)
6. Rough edges such as [1] should either be fixed, or automatically be disallowed.
As an aside, I'm curious why the entire nocode industry docs are on GitBooks.
[0]: https://stoplight.captnemo.in/
[1]: https://github.com/Budibase/budibase/discussions/1385#discus...