I'm not sure I like the idea of not applying filters when viewing a setlist's songs on the library screen. That is inconsistent with all the other tabs and would probably be very confusing to people. I can certainly see times where users might want to find just one song inside a large setlist and either load that one song or jump to that song.
As far as persisting the filters when editing setlists, that brings up a couple of issues that I would need feedback on:
1) The screen that is used for editing setlists is basically the same screen that is used for editing any group of songs. Would the filters be persisted for all group types or just setlists?
2) Should the filters be maintained and persisted separately for every group type? Furthermore, if you set filters for one setlist and then edit a different setlist, should those same filters be applied? Or do I have to persist filters per setlist as well, as that would significantly drive up the amount of data I have to store. Or do I just reset the filters if a different setlist is edited?
In this case, I'm just talking about persisting them across screens in the app. Are you also wanting these persisted between loads of the application? With all of the different supported filters, I'm probably going to need to add a new database table to store everything.
As far as persisting the filters when editing setlists, that brings up a couple of issues that I would need feedback on:
1) The screen that is used for editing setlists is basically the same screen that is used for editing any group of songs. Would the filters be persisted for all group types or just setlists?
2) Should the filters be maintained and persisted separately for every group type? Furthermore, if you set filters for one setlist and then edit a different setlist, should those same filters be applied? Or do I have to persist filters per setlist as well, as that would significantly drive up the amount of data I have to store. Or do I just reset the filters if a different setlist is edited?
In this case, I'm just talking about persisting them across screens in the app. Are you also wanting these persisted between loads of the application? With all of the different supported filters, I'm probably going to need to add a new database table to store everything.