About Disctopia
Music-streaming platform where artists publish and monetize their content directly.
Disctopia has two products. A marketing website presents the platform, news and updates. A separate web app is where people stream and interact.
For users, these were two places with two experiences. Disctopia wanted them to behave as a single system, where one account, one set of data and one content team serve both. OSKI was asked to connect them without building a heavier architecture than the products needed.
What had to be solved
Joining the two products meant sharing identity, data and content without adding complexity.
- One account should open both the website and the app.
- News, comments and likes needed one API instead of duplicated backend code.
- User data had to stay consistent between site and app.
- Marketing needed a way to announce events on either platform from the CMS.
- The architecture had to stay simple enough to maintain.
How the team built it
Auth0 became the identity provider for both products. Token handling is secure and sessions stay consistent as users move between site and app.
One API serves the website and the web app on the same backend. News, comments and likes go through it, so both products read and write the same data and user records stay consistent.
Events are created in Umbraco. Editors choose whether each one appears on the website, the app or both, and a small script loads the matching banner and draws it on the page. Marketing can run announcements on its own schedule.
What changed
Disctopia now runs its site and app as one ecosystem that is easier to maintain.
- One set of Auth0 credentials works on both platforms.
- Both products run on a single backend and API, and comments and likes live in one place.
- Marketing publishes event banners from the CMS without developer involvement.
Inside the product
