Audio player implementation

Audio player implementation is an audio player on your site for podcasts, music, audiobooks and voice content: a branded look, a playlist, choice of speed (handy for podcasts and lectures), chapters and timecodes, a progress indicator and seeking along the track, lazy loading. Optionally — persistent (background) playback that continues while a person browses the site. Unlike a bare audio tag or a SoundCloud/Spotify embed, with your own player you control the look and the features: with the controls, accessibility you need and without the excess. Honestly about a wrapper over a platform: it minimizes the third-party branding and recommendations but does not exclude them completely — some of the platform’s UI and API limits remain, and not all features (for example, chapters or speed) are available on every source. A fully custom look and feature set — only with self-hosting (audio is lighter than video, but traffic and storage still cost money). For most, an embed is cheaper and enough. About ready solutions, honestly: for simple tasks there are libraries (Howler.js, Plyr, Wavesurfer) you can set up yourself — the value of our work is in WHAT to show, the design, the persistent mode and accessibility; if the task is simple, we will say so. And honestly about rights: for music the licenses are the hardest — public playback and distribution of tracks require separate licenses, and that is on your side; in case of a violation the platform (SoundCloud/Spotify) may block playback or the account. For your own podcasts and voice the rights are usually yours. Picture this: a podcast page — a player with a playlist, 1.5x speed and chapters, and playback does not stop when moving to another page. The base price starts from 15,000 ₽ for a simple integration; persistent playback and serious customization are more complex (a shared layer above the pages is needed) and cost more; self-hosting is estimated separately by traffic.

• Audio plays in an inconvenient standard player or with SoundCloud branding — it is not your experience.
• There is no speed, chapters and playlist — podcasts and lectures are inconvenient to listen to.
• Playback stops when navigating the site — the listener loses their place.
• There is no accessibility and mobile convenience — part of the audience drops off.

• An audio player in a branded design with the controls you need
• A playlist, chapters and timecodes, seeking along the track
• Playback speed (for podcasts and lectures)
• Optionally — persistent (background) playback while navigating between pages (more expensive, needs a shared layer)
• Lazy loading, accessibility (keyboard, screen readers)
• A source per the task: a wrapper over SoundCloud/Spotify or your own hosting (full control)
• Responsive, convenient control on a phone

• The listener stays in your player — the platform’s branding and recommendations are minimized (fully removed — with self-hosting)
• Podcasts and lectures are convenient to listen to — speed, chapters, playlist
• Playback does not stop — the persistent mode keeps the place
• Audio is available to everyone — keyboard, screen reader, mobile

• You leave a request, describe the audio, the source and the needed features
• We choose the approach, design the player (playlist, chapters, background)
• We implement it, check mobile and accessibility, and launch

• How is it different from a SoundCloud / Spotify embed?

  A custom player (even over SoundCloud/Spotify) fits the design, gives speed, chapters, a playlist and persistent playback. But honestly: if the source is a platform, a wrapper only minimizes its branding and recommendations rather than removing them completely, and some features may be unavailable on a platform source. Full control is with self-hosting. For simple tasks a ready library (Howler.js, Plyr) on your own is enough — we will say so.

• What about the rights to the music?

  For music the rights are the hardest: public playback and distribution of tracks require separate licenses (copyright, related rights), and that is on your side. In case of a violation the platform may block playback or the account, and the rights holder may make claims. We make the player and do not assess the legality of the content. For your own podcasts and voice the rights are usually yours.

• Can playback continue while navigating the site?

  Yes, we make a “persistent” player: it stays at the bottom and does not stop while a person navigates the pages — handy for podcasts and background music. This is noticeably more complex than an ordinary player (it needs a shared layer above the pages, as in single-page apps), so it costs more — we build that into the project.