Early versions of Set List Maker had "set lists," but I renamed that to "shows" when I added fields for contact and payment information. This makes it more clear that if you want to play the same songs at two different events, you should duplicate the "show" rather than reusing the same "set list," so that you can enter both sets of event information. This also avoided the confusion that some people had about a "set list" containing multiple "sets" -- some people were creating three set lists for a show with three sets, rather than one set list with three sets (a.k.a., two breaks).
When I launched BandHelper, I went back to "set lists" in that product, because BandHelper lets you enter event information separately and attach a set list to an event. So it is more intuitive to enter event info for each event but reuse one set list across several events.
Now I'm considering renaming "shows" back to "set lists" in Set List Maker again. Here are some advantages:
- It would be easier for new users to figure out how to make a set list, since there's nothing called "set list" in the app currently
- It would be easier for me to share code and documentation between the two products
And the disadvantages:
- Current Set List Maker users would have to get used to a button labeled "Set Lists" instead of "Shows" (but the functionality wouldn't change)
- As before, some confusion about where to enter event info when reusing a set list
- As before, some confusion about the "set" vs. "set list" terminology
What do you think?