I would envision this would make sense for microservice style APIs, not so much for client/product facing interfaces like an API tied to a web front end
I just meant something with a lower level of programming than business apps.
Usually, the frameworks themselves, “servers,” “engines,” and “drivers” would not be easy to generate with the MDA approach.
I imagine, apps and games with highly customized UI/UX would not be a good fit either.
MDA is for “boring” business apps where you would want all your screens look the same unified way. That’s where MDA shines, cuts down coding and QA effort, and allows producing massive products with many hundreds of tables and screens.
Agreed, I see this as a good fit for micro service APIs where the consumers are just other parts of a larger system. APIs for front end or consumer facing applications would likely not fit this model so well
Usually, the frameworks themselves, “servers,” “engines,” and “drivers” would not be easy to generate with the MDA approach. I imagine, apps and games with highly customized UI/UX would not be a good fit either.
MDA is for “boring” business apps where you would want all your screens look the same unified way. That’s where MDA shines, cuts down coding and QA effort, and allows producing massive products with many hundreds of tables and screens.