Skip to content
Alpha · Live Product · Pre-funding
OHR.FM

Music culture, reconnected.

A platform giving credit, context, and community back to club culture — DJs, labels, artists, and fans.

0→1Web PlatformMusic TechCommunityFounding Designer

Founding Designer · 2024–Present · Live

These screens show the full product vision across discovery, editorial, community, and creator monetisation. The live alpha prioritised the tracklist crediting engine first. Discovery, social, and monetisation layers are being sequenced based on user feedback and product readiness.

Full Product Vision · Homepage

ohr.fm
OHR.FM homepage design — Discover the Tracks Behind the Culture. Shows connected scenes graph, tracklist view, crate section, featured collectives, editorial articles, and fair splits model.

Homepage — discovery feed, connected scenes graph, editorial content, fair splits revenue model, and featured collectives.

Community & Monetisation · Collective Profile

ohr.fm/collectives
OHR.FM collective profile page — OHR Berlin community radio. Shows support tiers (€5 Listener, €10 Inner Circle), latest sets with tracklist previews, community activity feed, and recent supporter list.

Collective profile — community radio page showing support tiers, latest sets, tracklist previews, and the community activity feed. Monetisation model: fans support directly, 0% platform extraction.

The Problem

“Club culture runs on invisible labour.
DJs credit producers. Fans discover labels.
But none of it connects.”
01

Producers don't know where their tracks are played

02

Fans can't follow music from set → artist → label

03

DJs lose credit when sets are shared without context

04

Platforms optimise for streams, not relationships

Every set is a map.

OHR makes the connections between DJs, tracks, labels, and clubs visible and navigable.

Tracklist crediting

Every set auto-credits artists and labels

Connected discovery

Follow a track to its artist, label, scene, sets

Direct support

Purchase tracks straight from tracklists

Community profiles

DJs discovered through music, not follower count

The hardest problem: making crediting effortless.

The hardest problem was making crediting feel like part of the listening experience, not admin work. The tracklist editor is OHR's most complex UI, a waveform-synced tool that turns a 2-hour mix into a fully credited, linked tracklist.

● Shipped in alpha

OHR mix detail view — Warehouse Logic tracklist with 9 credited tracks showing artist, label, genre and BPM data

Mix detail — Warehouse Logic (Techno/Industrial). Every track credited with artist, label, album, genre, and BPM. Live in alpha.

Waveform sync

Click to timestamp, no manual entry

Artist autocomplete

Linked to Discogs database

Rekordbox import

Paste export, timestamps preserved

Design vision vs. shipped alpha

The social layer — a discovery feed connecting posts to music objects — was designed before the alpha launched. The alpha prioritised the tracklist crediting engine first. The social layer ships next.

Design Concept

OHR social layer design concept

Social layer concept — designed to connect posts to tracks, DJs, mixes, labels, events, and discovery trails.

Share your mix in 4 steps.

OHR pulls directly from SoundCloud, so artwork, description, and title come with it. No duplicate work.

01

Connect SoundCloud

Authenticate once, access all your sets

02

Select your mix

Pick from your public SoundCloud library

03

Add your tracklist

Sync timestamps with the waveform

04

Publish & get credit

Live on OHR, linked to your profile

My Role

What I owned

0→1 product structure, UX flows, and interface direction

Core listening, crediting, profile, and tracklist experiences

Design system foundations for a live alpha

Product decisions with founders across scope, sequencing, and MVP clarity

Front-end collaboration and implementation support for a small team

AI IN MY WORKFLOW

How I used AI without outsourcing judgement

OHR was designed under early-stage constraints with a small team. I used AI as a speed layer across exploration, prototyping, and product documentation — closing the gap between product thinking and something testable in the browser.

AI was useful for

Generating first-pass component structures in Cursor and Claude Code

Testing layout and interaction ideas directly in code

Scaffolding screens with Figma Make before refining in Figma

Writing rough acceptance criteria and product notes

Exploring edge cases in tracklist editing, mix submission, and community profiles

Comparing product directions before committing design time

I kept human judgement for

Product direction and MVP scope

Community sensitivity and tone

Visual taste and design quality

Prioritisation — deciding what not to build

Naming, copy, and interaction logic

Tools

CursorClaude CodeFigma MakeSupabaseVS Code

Built with the community.

OHR isn't built for the music industry — it's built with the people who live in it. From day one, we worked with ambassadors, DJs, and collectives to shape the platform around real needs.

Collectives like BLVSH — a Berlin-based group supporting women, trans and non-binary DJs — help us understand what meaningful credit actually looks like for marginalised communities in club culture. Ambassador feedback pushed us to prioritise crediting and context before social posting, because discovery without attribution would reproduce the same extractive pattern OHR was trying to solve.

Supported by

Club Commission Berlin logoClub Commission Berlin
Music WorX logoMusic WorX

Supported by institutions that care about club culture

Built from scratch

A system for underground culture

Colour

#6A5CFF

Brand purple

#F1FF4F

Signal yellow

#0E0E10

Background

#F2F0EB

Text primary

Type

OHR

Space Grotesk · Display

Components

Primary action
Secondary action
Tertiary / outline
Live status badge
Pre-funding badge

MVP trade-offs

The early product had to prove the core behaviour without becoming a full social platform too soon. I helped keep the alpha focused on the parts that made OHR distinct: mixes, credits, discovery, and the network around music culture.

01

Prioritised tracklist crediting and mix detail over broad social features.

02

Kept profiles lightweight until there was enough behaviour to justify deeper community tooling.

03

Designed around SoundCloud-linked mixes and practical creator workflows before heavier native upload infrastructure.

04

Used the waveform-synced tracklist editor as the product's trust and differentiation layer.

Design challenges

01

Making a graph feel linear

The platform is fundamentally relational. The design challenge was giving users a clear path through complexity — without hiding the connections that make OHR valuable.

02

Credibility in a credible scene

Club culture has high aesthetic standards. The UI had to feel like it belonged — not like a tech startup trying to understand music. Every micro-decision was made with that bar in mind.

03

0 to 1 with a small team

The alpha shipped with a focused early community. The important proof was not feature volume, but whether DJs, collectives, and listeners understood the value of visible credit and contextual discovery.

Live. Pre-funding. Growing.

Alpha livePre-funding

The platform is live with an early community of DJs, ambassadors, and collectives. We're actively iterating on feedback and preparing for a seed round.

Product Roadmap

OHR roadmap showing track identification and cataloguing discovery features

Next: automatic track identification from audio, no manual tagging needed. Plus smarter search across tracks, labels, artists, collectives, and community radios.

Follow the connections.

OHR is free and open to the community. DJs, producers, labels, and fans welcome.