<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Aaron Sun builds small free tools]]></title><description><![CDATA[Aaron Sun builds small free tools]]></description><link>https://aaronsun.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 17:09:08 GMT</lastBuildDate><atom:link href="https://aaronsun.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[A daily standup timer the whole team can see]]></title><description><![CDATA[A time box for every person on a shared screen, run from your phone: colour cues, a rundown and messages. Free, no account.]]></description><link>https://aaronsun.hashnode.dev/a-daily-standup-timer-the-whole-team-can-see</link><guid isPermaLink="true">https://aaronsun.hashnode.dev/a-daily-standup-timer-the-whole-team-can-see</guid><category><![CDATA[Productivity]]></category><category><![CDATA[agile]]></category><category><![CDATA[showdev]]></category><dc:creator><![CDATA[Aaron Sun]]></dc:creator><pubDate>Fri, 20 Nov 2026 22:15:58 GMT</pubDate><content:encoded><![CDATA[<p>Daily standups drift. One person's update runs long, the next one rushes, and the meeting that was meant to take fifteen minutes takes thirty. A visible time box for each person helps, and it doesn't need an app or an account. I use a free synced timer in my team's daily scrum to keep everyone's turn short: <a href="https://timer.zexa.se/standup-timer?ref=hashnode">https://timer.zexa.se/standup-timer?ref=hashnode</a></p>
<h2>Give every person a time box</h2>
<p>Add one item per teammate and set a time box. Many teams use one or two minutes, but pick what fits your team. When a person finishes, press <em>Next</em>: the clock moves to the next name and starts from its full length.</p>
<h2>Let the colour do the nagging</h2>
<p>The clock turns amber in the last minute and red at zero, and then counts up. A long turn is visible to everyone without anyone having to interrupt. That is easier on the person talking than a facilitator saying "we need to move on".</p>
<h2>Same screen for the room and the call</h2>
<p>Open the screen link on the team screen. If part of the team is remote, share that same screen in the call, or let each person open the link on their own device: up to 60 screens show the same time, calculated from a server clock, so they don't drift apart.</p>
<h2>One person runs it from a phone</h2>
<p>Scan the QR code on the controls page and your phone becomes the remote: pause when someone asks a quick question, add a minute, or send a short message such as "Let's take this offline" that appears under the clock on every screen.</p>
<h2>Practical notes</h2>
<ul>
<li>No account, no ads, no tracking, and nothing to install. It runs in a browser.</li>
<li>Keep the private controls link: it is the only way to run that timer. A timer is deleted 7 days after its last use, so for a standing meeting you simply start a new one.</li>
<li>The same setup works for retrospectives, planning and any meeting where each person or topic gets a time box.</li>
</ul>
<p>If you run standups, I'd like to know what would make this better for your team: <a href="mailto:timer@zexa.se">timer@zexa.se</a></p>
<p><em>Zexa Timer was built with a lot of help from Claude Code, and so was a draft of this post.</em></p>
]]></content:encoded></item><item><title><![CDATA[A speech timer for Toastmasters and debates: the speaker sees it, one person controls it]]></title><description><![CDATA[Amber and red cues, a rundown for every speech, and a phone remote for the timekeeper. Free, no account.]]></description><link>https://aaronsun.hashnode.dev/a-speech-timer-for-toastmasters-and-debates-the-speaker-sees-it-one-person-controls-it</link><guid isPermaLink="true">https://aaronsun.hashnode.dev/a-speech-timer-for-toastmasters-and-debates-the-speaker-sees-it-one-person-controls-it</guid><category><![CDATA[publicspeaking]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[showdev]]></category><dc:creator><![CDATA[Aaron Sun]]></dc:creator><pubDate>Fri, 20 Nov 2026 20:30:26 GMT</pubDate><content:encoded><![CDATA[<p>A fair speech timer has two jobs: the speaker sees the time, and one person controls it. Here is how to set that up for a Toastmasters meeting, a debate round or a conference slot with a free synced timer: <a href="https://timer.zexa.se/speech-timer?ref=hashnode">https://timer.zexa.se/speech-timer?ref=hashnode</a></p>
<h2>Show it to the speaker, control it from the audience</h2>
<p>Open the screen link on a projector, TV or tablet that the speaker can see. The timekeeper scans the QR code on the controls page and runs it from a phone from their seat. Everyone sees the same time, and up to 60 screens can follow one timer.</p>
<h2>Colours instead of cards</h2>
<p>The clock turns amber in the last minute and red at zero, and then counts up so the speaker sees how far over they are. That replaces the green, yellow and red cards for many meetings.</p>
<h2>One item per speech</h2>
<p>For a meeting or a debate, add each speech as an item with its own length (for a debate: constructive, cross-examination, rebuttal). <em>Next</em> moves to the following speech, and the clock resets to its length. There is a page for debates with that layout: <a href="https://timer.zexa.se/debate-timer?ref=hashnode">https://timer.zexa.se/debate-timer?ref=hashnode</a></p>
<h2>Practical notes</h2>
<ul>
<li>No account and nothing to install; it works in any browser.</li>
<li>Messages ("Please conclude") show under the clock if you need to nudge someone.</li>
<li>Keep the private controls link. A timer is deleted 7 days after its last use.</li>
</ul>
<p>If you time speeches for a club or a school, I would like to know what is missing: <a href="mailto:timer@zexa.se">timer@zexa.se</a></p>
<p><em>Zexa Timer was built with a lot of help from Claude Code, and so was a draft of this post.</em></p>
]]></content:encoded></item><item><title><![CDATA[A countdown for the sound desk: timing a sermon or church service]]></title><description><![CDATA[A big quiet countdown for the speaker and a phone remote for the sound desk: rundown, messages and colour cues. Free, no account.]]></description><link>https://aaronsun.hashnode.dev/a-countdown-for-the-sound-desk-timing-a-sermon-or-church-service</link><guid isPermaLink="true">https://aaronsun.hashnode.dev/a-countdown-for-the-sound-desk-timing-a-sermon-or-church-service</guid><category><![CDATA[webdev]]></category><category><![CDATA[Productivity]]></category><category><![CDATA[showdev]]></category><dc:creator><![CDATA[Aaron Sun]]></dc:creator><pubDate>Fri, 20 Nov 2026 20:29:30 GMT</pubDate><content:encoded><![CDATA[<p>For a sermon or a service, the speaker needs a clock they can glance at, and the person who knows how the service is going needs to run it quietly. This is how that can work with a free synced timer: <a href="https://timer.zexa.se/church-timer?ref=hashnode">https://timer.zexa.se/church-timer?ref=hashnode</a></p>
<h2>Two roles, two devices</h2>
<p>Start a timer and you get two links. The screen link goes on a stage monitor, a confidence screen or a tablet on the lectern. The controls link stays at the sound desk: scan its QR code with a phone and the phone becomes the remote. The speaker sees a big, quiet countdown; the team controls it without leaving their place.</p>
<h2>Build the service as a rundown</h2>
<p>Add one item per part with its length: welcome, worship, reading, sermon, response. Press <em>Next</em> when the part actually changes. The clock turns amber in the last minute and red at zero, and if the sermon runs over, the time keeps counting up so everyone can see by how much.</p>
<h2>Tell the speaker without a note</h2>
<p>Send a short message from the controls ("Five minutes", "Please conclude") and it appears under the clock on the screen. It is easier than passing a note or catching their eye.</p>
<h2>Practical notes</h2>
<ul>
<li>It runs in a browser, so it works on whatever is already at the desk: Windows, Mac, Chromebook, iPad.</li>
<li>If the internet drops, screens keep counting from the last update and reconnect by themselves, because the time is calculated from the server clock.</li>
<li>No account, no ads, no tracking. Keep the controls link private; it is the only way to run that timer.</li>
</ul>
<p>What would a church media team need that is missing? I'm still working that out: <a href="mailto:timer@zexa.se">timer@zexa.se</a></p>
<p><em>Zexa Timer was built with a lot of help from Claude Code, and so was a draft of this post.</em></p>
]]></content:encoded></item><item><title><![CDATA[How to run a classroom timer from your phone]]></title><description><![CDATA[Show a countdown on the board and control it from your phone: rundowns for stations, colour cues and messages, no account.]]></description><link>https://aaronsun.hashnode.dev/how-to-run-a-classroom-timer-from-your-phone</link><guid isPermaLink="true">https://aaronsun.hashnode.dev/how-to-run-a-classroom-timer-from-your-phone</guid><category><![CDATA[education]]></category><category><![CDATA[teaching]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Aaron Sun]]></dc:creator><pubDate>Fri, 20 Nov 2026 20:28:40 GMT</pubDate><content:encoded><![CDATA[<p>A timer on the board is useful, but only if you can change it without walking back to the computer. These are the habits that make a classroom timer work, using a free synced timer: <a href="https://timer.zexa.se/classroom-timer?ref=hashnode">https://timer.zexa.se/classroom-timer?ref=hashnode</a></p>
<h2>Put it where everyone can see it, control it where you stand</h2>
<p>Open the screen link on the projector or smartboard, then scan the QR code on the controls page with your phone. The board shows the clock, and you walk around the room with the remote in your pocket. Pause when a question runs long, add a minute when the group is almost done, or change the time without touching the computer.</p>
<h2>Use a rundown for stations and transitions</h2>
<p>If a lesson has parts, add one item per part with its own length: starter, group work, feedback, tidy up. Press <em>Next</em> to move on. The clock turns amber in the last minute and red at zero, and overtime keeps counting, so the class sees how far over a part is without you saying a word.</p>
<h2>Send a message instead of interrupting</h2>
<p>Type "Two minutes" or "Share with your partner" and it appears under the clock on every screen. It is a quiet way to steer the room.</p>
<h2>Practical notes</h2>
<ul>
<li>Nothing to install and no account, so it works on a school Chromebook or iPad. Up to 60 screens can follow one timer.</li>
<li>Keep the private controls link. It is the only way to run that timer. A timer is deleted 7 days after its last use.</li>
<li>Need just a simple timer on one device? There are instant 1, 5, 10 and 15 minute pages that need no setup.</li>
</ul>
<p>I'm not a teacher by trade, so I would like to hear what would make this better for a real classroom: <a href="mailto:timer@zexa.se">timer@zexa.se</a></p>
<p><em>Zexa Timer was built with a lot of help from Claude Code, and so was a draft of this post.</em></p>
]]></content:encoded></item><item><title><![CDATA[I built a free stage timer you run from your phone]]></title><description><![CDATA[A free web timer for talks, classes and church services: a big countdown on any screen, controlled from your phone by QR code. No account.]]></description><link>https://aaronsun.hashnode.dev/i-built-a-free-stage-timer-you-run-from-your-phone</link><guid isPermaLink="true">https://aaronsun.hashnode.dev/i-built-a-free-stage-timer-you-run-from-your-phone</guid><category><![CDATA[webdev]]></category><category><![CDATA[showdev]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Aaron Sun]]></dc:creator><pubDate>Fri, 20 Nov 2026 17:43:11 GMT</pubDate><content:encoded><![CDATA[<p>I use this timer in my team's daily scrum to keep everyone's turn short, and it works anywhere a speaker needs to see the time: talks, debates, classes, church services. A phone on the lectern is too small, and a countdown on the projector means whoever runs the laptop must also watch the clock. So the screen and the remote are two different devices.</p>
<p><strong>Zexa Timer</strong> is a free web timer: <a href="https://timer.zexa.se/?ref=hashnode">https://timer.zexa.se/?ref=hashnode</a></p>
<h2>How it works</h2>
<ol>
<li>Open the page and press <em>Start a free timer</em>. You get two links: one for screens, one private link for the controls.</li>
<li>Open the screen link on a projector, TV or tablet. Up to 60 screens can watch the same timer.</li>
<li>Scan the QR code on the controls page with your phone. Your phone is now the remote: start, pause, add a minute, set any length.</li>
</ol>
<p>There is no account and nothing to install. It runs in the browser on Windows, Mac, Chromebook, iPad and a smart TV browser.</p>
<h2>What it does for a speaker</h2>
<ul>
<li><strong>Rundown:</strong> one item per speaker or segment, each with its own length, and a <em>Next</em> button. Overtime keeps counting so you can see how far over you are.</li>
<li><strong>Messages:</strong> type "Two minutes" or "Please conclude" and it appears under the clock on every screen.</li>
<li><strong>Colour cues:</strong> amber in the last minute, red at zero.</li>
<li><strong>Quick timers:</strong> if you only want 5, 10 or 15 minutes on this device, there are pages for that with no setup.</li>
</ul>
<h2>How the clocks stay together</h2>
<p>Each timer is one Cloudflare Durable Object with WebSocket hibernation. The server holds the time, and every screen calculates what to show from the server clock, so screens do not drift. If the internet drops, a screen keeps counting from the last update and reconnects by itself.</p>
<h2>Honest notes</h2>
<ul>
<li>It is free and I have no paid tier. If paid features ever come, the timers you already use will keep working.</li>
<li>There are good existing tools (Stagetimer is the best known). Mine is simpler and has no account at all; theirs does more.</li>
<li>No ads, no tracking, no cookies. A timer is deleted 7 days after its last use.</li>
<li>I built it with a lot of help from Claude Code.</li>
</ul>
<p>It is new, so I would like to hear what is missing for your classroom, church or meetup: <a href="mailto:timer@zexa.se">timer@zexa.se</a></p>
]]></content:encoded></item><item><title><![CDATA[I'm still learning Swedish, so I built a dual-subtitle extension for Nordic public TV]]></title><description><![CDATA[A free browser extension that shows the original Swedish, Norwegian or Danish subtitle with a translation, on SVT Play, UR, NRK and DR.]]></description><link>https://aaronsun.hashnode.dev/i-m-still-learning-swedish-so-i-built-a-dual-subtitle-extension-for-nordic-public-tv</link><guid isPermaLink="true">https://aaronsun.hashnode.dev/i-m-still-learning-swedish-so-i-built-a-dual-subtitle-extension-for-nordic-public-tv</guid><category><![CDATA[showdev]]></category><category><![CDATA[JavaScript]]></category><category><![CDATA[cloudflare]]></category><category><![CDATA[webdev]]></category><dc:creator><![CDATA[Aaron Sun]]></dc:creator><pubDate>Thu, 19 Nov 2026 15:55:11 GMT</pubDate><content:encoded><![CDATA[<p>I'm a developer living in Sweden, and I'm still learning Swedish. The best practice material I've found isn't a course: it's public TV. SVT Play, UR, NRK and DR have huge free libraries, and almost every programme comes with subtitles in the original language.</p>
<p>The problem is the player. It shows one subtitle track at a time, and there is no subtitle in my language. Swedish-only subtitles are too hard at the start, and pausing to look things up kills the flow. Tools like Language Reactor solve this for Netflix and YouTube, but not for the Nordic broadcasters. So I built <strong>Nordic Dual Subs</strong>: a free browser extension that shows the broadcaster's own subtitle line together with a translation in your language, perfectly in sync.</p>
<img src="https://dualsubs.zexa.se/img/1-en-pa-sparet.jpg" alt="Two subtitle lines on SVT Play: the original Swedish line and a translation under it" style="display:block;margin:0 auto" />

<h2>What it does</h2>
<ul>
<li><strong>Two lines at once</strong> on SVT Play, SVT Barn, UR Play, NRK TV and DR TV: the original Swedish, Norwegian or Danish line, and a translation (29 languages, including Arabic, Persian, Somali, Tigrinya, Ukrainian and Chinese, right-to-left included).</li>
<li><strong>Click any word</strong>: the video pauses and you get the meaning and the base form (<em>sprang → springa</em>), with an English gloss from the open Folkets lexikon dictionary.</li>
<li><strong>Save words with their sentence</strong>, review them with simple spaced repetition, or export them to Anki as CSV.</li>
<li><strong>Practice keys</strong>: A / S / D for previous / repeat / next line, Shift+S replays the line slowly.</li>
<li><strong>Burned-in subtitles</strong>: some foreign films have the Swedish text in the picture. The extension reads it locally with Tesseract (WebAssembly) and translates it.</li>
</ul>
<h2>How it works (the parts that were interesting to build)</h2>
<p><strong>Getting the subtitles.</strong> Each broadcaster exposes its subtitle files (WebVTT and friends) through the same APIs its own player uses. The content script works out which programme is playing (all five sites are single-page apps, so it follows URL changes), the background worker fetches and parses the subtitle file, and an overlay is drawn inside the site's own player so it also works in fullscreen. The site's own subtitles are hidden so nothing overlaps.</p>
<p><strong>Translation without a translation bill.</strong> I wanted this to run at zero cost. Each browser translates lines with Google's free web endpoint from its own IP, and sends <code>[line, translation]</code> pairs to a small backend. A line becomes <em>trusted</em> only when installs from <strong>two different networks</strong> submitted the identical translation (Google is deterministic, so honest clients agree, and one client can't plant a translation). Trusted lines are then served to everyone, keyed by a hash of the line, so the server never hands out subtitle text to someone who doesn't already have it. When Google rate-limits a user, a capped DeepL fallback covers the lines near the playhead.</p>
<p><strong>The backend is Cloudflare's free tier.</strong> One Worker plus a D1 (SQLite) database: anonymous installs with HMAC session tokens, the shared translation cache, optional Google sign-in for syncing saved words, and Stripe for a future optional Pro plan. Free tiers have hard daily limits, so a small GitHub Action checks D1 and Workers usage every morning and mails me before anything gets close. One lesson: my end-to-end tests were quietly writing thousands of rows to the production database. They now run against an in-process mock API, with a guard that fails the test if anything tries to reach production.</p>
<p><strong>One codebase, three stores.</strong> The same source builds a Chrome/Edge package and a Firefox package. The Firefox build swaps the MV3 service worker for background scripts, drops the <code>offscreen</code> API (OCR runs in Firefox's background page instead, which has a DOM), and declares Firefox's data-collection consent. Firefox for Android gets touch controls (⏮ ↺ ⏭ 🐢) instead of keyboard shortcuts. Publishing goes through each store's API, with one catch: Microsoft only lets the API publish an Edge extension after its first version was published by hand.</p>
<p><strong>Things outside my control.</strong> DR TV only plays when you're logged in, and some programmes on all three broadcasters are geo-restricted to their own country. The first user email I got was exactly that: "it doesn't work on DR TV". The extension now says <em>why</em> (log in to DR, or "this programme is only available in Denmark") instead of staying silent.</p>
<h2>Built with a lot of AI help</h2>
<p>Full disclosure: I built this with heavy help from an AI coding assistant. It wrote much of the code and the tests, ran the end-to-end tests against real SVT and NRK programmes, and handled most of the store paperwork. I decided what to build, tested it on my own TV evenings, and pushed back when something was wrong. It's been a fun way to ship a side project in the evenings without cutting corners on tests.</p>
<h2>Try it</h2>
<p>It's free (everything is free during the launch period; the dual subtitles stay free), no account needed.</p>
<ul>
<li>Website and guides (16 languages): <a href="https://dualsubs.zexa.se?utm_source=hashnode&amp;utm_medium=article&amp;utm_campaign=launch">https://dualsubs.zexa.se?utm_source=hashnode&amp;utm_medium=article&amp;utm_campaign=launch</a></li>
<li>Chrome Web Store: <a href="https://chromewebstore.google.com/detail/ejmbcllddngiakhpcpajkajeghmdapko?utm_source=hashnode&amp;utm_medium=article&amp;utm_campaign=launch">https://chromewebstore.google.com/detail/ejmbcllddngiakhpcpajkajeghmdapko?utm_source=hashnode&amp;utm_medium=article&amp;utm_campaign=launch</a></li>
</ul>
<p>If you're learning a Nordic language, I'd love to hear what's missing. And if you've built something similar for other broadcasters, I'm curious how you handled subtitles and translation costs.</p>
]]></content:encoded></item><item><title><![CDATA[I replaced Spotify for my family with a music server I built, and its own phone apps]]></title><description><![CDATA[A dad built an open-source music server and its own Android and iPhone apps to replace Spotify for the family: car autoplay, offline favorites, synced…]]></description><link>https://aaronsun.hashnode.dev/i-replaced-spotify-for-my-family-with-a-music-server-i-built-and-its-own-phone-apps</link><guid isPermaLink="true">https://aaronsun.hashnode.dev/i-replaced-spotify-for-my-family-with-a-music-server-i-built-and-its-own-phone-apps</guid><category><![CDATA[#selfhosted]]></category><category><![CDATA[Open Source]]></category><category><![CDATA[golang]]></category><category><![CDATA[Android]]></category><dc:creator><![CDATA[Aaron Sun]]></dc:creator><pubDate>Wed, 18 Nov 2026 19:43:57 GMT</pubDate><content:encoded><![CDATA[<p>I ran Navidrome at home for a long time. The server was never the problem. The phone was: every client I tried had its own bugs, and they always showed up in the same two places, playing in the background and playing in the car. My family uses music mostly in the car and on walks, so "it works when the screen is on" wasn't good enough.</p>
<p>So I built my own server and its apps together, and called it <strong>Melarka</strong>. It has replaced Spotify for us. This post is how it's put together and what I learned. It's open source (AGPL-3.0): <a href="https://github.com/aaronsuns/melarka">github.com/aaronsuns/melarka</a>.</p>
<blockquote>
<p><strong>AI disclosure:</strong> Melarka was built with a lot of help from Claude Code, and this post was drafted with Claude too. I designed it, steer it, review what goes in, and test it on our phones every day.</p>
</blockquote>
<img src="https://raw.githubusercontent.com/aaronsuns/melarka/main/docs/screenshots/phone-now-playing.jpg" alt="Melarka on a phone: home, now playing with synced lyrics" style="display:block;margin:0 auto" />

<h2>What it does</h2>
<ul>
<li><strong>Your folders, untouched.</strong> Point it at the music you already have. It never rewrites files or tags; titles, tags, lyrics and fixes live in its own database.</li>
<li><strong>An account per person.</strong> Everyone at home gets their own favorites, playlists, personal radio and nightly picks.</li>
<li><strong>Synced lyrics</strong>, and anyone can nudge lyrics that run early or late.</li>
<li><strong>Native apps.</strong> An Android app in Kotlin and an iPhone app: background play, lock-screen and car controls, gapless, and an offline cache of favorites.</li>
<li><strong>Car autoplay.</strong> When the phone connects to the car over Bluetooth, the favorites start playing by themselves, and the current lyric line shows on the car's display.</li>
<li><strong>Optional YouTube.</strong> Search YouTube or follow channels, and download songs into your own library with yt-dlp.</li>
</ul>
<h2>How it's built</h2>
<p>The server is one Go binary with SQLite, shipped as one Docker container. Install is one command:</p>
<pre><code class="language-bash">curl -fsSL https://raw.githubusercontent.com/aaronsuns/melarka/main/deploy/install.sh | sh -s -- /path/to/your/music
</code></pre>
<p>It streams the original file, or transcodes to AAC on the fly with ffmpeg when the phone needs it.</p>
<p>The web app is React. The phone apps are a mix that turned out to be the main design decision: <strong>the screens are the server's own web app, and playback is native.</strong> The page sends "play this queue" to the native side over a small bridge; the native player (Media3 on Android, AVFoundation on iOS) owns the audio, the lock screen and the car.</p>
<p>That split is why it works in the car. The web page can die, the screen can be off, the app can be in the background, and the music keeps going, because nothing about playback depends on the page. And every new server feature shows up in the apps on day one, because the screens come from the server.</p>
<h2>Things that took the longest</h2>
<ul>
<li><strong>Never starting music on its own.</strong> A player that resumes when a Bluetooth device connects is a nice feature in the car and a terrible one at 6 a.m. in a quiet house. The rule now: only a person (or the car autoplay they turned on) starts sound, and there are tests for every path that can start playback.</li>
<li><strong>Offline that actually works.</strong> The favorites are cached on the phone and the player falls back to them when the network goes, instead of stopping or skipping through the whole queue.</li>
<li><strong>Emulator tests in CI.</strong> The Android app has an end-to-end test on an emulator against a real server: sign in, play a favorite, kill the page's renderer, background the app, go offline. Keeping that test reliable on CI machines was its own project.</li>
</ul>
<h2>The honest catch</h2>
<p>Melarka has its own API, so it is <strong>not Subsonic-compatible</strong>: your existing Subsonic clients won't work with it, and it only makes sense if you want its apps. It's also young, about a month public. The Android APK is on the GitHub releases page (F-Droid is submitted but waiting until the app is older), and the iPhone app installs with SideStore, not the App Store.</p>
<p>If you run a home server and your family still pays for Spotify, I'd love to hear what you think, and especially what breaks. A one-minute tour is on <a href="https://melarka.zexa.se">melarka.zexa.se</a>.</p>
<p><em>Originally published on</em> <a href="https://dev.to/aaronsuns/i-replaced-spotify-for-my-family-with-a-music-server-i-built-and-its-own-phone-apps-2f8m"><em>dev.to</em></a><em>.</em></p>
]]></content:encoded></item></channel></rss>