Customers
Broadly, our customers are users of Spotify and/or Apple Music.
The two primary subsets of our are:
power users of a particular platform
users that use both Spotify and Apple Music (multiplatform users)
We also refer to general users as anyone who uses our platform and may fall into one or both of those subsets.
Needs
Power users need...
n1. an interface that lets them build smart playlists quickly and intuitively
n2. tools to let them build smart playlists based on arbitrarily complex custom logic schemes
Multiplatform users need...
n3. a near-unified experience on accounts of different platforms (specifically Spotify and Apple Music)
General users need...
n4. a way to easily manage all of their previously created smart / multiplatform playlists
n5. to see their playlists automatically updated
Requirements:
Our platform shall...
r1. provide a web-based interface
r2. provide the ability to design playlist configuration logic using drag and drop components and connections
r3. provide the ability to select components to add via an interactive multi-step menu system
r4. autogenerate meaningful component names for the user
r5. provide feedback and warnings on invalid configurations, or configurations containing sections with no impact on the configuration
r6. provide a real-time preview of what songs the playlist will contain based on the current configuration
r7. provide the ability to add source components from artists, albums, playlists, liked tracks, specific tracks
r8. provide the ability to add filter components by liked, explicit, year range, duration range, top 100 most played (accepting one input stream)
r9. provide the ability to add logic gate components such as and, or, & not (accepting any number of input streams)
r10. provide to ability to maintain the same playlist across both Spotify and Apple Music (multiplatform playlist)
r11. provide the ability to build multiplatform playlists with source playlists on both Spotify and Apple Music simultaneously
r12. provide ways to manage previously-created smart/multiplatform playlists i.e. edit, delete, relinquish options
r13. be capable of regenerating smart/multiplatform configuration graphs of previously created playlists based on some standard (the position of components may differ for the user's original layout, but the topology / connection scheme will match)
r14. periodically regenerate all smart/multiplatform playlists based on their configurations. This is necessary if source components change (for example if an artist releases a new track)
Needs Requirements Mapping
n1. an interface that lets them build smart playlists quickly and intuitively
r1. provide a web-based interface
r2. provide the ability to design playlist configuration logic using drag and drop components and connections
r3. provide the ability to select components to add via an interactive multi-step menu system
r4. autogenerate meaningful component names for the user
r5. provide feedback and warnings on invalid configurations, or configurations containing sections with no impact on the configuration
r6. provide a real-time preview of what songs the playlist will contain based on the current configuration
n2. tools to let them build smart playlists based on arbitrarily complex custom logic schemes
r7. provide the ability to add source components from artists, albums, playlists, liked tracks, specific tracks.
r8. provide the ability to add filter components by liked, explicit, year range, duration range, top 100 most played (accepting one input stream)
r9. provide the ability to add logic gate components such as and, or, & not (accepting any number of input streams)
n3. a near-unified experience on accounts of different platforms (specifically Spotify and Apple Music)
r10. provide to ability to maintain the same playlist across both Spotify and Apple Music (multiplatform playlist)
r11. provide the ability to build multiplatform playlists with source playlists on both Spotify and Apple Music simultaneously
n4. a way to easily manage all of their previously created smart / multiplatform playlists.
r12. provide ways to manage previously-created smart/multiplatform playlists i.e. edit, delete, relinquish options
r13. be capable of regenerating smart/multiplatform configuration graphs of previously created playlists based on some standard (the position of components may differ for the user's original layout, but the topology / connection scheme will match)
n5. to see their playlists automatically updated
r14. periodically regenerate all smart/multiplatform playlists based on their configurations. This is necessary if source components change (for example if an artist releases a new track)