I wanted to get feedback from users on the behavior of the new action on the library screen. Currently, this is contextual and creates a new song on the Recent and Songs tab, or it creates a new group type if on a group tab (setlists, collections, genres, etc). The question, if you tap a setlist or collection and view the songs under it, should the new action create a new song in this case, or create a new setlist or collection? Currently, it creates a new setlist or collection (so it behaves the same regardless of whether a group has been selected). I received feedback suggesting that it should create a new song in this case, so I wanted to hear more opinions. It's also possible to change the behavior to show a popup to let the user choose, but this does then take an extra tap.

Thanks,
Mike

Imho it's perfectly logical and consistent as it is today: a list of items is shown and the "New" button above this list creates a new element of the same item type and adds it to the list that is currently shown.
Furthermore: I almost never use the "New" button to create a song. I create songs most of the time by by entering a collection and start an import.
My most frequent use of the "New" button is for creating a new setlist or a new collection.

That was my feeling as well, so I just wanted to hear the thoughts of others. Thanks!

Mike

Like itsme, when I am in the Setlist menu or looking at a setlist's songs, clicking on New I expect it to do what it does, create a new setlist. Likewise with Collections, New should create a new collection. When I am in the Songs menu clicking on New I expect it to do what it does, creat a new song, although personally I create songs outside of MobileSheets or occasionally I use ... > Add a placeholder. I am happy with MobileSheets as it it performs now.

Same here.

I've personally found myself in both situations: wanting to create a new setlist or adding a new song. You could probably support creating a new song from those menus by long pressing the add button

I'm not opposed to supporting a long press to add a new song in that scenario.

Mike

I'm perfectly happy with the current behaviour.  I'm not opposed to the long press suggestion, but I'm not sure I'd ever use it.  My new songs are always created with import.

IMHO, 
the current workflow works as someone would expect, that´s ok.

e.k.

The post of user ItalianOrgan motivated me to check again.
For my first answer I only looked at the tabs Songs, Collections and Setlists. "Songs" shows a list of songs, "Collections" and "Setlists" show a list of groups. So I wrote:
"Imho it's perfectly logical and consistent as it is today: a list of items is shown and the "New" button above this list creates a new element of the same item type and adds it to the list that is currently shown."

This is NOT the case when a group (a collection or a setlist) is displayed. In this case the content of the group is shown, which is a list of songs whereas clicking "New" creates a new group. This is somehow inconsistent and confusing. To see the newly created item the user has to leave the current window and navigate "one step up in the navigation tree". So I understand and support now the request (that propably triggered this discussion) that the "New" button above an open group should create a song to behave exactly the same as elsewhere. Creating a new group (if it turns out that this really makes sense when the content of a group is displayed) should be a different user action. If it is triggered by a long press, a second button or something else is a design decision.

Again: in more than 10 years of using MobileSheets, adding thousands of songs I rarely used the "New" button, probably never with an open group. So I don't care at all if the outcome of this request and discussion is changing the behaviour of the "New" button or if it stays as it is today.

As I wrote I never saw an "issue" with the current situation,
I always related "new" to the choosen or active tab, never to the content of a tab.
So I used "new" always for creating new collections, setlists,.....never for songs,
which I add always by "import".

But, as itsme wrote, there is a possible different approach.


Is there an advantage if I create songs by using "new" instead of "import",
or when would this be a better way? (Maybe I can improve my workflow.....)

e.k.

The only reason to use the New option is either if you want to be able to add more metadata to the song being created than what is available through the import settings dialog, or if you need to set up the files for the song differently than what is supported by the import (such as creating a new text or ChordPro file, adding a blank page or a template, etc).

Mike

THX, got it!