Eight platforms, one listening history
Connected accounts feed a unified listening history rather than leaving taste data fragmented per platform.
One picture, not eight fragments.
Deep multi-platform music analytics — eight integrations, real taste profiling, one dashboard.
Spotify Wrapped shows one platform’s slice once a year; the rest of the time, real listening habits across eight services stay siloed with no unified view of what someone’s taste actually looks like.
SoulShriek pulls listening history from eight integrations into a single Node.js analytics backend, building Last.fm tag-based taste profiles instead of just aggregating top-artist charts.
A full Expo mobile client ports the same API service as the web dashboard, with concert tracking, recommendations, and playlist tools layered on top of the core analytics.
Connected accounts feed a unified listening history rather than leaving taste data fragmented per platform.
One picture, not eight fragments.
Last.fm tag analysis builds a genre and mood profile deeper than a simple top-artists ranking.
Closer to how taste actually works.
Auth, dashboard, library, analytics, concerts, and recommendations all ship in a native mobile client backed by the same API as the web app.
One backend, two real front ends.
Listening history from eight platforms feeds a single analytics engine instead of leaving a user’s taste data fragmented across each service’s own dashboard.
Last.fm tag data builds a genre and mood profile that goes deeper than a top-artists list, closer to what actually characterizes someone’s listening habits.
The Expo mobile client ports the same API service the web app uses rather than duplicating analytics logic across two codebases.
SoulShriek’s web dashboard, API, and mobile client are built and working locally; the multi-service backend (API, gateway, OAuth integrations) isn’t provisioned on public infrastructure yet.
The API, gateway, and OAuth integration layer need a production host before the web app can go live.
Each of the eight platform integrations needs production-grade API credentials and OAuth app review.
Once hosted, the existing web dashboard and mobile client connect to the live backend with no further rework.