spotiplay
Spotiplay is a Spotify data exploration toolkit built with Flask, HTML, and CSS that exposes detailed track, album, and playlist metadata through the Spotify Web API. It focuses on retrieving information that is not typically surfaced in the Spotify client interface, giving users deeper visibility into Spotify’s underlying dataset.
00
problem
The Spotify app is designed for listening, not inspection. As a result, many useful metadata fields such as detailed track information, album-level data, and structured playlist attributes are not easily accessible to users. This creates limitations for people who need deeper analytical access to Spotify’s ecosystem, such as developers, researchers, or music industry professionals who want to verify or analyze release data.
solution
Spotiplay acts as a lightweight web-based toolkit that bridges this gap by directly interacting with the Spotify Web API and presenting structured music metadata in a readable format. Built using Flask with HTML and CSS for the frontend, it provides an interface to query and inspect: - track-level metadata - album details - playlist structures and attributes Instead of focusing on streaming or playback, Spotiplay emphasizes data transparency, turning Spotify’s API into a practical inspection tool. This makes it useful for scenarios like catalog verification, metadata analysis, and music industry research workflows.
Spotiplay came from noticing a simple mismatch: Spotify is powerful as a player, but surprisingly closed when it comes to seeing its own structure.
While working with the Spotify API, I realized how much richer the underlying data is compared to what the app actually shows. That gap became the idea - what if you could just look into the system instead of only interacting with it through playback?
So I built Spotiplay as a small web toolkit using Flask, where Spotify data could be queried and displayed in a clean, structured way. It wasn’t about building another music app - it was about exposing the parts of the system that usually stay hidden.
Over time, it started feeling less like a “playlist viewer” and more like a lightweight inspection tool for music data, something that could actually be useful beyond personal use cases, especially in contexts where metadata accuracy matters.
year
2026
timeframe
2 Months
tools
Flask, HTML, CSS, JS
category
Personal Project
01
02
03
