Thank you. Please share what you build with us, and get in contact if you need any help.

We are so excited that people are excited to try our project. This sounds like a great use case. Please let us know how things go, and get in contact if you get stuck.

Thanks a lot. We were really excited the day we realised we could use Lowdefy to build our own docs, and that we could create a playground where you can see what happens when you change a property.

It would be very interesting to see what your ideas and approaches to the same problem are.

We definitely find a lot of value in being able to make references to pieces of configuration that can then be used throughout the app. Then you can change something in one place, and it is consistent everywhere.

Thanks, and we hope you find it useful.

Thanks! I'll go through some things that are possible, and hopefully that answers your questions. Please let me know if I missed/misunderstood anything.

Firstly, we don't have an existing GUI that generates Lowdefy config, but you would be able to build a GUI that does that using Lowdefy. We kind of do that in the documentation, where we give you options to configure a block. So you would be able to write a "form generation app", where users define their forms.

To render the forms it would be possible (but would require a little engineering) to create a React component that renders Lowdefy config, that you could use in your production platform. (This already exists, but currently is connected to the browser router and graphql client in our "renderer" package).

Otherwise you should also be able to run a Lowdefy app in an iframe to render the forms.

Does that make sense?

Hi dreamer. Yes, it is quite simple to add new connections, they are logically separated, since we do have plans to add custom connections, much like we have custom blocks, and also to only include the connections used by the app in the server, since bundle size becomes important in serverless applications.

If you would like to contribute a connection to the project, we would be more than happy helping with that.

Can completely understand. We support both YAML and JSON. This isn’t documented that well, so we can add a section in the docs on that.

Thanks, we hope it can be useful for you.

Currently we don’t have any authentication or authorization built in, but it is the next feature we are adding. We will be adding OAuth/OpenId Connect authentication, and then you will be able to use services like Auth0 or Okta.

We also plan on providing our own user service, with group based user authorization that will integrate easily with Lowdefy apps.

+1 keep it OSS

Very much looking forward to this. An auth mechanism is a must have for my team to adopt new tools.