Redomi routes music links to the streaming app you actually use

The cross-platform link that will not play

Platform boundaries are most annoying in chat threads. A friend sends a track link from a service you do not use, and the result is either a page asking you to sign up somewhere new or a link that opens a browser tab instead of your player. Redomi exists for that exact moment. It is an unofficial client for Song.link, written in Kotlin with Jetpack Compose and Material You, and its job is narrow on purpose: receive a music link from a platform you did not choose, then route it to the streaming app you did choose. The reverse direction matters as much. When you want to send someone a song, Redomi converts the link into a form their platform understands, so the recipient lands in their own player rather than in an app they avoid. The project describes itself as an unofficial Song.link client rather than a music player, and that framing explains most of what follows, including the fact that the interesting engineering sits in Android link handling and the share sheet rather than in any audio decoding.

Song.link does the resolving, Redomi does the handing over

The README credits Song.link as the reason the project exists at all, and a separate Android client as the source of inspiration. So the architecture has two halves. Song.link is the resolver: a link of the form people already share points at a service that knows where the same track lives on other platforms. Redomi is the Android half, the piece that receives an incoming link, lets you pick a destination, and hands the resolved destination to the app on your phone. Playback never happens inside Redomi. Once the track reaches Spotify, Tidal, or any other client, that client owns the stream, the account, and the audio quality. The practical consequence is that Redomi inherits the limits of both halves. If a track has no counterpart on the destination platform, Song.link has nothing to offer, and Redomi has no catalogue of its own to fall back on. The project also states that third party clients work as long as they are the default app to handle the corresponding link, which puts the routing decision partly in the hands of the system rather than inside the app.

Android 12 setup: telling the system Redomi may handle your links

Redomi does not receive music links by default, and the project is explicit about that. The setup walkthrough targets Android 12 and later, where the relevant control lives under the app info page. The steps are short enough to follow from the README directly, and they exist because Android only offers a link to an app that has declared an interest in that link type. The important detail is the third step: the platforms you do not have installed must still be checked, since those are exactly the links that need converting. The README notes that the label may differ from device to device, so look for the equivalent of the default app screen rather than hunting for the exact wording. After this, opening a supported link from another app should route through Redomi, which then lets you choose the destination rather than sending you straight to the platform that produced it.

Customizing the sharesheet instead of accepting the default

The share sheet is where Redomi spends its effort beyond link routing, and the project lists four axes of control: icon shapes, which apps to display, whether the list runs horizontally or vertically, and the grid size of that list. That combination matters more than it first appears, because a share sheet that shows twelve icons in a cramped vertical strip is slower to use than one that shows four in a row of tiles. The app can also filter which apps appear, which is the setting to reach for when you want Spotify and Tidal in the sheet but no interest in anything else. Material You is a separate feature from all of this, and so are the light and dark theme options, which follow the system palette rather than offering independent color choices. The README does not document per-app destination defaults, so the choice of target is made at share time rather than pinned in advance.

Eleven named services plus whatever handles the link

The supported list covers YouTube Music, YouTube, Spotify, Deezer, Tidal, Amazon Music, Apple Music, SoundCloud, Napster, Yandex Music, and Anghami. That list is long enough that the common case of a friend on a different platform is usually covered, and it is the practical check to run before installing. The open-ended part is the third party rule: any client works as long as it is set as the default handler for the corresponding link, so an app outside the named list can still serve as a destination. That is a broader statement than the eleven names and worth taking literally, because it means the real limit on destinations is the set of apps registered on your phone, not the set of lines in the README. A platform that is not installed cannot be a destination, which is why the setup step asks you to enable the platforms you are missing. The share direction follows the same path, with your selection converted into a link the recipient's platform can resolve.

What the documentation leaves out

Several things a reader might expect to find are absent from the README. There is no documented install command, no build instructions for running the Gradle project locally, and no description of the release signing or distribution process beyond the fact that builds are published through GitHub releases and listed in F-Droid and IzzyOnDroid repositories. There is also no statement about offline behaviour, no account system, no lyrics or playlist handling, and no description of what happens when a link resolves to no match on the chosen platform. The Android requirement is split across two places: the badge advertises support for Android 8 and above, while the default handler walkthrough is written for Android 12 and later, which leaves the range between those versions unaddressed. Translations are handled through Crowdin rather than shipped by hand. Licence is GPL-3.0, so anyone who wants to fork the app or ship a modified build inherits copyleft obligations on redistribution, and anyone embedding the code in a larger product should read the licence text before doing so.

Release rhythm and where the upstream alternative fits

The published releases run 1.4.1 on 2026-03-09, 1.4.2 on 2026-07-04, and 1.4.3 on 2026-09-01, and the last push to the repository was on 2026-09-08. The gaps between those versions range from weeks to months, which is enough to suggest ongoing work without saying anything about a fixed schedule. Three versions landing in 2026 also suggests that some of the recent effort has gone into fixing or refining behaviour rather than adding new services. The closest alternative is the web service itself: Song.link resolves links in a browser without an Android install, but it hands you a page of destinations rather than a native share sheet with configurable icons and grid layout, and it does nothing for outgoing links from your own player. The other alternative is the project the author names as inspiration, an Android client that took a similar approach. Redomi's difference is the share-side customization, not the routing.

Editorial conclusion

Redomi fits Android users whose music life spans more than one streaming service and who keep arriving at a link for a service they did not subscribe to. It is a poor fit for anyone who wants a player of its own, for desktop or browser use, or for a workflow where link conversion has to be scripted, since the project offers no documented command line and no stated batch mode. Before installing, check two things: that the services you use are on the supported list, and that on your Android version you can grant Redomi the default handler role for the services you do not have installed, because the setup walkthrough is written for Android 12 and later. Install the release build from the GitHub releases page or an F-Droid repository, then confirm a single link resolves before you rely on it for daily sharing.

Frequently asked questions

Official sources

1. acszo/Redomi on GitHub
2. Issues
3. License: GPL-3.0
4. README
5. Releases