I am trying to create an understandable and clear UX design for a schedule designer web app.
Imagine we have categories of followers and marketing emails to send. Also we have a schedule: each day we are going to send some pool of emails of some category.
Here is the data model:
Sometimes we need to move an email of some category to another day on the schedule, so
emails on a day ≠ emails of a Followers category.
My current design:
The primary call to action is a Generate schedule button. We suggest that the user arrange categories by day; the user then generates the schedule. If the user needs to move an email to another day, it has to be done on another screen.
Question: If the user moves an email to another day, they have to re-generate the schedule. All edits to the previous version will be lost. What is a more elegant way to help the user create a "ready to use" schedule on the fly?
