Background A user is presented a panel with a big listing. There is a default view, but the user can also filter the listing to refresh the "panel". There are two sequential and almost dependent filtering options (E.g: filter by "flower type", then filter by "color"), and the selection will consist on checkboxes.
Every time the user enters the panel, s/he is able to see the default view, filter by hand to refine the listing OR change the view to a pre-saved filter (or pre-set, or favorite).
I've considered two options (can be more, if you help me) to create those pre-set filters. Which option do you think will offer a better user experience?
Option 1: Trigger with a permanent button... Provide the panel with a button to see the list of "My pre-set filters". Inside the view, provide a button to "Create new filter", which opens/expands a view of the 1st filter: flower type. After clicking "Next", the 2nd filter: color, is shown. ---this is an easy CTA, but the problem is to render an overlay or expandable option to show the creation flow with the same filters that are presented when filtering by hand.
Option 2: Let the user make changes and then invite to save... Only after the user has completed a successful filtering (filtered by flower type an then by color) and hit the "Update listing" button, a pop-up or modal will invite the user to save the recently applied set of filters. The panel will have a button to see the list of "My pre-set filters", without the button to create it. (this option may contain a short instruction of how to create a pre-set from zero, as there is no CTA to trigger the action directly). ---this has no direct CTA, but the action will derive from a wanted filtering action triggered by the user. (although can be annoying when the user is only exploring and does not want to save each set of filters s/he is playing with)
Thanks for your feedback!!