Hey everyone! I'm the developer behind OfflineTunes, and I'm looking for a few people who would be interested in testing a new feature I've been working on for a while.
Ever since I started building OfflineTunes, I've had this idea of turning the phone itself into a music server. I built a custom RPC architecture over 4 years ago when i started working on this app with the intention of eventually allowing me to host my entire music library directly from my phone and access it from other devices.
The idea is that I can use my phone as my main source of audio files, and whenever I want to listen to my music on my PC, I can just connect to it through a browser. Eventually, I'd also like to aggregate all the different services and cloud storage providers where I have music stored so I can access everything in one place.
There are two different server modes:
- Full Player Mode: This basically turns your phone into a full music server. You start the server, connect to it from your desktop browser, and the entire music player runs in the browser. You can browse your library, manage playlists, play music, edit tags, and use the different player features directly from your desktop.
- Playback Mode: This is a little different. Instead of using the browser as the actual music player, you use your phone to control playback. Whatever you play on your phone gets streamed to the browser, where it displays the album artwork, cover view, and your upcoming tracks. You can also trigger the visualizer directly from your phone and have it displayed in the browser. This is useful if you want to keep your phone as the main player but still have a visual display on your desktop.
Both modes support the visualizer. In Full Player Mode, you can trigger it directly from the desktop using your mouse, while in Playback Mode, you can trigger it from your phone.
How does it work?
The most basic use case is pretty straightforward. You start the music server on your phone, open the desktop client in your browser, and you have access to the music stored locally on your device.
But it goes beyond just streaming local files.
If you have music stored on cloud services like Dropbox, OneDrive, S3, WebDAV drives like Nextcloud, and other connected services, you can also access and stream those tracks directly through the browser. The phone basically acts as a proxy, streaming directly from those services rather than requiring you to download everything onto your phone first.
Note: For obvious DRM reasons, you can't stream music from your iPod/iTunes-synced tracks or Apple Music subscription. Those can only be listened to through the app itself.
This also works with Plex, Jellyfin, and Navidrome, although using the phone as a gateway for those services doesn't make quite as much sense since they're already hosted servers. It could still be useful if you want to quickly transfer tracks from those servers to your PC or want to host your local only self-hosted server so that it can be streamed remotely.
What can you do from the desktop?
It's not just a basic music player. The desktop client currently supports quite a few features:
- Stream music directly from your phone or connected cloud storage/self-hosted servers.
- Access live playlists from your devices.
- Access Smart Playlists.
- Download tracks directly to your computer.
- Upload tracks from your computer.
- View lyrics.
- Edit music tags and metadata.
- Convert audio files.
- Play Track Radio using Sonic Analysis data, similar to how it works in the app.
- Display the music visualizer.
- Use FineTune Mode to review and organize your music library.
FineTune Mode is actually one of the big reasons I wanted to build this feature.
I wanted to be able to finetune my music library while working on my desktop, without having to constantly switch back to my phone. FineTune Mode allows you to go through your music, filter out tracks you don't want, approve or reject songs, and organize everything into playlists or remove unwanted tracks from your library.
Having this available on the desktop means I can listen to music while working and clean up my library at the same time. It's something I personally wanted to use, and having it available through the server makes that workflow much more convenient.
Some of these features still need optimization, and the desktop experience currently uses the iPad view as its starting point. I'm gradually changing things to make it feel more like a proper desktop application rather than just an iPad interface running in a browser.
Note: EQ, gapless playback, bit-perfect audio, crossfade, Automix, and ReplayGain do not work in server mode and are unlikely to be supported in the future.
How do you connect?
There are currently two ways to connect your desktop to the phone.
- Local IP: This is a completely on-device connection. You start the server on your phone and connect to its local IP address from your desktop. No external server or internet connection is required for the connection itself.
- Remote connection: You can visit https://offlinetunes.app/player and scan a QR code from your phone to connect through the internet. This means you don't have to be on the same Wi-Fi network to access your music.
I wouldn't recommend relying on the remote connection if you're on the same network, though, since it has additional costs and is slower than connecting directly through the local IP.
There is also an interesting part to the remote connection. Once connected through the website, you can grant permission to use the browser's Local Network API. This allows the desktop client to discover and use the phone's local IP address for streaming, which is much more performant.
The website also remembers your connected device. So the next time you start the server, you can simply select your phone from the device list and load the application.
The desktop client is a PWA, so you can install it as a desktop app and launch it directly. When everything works as expected, the entire process of opening the app, starting the server, and connecting to your desktop takes less than 20 seconds.
Why did I build this?
Personally, I want to use my phone as my main music source without having to maintain my own Plex, Navidrome, or Jellyfin server.
I've moved most of my music storage to Nextcloud, and I wanted a way to get the benefits of having a dedicated music server without actually having to host one.
One of the things I really wanted was to keep all my music activity in one place. Play counts, scrobbling, ratings, metadata editing, and everything else should work regardless of whether I'm listening from my phone or desktop.
For example, if I edit cover art or change a tag from the desktop client, the app can write those changes back to the original file in Nextcloud. This way, I'm not maintaining separate copies of my music or losing track of my listening history just because I'm using a different device.
Ultimately, I want to be able to pick up my phone, start the server, connect from my PC, and have access to my entire music library without needing another computer running in the background.
A few things about pricing and availability
Currently, this feature is available on iOS only, since that's where OfflineTunes is currently available. I'm slowly working on an Android port that will include the same features, but that takes time. Once that's ready, the music server should work on Android as well.
If you're using the free version of the app, you can watch an ad to unlock a 45-minute session on the Player Server.
If you're interested in testing it for longer or want to experience the feature without session limitations, just reach out to me. I'm happy to help extend your free testing access so you don't have to pay just to test this feature in its fullest.
One thing worth mentioning is that audio conversion and tag editing are not available on the server for free users. Unlike the mobile app, where these features are available through ads, implementing ads in a desktop browser environment opens up a whole other level of complexity that I don't want to get into while this feature is still experimental.
What needs work?
This is still very experimental, and there are quite a few things that need improvement.
- The desktop interface needs more work to feel like a proper desktop experience.
- I haven't fully tested it with my larger music library yet, especially since I recently got a new phone.
- There are currently some bugs with remote connection handshaking and reconnection. I'm working on fixing these in the next update.
- For now, you'll need to scan the QR code every time you want to establish a new remote connection.
I'm sharing this because I'd really appreciate having some people test it out and give me feedback. I'm particularly interested in hearing how it performs with different music libraries, cloud storage providers, and network configurations.
I'm not just looking for people to try the player, but also people who might have ideas about how this kind of setup could be improved.
If you're interested in testing it, let me know! I'd really appreciate any feedback, suggestions, or guidance that could help me improve this.
Thanks!
P.S. All the thoughts, ideas, and words in this post are my own. ChatGPT helped me organize and rewrite them, as well as fix spelling and grammar mistakes since English isn't my primary language. I wanted to make that clear!
DM me if you are interested!