New look · Radio platforms · Engineering
Tiago Ferreira
Radio platforms that ship
Frontend & backend for radio station platforms — players, schedules, and the systems behind the stream.
01 — Services
What I build
Engineering for radio station platforms — frontend, backend, and launch. Not design.
Radio web players & apps
React / Next.js listening experiences: live stream players, now-playing, show pages, and mobile-ready UIs from your designs.
Station backends & APIs
Node services for schedules, shows, DJs, metadata, auth, and integrations with stream hosts and third-party tools.
Full-stack radio platforms
One engineer for listener-facing sites and station admin — connected UI and API without messy handoffs.
Launch & care
Deploy, performance under live traffic, monitoring basics, and ongoing fixes when the station needs continuity.
02 — Work
Selected work
Radio platform outcomes. Replace these with your real case studies.
Frontend + backend
Live web player rebuild
- Problem
- Legacy station site dropped listeners on mobile and the player stalled during peak hours.
- Solution
- Rebuilt the listening UI in Next.js and wired a reliable stream/metadata API.
- Result
- Smoother playback and a clearer path from visit to listen.
Full-stack
Schedule & shows platform
- Problem
- Programming lived in spreadsheets; the public schedule was always out of date.
- Solution
- Built an admin for shows/DJs and a public schedule synced through a Node API.
- Result
- Staff update once; listeners always see what’s on air.
Frontend
Multi-station network hub
- Problem
- A network of stations needed one branded hub without rebuilding design systems.
- Solution
- Implemented a shared Next.js frontend from their Figma with station switchers and deep links.
- Result
- One codebase, many stations — faster launches for new channels.
Backend
Metadata & integrations layer
- Problem
- Now-playing, podcasts, and chat tools didn’t talk to each other.
- Solution
- Unified a Node API that syncs stream metadata and the tools the station already uses.
- Result
- Reliable now-playing and fewer manual updates for the team.
03 — Process
How projects run
From your designs and station brief to a live platform — clear steps, no theatre.
- 01
Discovery
Stream setup, schedule needs, stack, design assets, and what “on air” success looks like.
- 02
Build
Player, admin, and APIs in short loops — something you can click and hear working.
- 03
Launch
Deploy, harden for live traffic, and hand off what your team needs to run the station.
- 04
Support
Fixes, small features, and care when you want continuity after go-live.
04 — About
About Tiago
I build the frontend and backend for radio station platforms — not the visual design. Bring your brand and product brief; I ship the player, the admin, and the APIs that keep a station online.
From live listening experiences to schedules, shows, and station tools: short loops, clear scope, and code your team can keep running. You own the look; I own the engineering.
Radio stations, broadcast networks, and media teams that need a modern platform — web player, schedule, CMS, and integrations — without juggling five freelancers.
05 — Signal
Clients say
Placeholder quotes — swap with real station feedback when you have it.
Our new player stayed up through peak hours, and the schedule finally matches what’s actually on air.
He took our Figma and shipped both the listener site and the admin API. One partner, no messy handoff.
Technical without the jargon fog. We always knew what was shipping next for the platform.
06 — Contact
Start a project
Include your live website URL, station details, and what you need built. I’ll reply by email.