3 ms·

It really depends on what you call CRUD, but for instance, in the past, I've had frontends hiding the crud behind more "friendly" gestures. For instance, a writ

by pyrale 1y ago

It really depends on what you call CRUD, but for instance, in the past, I've had frontends hiding the crud behind more "friendly" gestures. For instance, a write such as rescheduling a sale could be done with drag&drop, reads would feed a local store of events/sales that could be browsed either as a workweek panel of which sales are happening, or as a monthly calendar aggregating sales and showing which day is a "hot" day and which day is quiet and needs more blockbusters to drive sales. Add in search features, graphs of forecasted sales and a news feed on the sales a specific user was managing. It's not that complex or fancy compared to what can be found in b2c, but it's not just a crud where users are directly tasked to update values in fields either. And yes, it could have been a crud, but I believe our users would have been worse off.

skydhash 1y ago
You can have interactivity within a single form, whithout having a whole app code humming in the background. And with the drag and drop example, I often see designers missing the obvious accessibility issue where the user can’t use a mouse.
- pyrale 1y ago
  So you’d need to select a sale, enter a change form, select a new date and validate the change. As opposed to moving the item on your planning. Accessibility issue is a good point, but the accessible way doesn’t need to be the only way.
  - skydhash 1y ago
    > So you’d need to select a sale, enter a change form, select a new date and validate the change. As opposed to moving the item on your planning. That's pre-javascript workflow. You can have your DnD without making your app an SPA. And why not have the DnD and the more complete change form?
    - pyrale 1y ago
      You're mixing two things here: having an app with more than just CRUD interactions, and making that app an SPA. My point was giving an example of an app that's a bit more featured than just some forms in a CRUD interface, not that you can only do that with a SPA. > And why not have the DnD and the more complete change form? It was, in fact, what we did.

by pyrale 1y ago

skydhash 1y ago

You can have interactivity within a single form, whithout having a whole app code humming in the background. And with the drag and drop example, I often see designers missing the obvious accessibility issue where the user can’t use a mouse.

pyrale 1y ago
So you’d need to select a sale, enter a change form, select a new date and validate the change. As opposed to moving the item on your planning. Accessibility issue is a good point, but the accessible way doesn’t need to be the only way.
- skydhash 1y ago
  > So you’d need to select a sale, enter a change form, select a new date and validate the change. As opposed to moving the item on your planning. That's pre-javascript workflow. You can have your DnD without making your app an SPA. And why not have the DnD and the more complete change form?
  - pyrale 1y ago
    You're mixing two things here: having an app with more than just CRUD interactions, and making that app an SPA. My point was giving an example of an app that's a bit more featured than just some forms in a CRUD interface, not that you can only do that with a SPA. > And why not have the DnD and the more complete change form? It was, in fact, what we did.