Skip to content
Stackly by Temaco

Personal project

Rozgłośnia.app — the listeners decide what plays during break.

A web app for a school radio station. A student pastes a YouTube link, everyone votes, and the queue orders itself by vote count. Access is controlled with registration codes issued by form teachers.

The problem it solves

A school radio station is usually run by one person who picks the playlist alone and collects requests on paper or in messages. The result is predictable: few people listen, because few people have any say.

Built with

  • Next.js
  • PostgreSQL
  • YouTube API
  • PWA

Related service

Web apps

How it works

  1. 1A student registers with a code from their teacher, which keeps out random accounts
  2. 2Submitting a track means pasting a YouTube link
  3. 3Everyone else votes, and the queue orders itself by vote count
  4. 4Submissions pass moderation before reaching the voting list
  5. 5The winning queue is played through the station during break
1Registration with a teacher code2Student pastes a YouTube link3Submission moderated4Voting orders the queue5Playback during break
Flow: code registration, link submitted, moderation, voting, playback queue.

What I would refine for a client

This is the largest of my projects and the one that taught me the most about access control. Next steps are per-person submission limits and statistics for the staff supervisor. The app is built as a PWA, so it installs on a phone without an app store.

Do you have a similar process?

Describe it in a few sentences. I will tell you whether it can be automated and what it would cost — including when the answer is that it is not worth it.