I used to work on a similar system 20 years ago that leveraged xml to define forms, then generic transformation system written in PHP generated pages from it. H

I used to work on a similar system 20 years ago that leveraged xml to define forms, then generic transformation system written in PHP generated pages from it. Here it's json to define view and some internal schema. It's good when your requirements are fairly stable, each view falls into a well known category. Meaning - it's great for an app that's basically a catalogue, but less so for apps with more complex user interactions. you know what they say... "All problems in computer science can be solved by another level of indirection" , in reality those levels can be leaky and cause debugging problems.