Getting Started
Onboarding Flow
SongDrive onboarding flow - 2025-08-25 (64 words)
- Status: 🚀 ROADMAP - New user experience
- Summary: Guided tour to onboard users with demo sandbox environment.
Onboarding Steps
- Welcome Screen
- Upload File Tutorial
- If in demo mode: Explicit notification "This is a demo sandbox"
- Comment on Audio File Tutorial
- Invite People Workflow
- Pivot Point: User chooses between personal vs shared workspace
- Prompt to rename workspace if switching to shared
- Promotional Email Opt-In (needs placement determination)
Login Flow
SongDrive Login Flow - 2025-07-23 (61 words)
- Status: 📋 REFERENCE - Login UX research
- Summary: Analyzed Kompoz.com's login flow as exemplar for SongDrive improvements.
Kompoz Best Practices to Adopt
- Landing Page Clarity:
- Clear feature explanations before signup
- Ownership Transparency: Explicitly state who owns uploaded content (frequently asked question)
- DAW Compatibility: Show users can use their DAW of choice
- Simple Email Form: Low-friction initial signup
- Musician Questionnaire:
- Profile picture input
- Two-part questionnaire to understand user needs/experience
- Gamification Integration: Planned for later implementation
Project Organization
Replacing the word "Project" in SongDrive's UI - 2025-11-03 (180 words)
- Status: 🚀 ROADMAP - Terminology redesign
- Summary: Replace vague "Project" term with specific, user-friendly terminology.
Problem Statement
"Project" is too vague - can mean anything the user wants it to be. This creates cognitive friction when organizing and finding content.
Proposed New Terminology
- Idea: Pre-song concepts, small snippets that may become part of future songs
- Song: Existing song or work-in-progress song files
- Album: Collection of songs
- Rehearsal Recording: Audio/video from band practice
- Performance Recording: Audio/video from live shows
- Setlist: Planned song list for specific date/performance
- Playlist: Arbitrary/custom song collections
Upload Workflow Change
When uploading media, system prompts: "What kind is it?" with options above. This categorization makes it trivial to find rehearsal videos, performance recordings, etc.
UX Philosophy: Get the user to think less. Make content self-organizing through smart categorization.
Browsing Projects
SongDrive - Browsing Projects - 2025-02-24 (366 words)
- Status: 🚀 ROADMAP - Project navigation overhaul
- Summary: Move toward Google Drive-style hierarchical browsing with grid/list views.
User Scenarios
Users visit SongDrive for three primary reasons:
- Creating new project + immediate data entry
- Data entry on existing project
- Following up on collaborator actions (often from push notification)
Target UX: Google Drive Model
- Grid View: Visual browsing with thumbnails
- List View: Compact, information-dense browsing
- Hierarchical Folders: Navigate through nested project structure
Technical Implementation
Considering react-arborist library (GitHub) for nested tree view showing:
- Application's remote projects
- Local importable projects
- Unified browsing experience
Current vs. Future Hierarchy
Current (Flat):
Workspaces
└── Projects (no sub-projects)
└── Files (no revisions, no nested structure)
└── Comments (files only, not projects)Future (Nested):
Workspaces
└── Projects/Folders (nested hierarchy)
├── Sub-projects (artist → album → song structure)
└── Files (with revisions, matching DAW project structure)
└── Comments (on files AND projects)Google Drive UI Analysis
- Home Page: Shows suggestions based on recent activity (grid view) - NO folders, only files
- Recent Activity: List view - again, NO folders shown
- "My Drive" Grid: Folders displayed in separate grid above files
- "My Drive" List: Folders listed first before files
Workspace Scope Evolution
- Personal: Individual musician's workspace for all ideas/songs
- Music Collective: Shared workspace for band/group
- Producer with Multiple Clients: Separate private workspace per client
- Setlist Preparation: Special project type for live performance planning