Re:Ask HN: Why Isn't the Construction of CRUD Web UIs 90% Au...
by paskster on Sunday October 08, 2017 @06:31PM
(#15430381)
It seems that folks at HN look down on so called "CRUD" apps. But the truth for most CRUD apps is, that a lot of thought went into building these apps and they have a lot of important parts, whose construction cannot easily be automized. Good examples are:
- Certain inputs might trigger other actions (integrity checks, sending an email, notifying another users, etc.)
- The UI / UX needs to be optimized for the specific Usecase of the app
- There are unlimited options for filtering or ordering items, and the choice of options depends on the specific Usecase
- A lot of apps need Cronjobs in the background to support certain workflows (notifying a user if a certain input has not been done in a certain time)
- There can be rather complex rules on who is allowed to create, update, delete or view certain items
- AB tests and Analytics need to be supported for a lot of Tasks / Views
- etc...
I cannot imagine a "CRUD" framework, that supports all of these issues. It would basically just be another programming language ;)
- Certain inputs might trigger other actions (integrity checks, sending an email, notifying another users, etc.)
- The UI / UX needs to be optimized for the specific Usecase of the app
- There are unlimited options for filtering or ordering items, and the choice of options depends on the specific Usecase
- A lot of apps need Cronjobs in the background to support certain workflows (notifying a user if a certain input has not been done in a certain time)
- There can be rather complex rules on who is allowed to create, update, delete or view certain items
- AB tests and Analytics need to be supported for a lot of Tasks / Views
- etc...
I cannot imagine a "CRUD" framework, that supports all of these issues. It would basically just be another programming language ;)