Album Creation Flow

[andrewvy]

This issue will hold some of the notes around the UX for Album Creation.

---

I am thinking of 3 states:

• Draft Album (unpublished)
• Processing (may not have to be displayed to the user as an explicit state)
• Published Album (available for purchase)

Current internal states:

• pending - Draft album?
• submitted - Draft album is in the process of being published. Submitted to the transcoding pipeline.
• transcoded_failure - Album failed to transcode.
• completed - Album is in a publicly consumable state.

Ideal flow:

1. I create an album, it gets saved as a draft album.
2. When I feel ready, I can publish the draft album.
3. The act of publishing starts all the internal workflow necessary to publish the album. (transcoding/etc.)

Questions:

• Does it make sense to go directly to a published album without having an intermediary "draft" state?