Many of the times, I just want to jump into a blank project, play around, and experiment. I never name a project until it has some structure and I have some sense of what it will be. Forcing me to name the project up front makes me do two of one things: A) give the project a generic date-based name which is hard to differentiate easily in a list or B) give the project some random meaningless name that I'll likely change later on. Neither of these approaches are optimal (or necessary) imo.
As for the saving, Studio One should prompt after the project starts, asking me whether I want to save it, only when I perform an operation that would require the save (start new project, close app, etc). This is a pretty standard process for most applications - not requiring an initial save and prompting user later. Studio One's caching and backup processes should be stable enough that a non-saved project could be recoverable in the event of something like a crash.
Forcing the naming and saving before starting the project generates this cognitive overhead and friction right up front that I don't have with other DAWs. Studio One is amazing, and currently my DAW of choice, but this UX pattern affects me every time I just want to get in and create, which is what this is all about, no?
