4 ms·
Excellent insights in this article. I've approached building web apps as data models. It works really well for our team. This was how / why we started to devel
by gervwyk 4y ago
Excellent insights in this article.
I've approached building web apps as data models. It works really well for our team. This was how / why we started to develop Lowdefy [0], to express a web application with a data model. We've been experiencing the benefits of this - I really need to start writing about it.
Writing this app model in json or yaml might not be ideal start, but once you have that creating a IDE / GUI builder / next thing on top of that becomes really a simple task while reaping all the benefits of defining an program / app as a data model.
[0] - https://github.com/lowdefy/lowdefy https://github.com/lowdefy/lowdefy
- panstromek 4y agoThat looks pretty cool, I will look at that. I already had this idea many times (and I think anybody who done some web stuff must have had, too), but it always felt apart when you consider all edge cases you want to handle differently.
- gervwyk 4y agoThanks. Yeah, we’ve been building all kinds of things. Anything form dashboards, crud, public forms, ver advanced forms with complex validation and logic and even full MRP and CRMs. Of course there is an egde, for now it’s stuff like pub/sub, server oauth etc. But mostly seems like these edge cases can be supported as features later. It seems like the abstraction is working really well thus far, separating the business logic, into operator functions, from the app and backend stuff is really key to this. Really looking forward to the next phase where we get to create all nice programs tools in front of the program model to provide a superior dev ex :)