Repository navigation
Mobile app
Khryz-Navarro edited this page Nov 9, 2026
·
1 revision
Install ArgonStream on your phone like an app, and share a link to it straight from YouTube or any other app ("Share → ArgonStream"), instead of copying and pasting.
A PWA (a website you install) runs in the phone's browser and can't run yt-dlp or ffmpeg. Something else has to do the downloading. The options, from simplest to most work:
-
The desktop app does the downloads, the phone just sends links:
- ArgonStream on your computer serves a small page on your home network.
- The PWA sends it links, and the files are saved on the computer, or sent back to the phone.
- It needs pairing (for example a QR code shown in the desktop app) and an access token, so only your phone can use it.
- This is real security work: a local server that accepts links is a new way into the app.
-
A native Android app:
- Tauri 2 can build for Android.
- Running yt-dlp there needs a Python runtime or a phone-ready build of it. Projects like Seal and YTDLnis do this.
- This is the biggest effort, but it works without a computer.
- A hosted server: a website that downloads for you. Not planned: it costs money to run and makes the project a download service, with the legal exposure that comes with it.
Sharing to the app:
- A PWA can receive shared links through the Web Share Target API.
- Chrome on Android supports it. iOS Safari doesn't, so on iPhone it would be copy and paste, or a Shortcut.
- Which of the three, if any? Option 1 fits the app best and keeps downloads on your own computer.
- Should downloaded files be sent back to the phone, or stay on the computer?
- Should it live in this repo or its own?
- Security: a network-facing server in the desktop app needs to be designed with care: pairing, local network only, tokens, and no file paths from the phone.
- Store rules: app stores restrict YouTube downloaders, which is why such Android apps are distributed outside Google Play.
- The platform: iOS limits what PWAs can do.
Phase 1: links you paste
Phase 2: tools for your files
Phase 3: new engines
Phase 4: beyond the desktop