Your personal, always-on Spotify Wrapped
Fletch is a desktop web application that gives you instant access to your top Spotify tracks, artists, and musical taste analyticsβanytime, not just once a year.
- π΅ Top Tracks & Artists: View your most-listened content across different time periods
- π Taste Analytics: Understand your music preferences with mood and genre insights
- π Time Ranges: Switch between short (4 weeks), medium (6 months), and long-term (all time) data
- π§ Playlist Creation: Generate playlists from your top tracks with one click
- π Privacy-First: Secure token handling with no data tracking or selling
- Spotify Premium Account (recommended for best API access)
- Modern Web Browser (Chrome, Firefox, Safari, Edge)
- Desktop/Laptop (optimized for 1200px+ screens)
- Visit Fletch (URL will be provided at launch)
- Connect Your Spotify Account via secure OAuth
- Explore Your Data across different time periods
- Create Playlists from your favorite tracks
- Return Anytime for updated insights
- Frontend: Next.js 15, React, TypeScript, Tailwind CSS
- Backend: .NET 9 Minimal API with Entity Framework Core
- Database: SQLite (with PostgreSQL migration path)
- Authentication: OAuth 2.0 PKCE with Spotify
- Deployment: Vercel (frontend) + Azure App Service (backend)
Fletch/
βββ spec/ # Project specifications
β βββ IDEA_AND_VISION.md
β βββ PRODUCT_SCOPE_AND_SHAPE.md
β βββ TARGET_USERS_AND_EXPERIENCE.md
β βββ TECHNOLOGY_AND_SYSTEM_OVERVIEW.md
β βββ QUALITY_RISKS_AND_CONSTRAINTS.md
β βββ SUCCESS_AND_MEASUREMENT.md
β βββ NON_FUNCTIONAL_EXPECTATIONS.md
β βββ ARCHITECTURE_DECISION_RECORDS.md
β βββ CHANGELOG_FOR_SPECIFICATIONS.md
β βββ ROADMAP.md
βββ src/ # Source code (coming in Phase 2)
βββ docs/ # Documentation (coming soon)
βββ scripts/ # Development scripts (coming soon)
βββ infrastructure/ # Deployment configs (coming soon)
- Project vision and requirements defined
- Technical architecture decisions documented
- User personas and experience requirements established
- Authentication and Spotify API integration
- Dashboard UI and data visualization
- Playlist creation functionality
- Performance optimization and polish
- Production deployment and user testing
- Feedback integration and refinement
- Public launch and user acquisition
- Feature enhancements based on user feedback
- User Engagement: Monthly return rate >30%
- Performance: Dashboard loads <3 seconds
- Reliability: 99% uptime with secure token handling
- Experience: User feedback emphasizing "ease" and "clarity"
- OAuth 2.0 PKCE: Secure authentication without exposing client secrets
- Encrypted Storage: Refresh tokens encrypted at rest
- Privacy-First: No user tracking, analytics, or data selling
- HTTPS Everywhere: All communication encrypted in transit
- Data Control: Users can delete their data anytime
Comprehensive documentation is available in the /spec directory:
- Project Vision: Core concept and problem statement
- Product Scope: Features and boundaries
- Technical Overview: Architecture and implementation
- Development Roadmap: Timeline and milestones
- Architecture Decisions: Technical decision rationale
This is currently a solo project, but contributions and feedback are welcome once the codebase is established in Phase 2.
-
Clone the repository
git clone https://github.com/username/fletch.git cd fletch -
Configure Spotify API credentials
Copy the template files and add your Spotify API credentials:
# Backend configuration cp src/backend/appsettings.json.template src/backend/appsettings.json cp src/backend/appsettings.Development.json.template src/backend/appsettings.Development.jsonEdit both files and replace the placeholders with your actual Spotify API credentials:
YOUR_SPOTIFY_CLIENT_ID_HERE- Get from Spotify Developer DashboardYOUR_SPOTIFY_CLIENT_SECRET_HERE- Get from Spotify Developer Dashboard
β οΈ IMPORTANT: Never commit these files to git. They are already in.gitignore. -
Start the development environment
# Instructions for starting backend and frontend services # Coming soon...
Current Phase: Specification Complete
Next Milestone: Begin Core Development
Estimated MVP: 10-12 weeks from start
Target Launch: Q1 2025
- Project Lead: [Your Name]
- Email: [Your Email]
- Issues: GitHub Issues (once public repository is created)
[License information to be determined]
Built with β€οΈ for music lovers who want to understand their taste beyond the annual Wrapped