JSON2App VS polyapp

https://gitlab.com/polyapp-open-source/polyapp is a self-hosted, MIT-licensed form builder with reporting I created. It can be adapted to handle asset tracking & relicensed under AGPL.

Basically, it works by reading the JSON; using https://gitlab.com/polyapp-open-source/polyapp to recursively create form HTML, validation, and schemas; and using polyapp again to import the data contained within the form.

A lot of people will jump at this and say, "but without a developer, you can't calculate X Y Z!" or "those tools aren't flexible enough to replace the app I'm building!" Obviously someone needs to code everything, but in large developer ecosystems someone has probably already coded something just like what you're writing and your job is reduced to configuring that thing. Most of the code I used to write was configuring components someone else wrote on the front end and transforming data from the database into the UI and back again on the back end. Even those things are just configuration. HTML is configuring components defined by the HTML standard. Typing out a data model in C# and setting up Entity Framework is just a way to configure the .NET framework. You could write a UI with all of the different choices for HTML and Entity Framework model choices as a form, and have someone select from the list of choices and all of that work would be poof - gone. Incidentally, this is sort of how Polyapp works.