openspot-music-app
OpenSpot is a free, open-source music app that lets you stream and download high-quality tracks across all your devices. With a sleek, intuitive UI built for a seamless experience, it supports Android, iOS, macOS, Windows, and Linux, so you can enjoy your favorite music anywhere, online or offline.
Runssource: GitHubhomepageTypeScriptMITcommit 640af8290f7d
TypeScript, MIT licensed. The project labels itself: android, android studio, api, eas, electron app, electronjs, expo and flac.
openspot-music-app runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Both openspot-mobile and openspot-desktop apps install dependencies via npm and export static web builds with 14 working routes including index, search, library, settings, downloads, and media pages.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing expo-asset dependency caused web export to fail3 minutes
- Missing query-string dependency required by expo-router2 minutes
- Missing shaka-player dependency required by react-native-track-player2 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npx expo export --platform web completed successfully for both openspot-mobile and openspot-desktop, producing valid HTML static sites at dist/web/ with working route files (14 routes each) and bundled JS assets (~4MB total per app)
- Model tokens used
- 346,383
- Exact commit tested
- 640af8290f7d
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
346,383 Good, repository is clean. Now let me write the final report. Here's my complete report: **Repository**: OpenSpot Music - a monorepo with two music streaming apps: - `openspot-mobile/` (React Native + Expo, for Android/iOS) - `openspot-desktop/` (Tauri + React, for macOS/Windows/Linux) **Install process**: Both apps use `npm` as the package manager. Initial `npm install` on both succ… **Errors encountered and fixed**: 1. `expo-asset` missing — the mobile web export needed `expo-asset` which wasn't in dependencies. I… 2. `query-string` missing — `expo-router` needed it. Installed via `npm install query-string`. 3. `shaka-player` not installed — `react-native-track-player` lists it as a peer dependency. Instal… **Verification**: Both apps successfully completed `npx expo export --platform web` producing stati…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 15 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.
Of the 14 android projects Argusic has installed and timed, openspot-music-app was the 12th fastest to reach a running state, and 11 of 14 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.08 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.02 |
Topics (from GitHub)
androidandroid-studioapieaselectron-appelectronjsexpoflacfree-musicioslinuxmacosmp3music-playernextjsopensourcereact-nativesongsstreamwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openspot-music-app)Questions
- Does openspot-music-app run?
- Yes. openspot-music-app runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test openspot-music-app?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 640af8290f7d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openspot-music-app?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openspot-music-app take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does openspot-music-app need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openspot-music-app?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does openspot-music-app compare with the alternatives?
- Of the 14 android projects Argusic has installed and timed, openspot-music-app was the 12th fastest to reach a running state, and 11 of 14 reached one at all.
- Where is the evidence for openspot-music-app?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.