Spinwell

How Spinwell was built, prompt by prompt

Spinwell, a native Navidrome player for Android and iPhone, was built in a single Claude Code conversation. These are all the prompts Nikita sent, word for word, each followed by a short note on what happened next.

Started November 16, 2026. This page is updated while the conversation is still going.

  1. i want us to build a new navidrome (subsonic) audio player for android and ios it should connect to my navidrome over tailnet url, and allow me to simply select artists/albums/playlists/favorites, etc, anything sensible should have download mode (check out how we do this with abs+), should have offline mode, should start playing right when we open it if we closed while playing before (or maybe don't start playing but bring up the player ui) should show the list of upcoming tracks like spotify does probably shuffle should be cool make sure it's beautiful, transitions are great, make sure it's super performant, lightweight, make sure each setting has "i" that explains what that setting is make sure our album covers/track metadata is great

    Claude studied ABS+ (the sister Audiobookshelf app) for its download design, ran a local Navidrome with a generated test library, and checked what the server really does (resumable downloads, transcoding, lyrics, cover ids). It wrote a shared SPEC.md for both apps, opened a board ticket, and started two builders in parallel: Kotlin with Compose and media3 for Android, and SwiftUI with AVFoundation for iPhone.

  2. you also have access to "Navidrome" in vaultwarden for my real production server, also you can debug oneplus 8 over wifi and i have the iphone connected over usb for you to try everything out

    Claude confirmed the credentials work without ever printing them, surveyed the real library (about 1,900 songs in MP3, FLAC and Opus), and noticed that iPhones can't play Opus, so the iPhone app asks the server to convert those songs to AAC. It connected to both test phones.

  3. ! tea api -X POST /user/repos -d '{"name":"naviplus","default_branch":"main"}'

    The command arrived as a chat message instead of running in the shell. Claude ran it, and the git server refused it because the token couldn't create repositories.

  4. ! tea api -X POST /user/repos -d '{"name":"naviplus","default_branch":"main"}'

    Same result. Claude explained that the token lacked the right scope and offered two ways forward.

  5. i want to give you access to creating repos on forgejo, how do i do this

    Claude explained the two pieces: a token with the right scope, and a Claude Code permission rule for that one command.

  6. can you: 1. edit forgejo token permissions youself 2. add permission to claude settings

    Claude added the permission rule. It wasn't allowed to mint a token with the account password, so it asked Nikita to create one.

  7. [screenshot of the git server's new-token form] what do i pick

    Claude listed which scopes to choose, with admin left off.

  8. it's in vaultwarden "Forgejo claude-code token"

    Claude installed the new token without displaying it, created the repository and pushed the spec.

  9. make sure it's mirrored to github + add gh pages landing behind cloudflare proxy, probably buy naviplus.app or something

    Claude started on the GitHub mirror, and Nikita stopped it before anything was created.

  10. actually wait, naviplus is a registered trademark, find better names for navidrome/subsonic app

    Claude brainstormed names, checked .app and .com domains, both app stores and trademark searches, and offered a shortlist.

  11. i like "spin", anything like "spinwave" or "wavespin"?

    Spinwave's domain was taken and a pickleball app already uses the name, and Wavespin collided with an app on Google Play.

  12. "spinwell" is ok too

    The app became Spinwell. Claude bought spinwell.app, renamed the repository, set up the GitHub mirror, and built the landing page with a share image and a privacy page on GitHub Pages behind Cloudflare. Both builders renamed their apps mid-flight.

  13. for spinwell.app we need to use github repo for links ot source

    The site's source and issue links now point at the GitHub repository.

  14. ok when will android/ios be ready to test?

    Both apps had working first builds. Claude reviewed their screenshots and sent each one into a second round against the real library: real artist photos, a mini player overlapping lists, and debug-only launch hooks. Then it sent an Android APK to try.

  15. improve ui/ux, make sure ui is compact enough, search works well, there's shuffle and repeat functions for albums/playlists/artists etc also artists should be available in the offline mode, also offline mode should turn on automatically when server isn't reachable login to my navidrome on oneplus 8 so that i could test it

    Both apps got a third round: a denser layout, live search with recent searches, play, shuffle and repeat on every list, artists and albums available offline, and offline mode that switches on and off by itself. Claude installed Tailscale on the OnePlus so it could reach the server. The sign-in needed Nikita's own GitHub password, so Claude asked him to do it.

  16. logged into tailscale on oneplus

    Claude signed the app in on the OnePlus. It checked which field had focus before typing anything, so the password never landed in a visible field.

  17. opening play ui from pressing a song kind of staggers for some reason i should be able to press download on albums/artists/playlists/individual songs also make settings ui more beautiful, and overall make ui better

    The builders measured the stutter on the phone and found the play queue being built on the main thread. They moved that work off it, which cut the freeze from about 72 ms to about 30 ms. Album, playlist and artist pages got download buttons, songs got a swipe to download, and Settings was redesigned with grouped cards, icons and storage bars.

  18. status?

    The Android round was done and installed on the OnePlus. Claude summarized what changed and what was still untested.

  19. ok logged in iphone to tailscale, also make sure app icons are complete without clipping left top corner

    Claude redrew the icon as the record from the website, kept inside the safe area every Android launcher shows, with a full-bleed version for the iPhone. The old iPhone icon really did have a black wedge in its corner.

  20. make sure we use the same icon for ios and android then record me a demo video on android to show my friends

    Both platforms now render the icon from one shared source file. Claude started on a produced video.

  21. just a screenrecording, no need for editing etc

    This OnePlus has no built-in screen recorder, so Claude scripted a tour of the app on the phone and recorded it from the Mac with scrcpy. It turned off play reporting for the take so the demo wouldn't add plays to the server.

  22. make sure to stop the music when you finish recording

    Music paused (and confirmed paused), play reporting switched back on, and the 97-second recording was sent over.

  23. where's the video?

    Claude copied it to the Desktop and revealed it in Finder.

  24. ok let's upload this whole thing to: 1. google play 2. apple app store 3. github as apk in releases and let's add these links to the main website also make sure we translate to other languages (i think 24 of them?) like with other apps and we have localized screenshots for all devices and all languages in the stores also make sure like with other apps we get our fast ci build and upload to playstore and appstore

    Claude merged both apps into one branch and made sure CI passed. It planned the store launch to follow the house pattern: 24 store languages, a public demo server for reviewers, screenshots for every device in every language, and one release that ships to both stores and GitHub. in progress

  25. you should be able to run simulator?

    Yes: testing and store screenshots for the iPhone run in the Simulator. To sign the real iPhone in to the server, Claude drove the app on the phone with a UI test and a debug launch hook, so nothing was typed on screen.

  26. make sure app icons are the same on ios and android

    Claude compared the iPhone icon file with the shared render (byte for byte the same) and the record on both home screens. The only difference left is each system's own mask: rounded square on iPhone, circle on this launcher.

  27. also make sure to add spinwell to radiant and optimize the store listings with radiant rules (don't mention android in ios store listing please)

    Spinwell joined Radiant, the marketing system: a project file with its App Store and Play ids, keyword research and weekly rank tracking for all 24 store languages, and its site set up for the daily translator. The store copy follows Radiant's rules, and the iPhone listing never mentions Android (a CI check enforces it).

  28. while working on this, get all the prompts i've sent you here (no replies from you) and build prompts.spinwell.app list of all the prompts i've sent you with summary of what happened after my prompts, and update them while we're still working in this dialogue

    This page, which Claude keeps updating as the conversation goes on.

  29. both play store and app store are logged in

    Claude created Spinwell for Navidrome in App Store Connect and Google Play Console. It gave the release pipeline's service account rights on the Play app, filled in most of Play's policy declarations, and uploaded version 1.0.0 to Play as a draft. Through the App Store Connect API it set the category, age rating, copyright, free price and all 175 territories. Meanwhile the parallel builders finished: 21 app languages, 24 store listings, a public demo server with original music for reviewers, and screenshots for every phone and tablet size in every language, all merged. The last steps wait on Nikita typing the review account's password into both consoles. in progress

  30. open me the pages, i'll type the password in

    Claude opened the Play Console sign-in dialog, scrolled to the empty password field, and opened App Store Connect on the version's App Review section.

  31. both saved

    The App Store side had saved, but Play's had not: the dialog was added without the page's own Save, and the next page Claude opened dropped it. Claude filled the dialog in again for a second try.

  32. saved now

    Claude finished Google Play: target audience 18+, data safety (no data collected), the Music & Audio category, contact details, the icon and all 178 countries.

    While recording the review video Play asks for, it found a real bug: the Android player never registered its media session with the service. That meant no media notification, no lock screen controls, and playback that Android could kill in the background. Claude fixed it as build 2, swapped it into the Play draft, recorded the video and hosted it on spinwell.app.

    Then it sent Spinwell to Google Play review, published "Data Not Collected" on the App Store, and released v1.0.0. The pipeline put the APK on GitHub, but both store steps stopped: Play already had build 2, and Apple wanted support and privacy URLs in every language. Claude added the URLs and submitted the iPhone build with the pipeline's own script.

  33. make sure to save all the required secrets to vaultwarden (e.g. signing for android apps) and make sure our ci for publishing releases to playstore/appstore is functional

    Claude checked every release secret against Vaultwarden by hash: the Android upload keystore opens with its stored password and matches the release certificate. It added a Vaultwarden note mapping each CI secret to its item, and deleted the last plaintext copy of the keystore on disk.

    Apple had also quietly blocked the first submission over new China-mainland compliance forms, so Claude took China out of the App Store availability, and the iPhone app went to Waiting for Review. A full pipeline dry run in CI with a throwaway build 3 then went green: Play accepted the release, and the iPhone build archived and exported. By then Google had already approved the app, so Spinwell went live on Google Play and the site got its Play button. App Store in review

  34. wireless debugging is on, test it on the oneplus

    Claude installed build 2 over the test build, keeping the sign-in, and started a shuffle of the real library at low volume. Playback ran in the foreground with its media notification, the lock screen showed the song with shuffle, pause and repeat, and it kept playing with the screen off.

    Then it switched Tailscale off on the phone: about 15 seconds later the stream failed with "no network", and with nothing downloaded in that queue, playback stopped. Once Tailscale was back on, one press of play resumed the song where it left off. The on-screen offline banner went unchecked, because the phone sat on its PIN lock screen.