Since it was a holiday week, I did not get as much done as I usually do, but I still managed to make some progress on one of the features, undo and redo functionality for both delete and move actions.
Setting this up took some work, especially building the stack system that records actions whenever a card is deleted or moved. Once I got undo working, getting redo up and running was a lot easier since it is basically the reverse process. At first, undo and redo only worked for single-card edits, which was fine for testing, but I quickly realized users would need the same for multi-select actions.
To fix that, I added new undo types, deleteMultiple, moveMultiple, and archiveMultiple, and included them in the main undo/redo functions. It ended up being pretty similar to how I handled the single-card version, just with a few more checks to handle multiple cards at once. Now, users can easily undo or redo both individual and bulk actions, which makes managing the board a lot more forgiving and intuitive.
Next week, our focus shifts toward getting ready for user testing. We will mainly be polishing the app and preparing a deployable version that uses fake data, since deploying the actual model would cost money. However, we will also have a few in-person testers who will get to try the model itself, which will give us a chance to see how accurate it is and whether any adjustments are needed.
