Coachella Co-Pilot

Uses Listening Data Optimize Your Coachella Experience

Comment

Inspiration

We wanted a single place to plan Coachella around your own taste: see who from the lineup you already love, discover new acts that match your Spotify history, get a personalized schedule that respects set-time conflicts, and build a prep playlist—all without juggling multiple apps. Clawchella is your Coachella co-pilot.

What it does

  • Log in with Spotify (OAuth via Composio) so we can use your listening history.
  • Compatibility view: Shows which lineup artists are in your top artists and suggests others you might like based on related artists and your taste.
  • Personalized schedule: A day-by-day plan that prioritizes your matches and suggestions and highlights conflicts so you can choose.
  • Prep playlist: One-click creation of a Spotify playlist filled with tracks from your planned artists so you can get ready for the fest.

How we built it

  • Backend (Node.js, Express): REST API for auth, lineup, schedule, compatibility, and playlist creation. We use Composio’s SDK for Spotify OAuth and for calling Spotify APIs (top artists, related artists, create playlist, add tracks). Lineup and set times come from You.com or from static JSON; compatibility and plan logic run in our own services.
  • Front-end (React, Vite): Landing page, dashboard with compatibility list and schedule view, and prep-playlist action. Dev server proxies API calls to the backend.
  • Deploy: Single Docker image (built React app + Express server) deployed on Akash Network so the app runs on decentralized compute.

Challenges we ran into

  • Configuring Composio Auth Config (correct scopes, callback URL, BASE_URL for OAuth) and ensuring the right Spotify scopes (user-top-read, user-read-private, playlist-modify-public) were set so the app could read taste and create playlists.
  • Matching lineup artist names to Spotify data (normalizing “&” vs “and”, handling slight name differences) for reliable compatibility and suggestions.
  • Designing the schedule/plan logic to surface conflicts and still let users see a clear day-by-day view.

Accomplishments that we're proud of

  • End-to-end flow: one login, then compatibility, schedule, and prep playlist from one place.
  • Using Composio to avoid building and maintaining our own Spotify OAuth and API integration.
  • Deploying the full stack on Akash as a single container with a public URL suitable for OAuth callbacks.

What we learned

  • How to integrate Composio’s connected accounts and tool execution for a production-style Spotify flow.
  • Practical OAuth callback handling and session management (cookie-session) for a React + Express app.
  • Tradeoffs between live lineup data (You.com) and static lineup/schedule data for reliability and control.

What's next for Clawchella

  • Optional calendar export (e.g. iCal) of your personalized schedule.
  • Better conflict UI (e.g. side-by-side comparison, “pick one”).
  • Keeping lineup/schedule data up to date each year and optionally pulling more from You.com or other sources.

Built With

Share this project:

Updates