Local Audio Overlay Across Apps
An Android overlay adds a local audio track to videos or music, with separate volume and loop controls that pause and resume alongside the primary player.
Anyone who wants to play local white noise, a practice track, or a cue track while watching video usually has to give up their usual player first. Switching apps, competing for audio focus, and playback stopping after the screen locks turn a small need into repeated trial and error.
The user chooses a local audio file in an Android overlay, then opens Spotify, YouTube, or a video app as usual. The overlay keeps separate volume controls, a loop range, and headphone presets, so the two sounds can be balanced to suit the user. When the primary media pauses, the overlay pauses too; when playback resumes, it picks up from the same position.
The first time it is paired with a media app, the product plays a brief test tone to determine whether that app mixes audio, ducks background sound, or takes over playback entirely. The result is shown beside the current pairing, so users know before starting a long video whether it will work reliably rather than discovering halfway through that the local track has disappeared.
On the lock screen, the notification keeps pause and volume controls for both tracks. The first release supports only local files and players that follow Android audio rules. It does not record or download streaming content, or bypass any app’s copyright protection.
Why now
An August 15 post in r/Subliminal asked whether a downloaded track could be layered over YouTube, Spotify, or a movie. S1 The comments suggested Spotify local files and Evermusic, but a reliable mixer that does not replace the primary player is still missing; as of August 17, the post recorded 1 point and 3 comments. S1
Target user
The core user already has a local track ready: someone using subliminal audio, shadowing materials, a metronome, or ambient sound. The need becomes acute just before a long video, podcast, or music session, when reimporting the chosen content or switching players would interrupt what they have already picked. They are not looking to edit audio; they need to confirm before starting that the pairing will mix, then preserve the same volume balance after the screen locks.
Minimal entry point
Use Media3 ExoPlayer to play the user’s chosen local file without aggressively taking audio focus. Android allows multiple apps to output sound at once, but the primary player may still pause or duck when audio focus changes. S2 During pairing, play a short test tone and record the observed outcome as concurrent playback, ducking, or interruption. After the user grants notification access, use MediaSessionManager to read the selected primary app’s playback state; this requires media-control permission or an enabled notification listener service. S3 Run the local track in a MediaSessionService for lock-screen continuity and notification controls. The first version follows only apps that reliably expose media sessions. Other apps retain independent playback and are clearly labeled as unable to auto-sync pause and resume.
Punching above its weight
The first users are already in audio-practice communities such as r/Subliminal. S1 A compatibility directory organized by phone model and media app is more likely to attract search traffic than generic feature descriptions. Each listing can include a short screen recording showing whether the local track pauses when YouTube or Spotify pauses. Preset templates for white noise, language shadowing, and instrument practice can also bring in adjacent use cases through specific workflows.
Competitors & gaps
- EvermusicGoogle
- Evermusic already imports local and cloud audio. Its iOS Mixed Mode can play alongside other apps. S4 It also saves playback position and offers full player controls. S4 This shows that sustained playback of a second audio track is already well established. The first gap is platform coverage: Mixed Mode is available only on iOS. S4 Android users still need another option. Second, Evermusic remains centered on being a standalone music player. Users must open the app, choose a track, then switch to their primary media themselves. It does not create pairing profiles for media apps or flag in advance whether a pairing mixes, ducks, or takes over audio. Nor is it a confirmed capability that the second track pauses in place when the primary player pauses. For people who repeatedly use practice tracks, manual calibration also has to be repeated. The competitive opportunity is Android compatibility testing, synchronized start and stop, and pairing presets—not rebuilding a file player.
How it makes money
Core playback is free. A one-time purchase unlocks loop ranges, headphone presets, and app-pairing records. Future cloud features such as cross-device sync can be paid, but local playback will not become a subscription.
The case against
Third-party players handle audio focus inconsistently. A pairing that passes one test may still break after an ad, phone call, or Bluetooth switch. Following the primary media state also requires notification access, which may raise privacy concerns. Overlay permission adds another point of installation drop-off and may be deliberately hidden by sensitive apps. If pause detection is even slightly delayed, the local cue can continue after the primary content stops, then resume out of sync. Frequent misreads would push users back to manual controls and directly weaken the product’s value. Device-specific battery policies, headphone switching, and lock-screen behavior also need coverage, so testing costs rise quickly with each device combination. The condition for continuing is to establish a reliable whitelist across a small set of widely used players and devices first.