streamyfin

A modern Jellyfin client built with Expo

Runssource: GitHubhomepageTypeScriptMPL-2.0commit cb00ae36955b

TypeScript, MPL-2.0 licensed. The project labels itself: android, ios, jellyfin, jellyfin client and streaming client.

streamyfin runs. An Argusic agent installed it in 15 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Streamyfin installation succeeded: dependencies installed, all 365 unit tests pass, TypeScript type check passes, all 20 Expo SDK compatibility checks pass, and the Metro bundler serves valid JavaScript bundles for both iOS and Android platforms, ready for native device deployment.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
5,206
forks
272
open issues
314
watchers
16
size
74 MB
created
last push

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.

Time lost to each failure while testing streamyfin, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18.19.1 too old for expo-doctor (requires >=20.19.4)3 minutes
  • bun binary not available in container2 minutes
  • 34 Expo SDK packages at minor/patch versions below SDK 57 expected range1 minute
  • Duplicate native modules (expo-asset, expo-constants, expo-font, @expo/log-box) after upgrade1 minute
  • React Native DevTools SUID sandbox crash on startup1 minute
Install time
15 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
bun test: 365 passed, 0 failed, 604 expect calls; bun run typecheck: TypeScript check passed; expo doctor: 20/20 checks passed; Metro bundler served HTTP 200 on / and index.bundle for both iOS and Android platforms
Model tokens used
63,906
Exact commit tested
cb00ae36955b
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

exec
/bin/sh -lc 'curl -s --max-time 90 "http://localhost:8081/index.bundle?platform=android" | head -c …
 succeeded in 81ms:
var __BUNDLE_START_TIME__=globalThis.nativePerformanceNow?nativePerformanceNow():Date.now(),__DEV__=
All verification steps completed. Let me build the final result:
exec
/bin/sh -lc 'pkill -f "expo start" 2>/dev/null; pkill -f metro 2>/dev/null; echo "cleaned up"' in /…
 exited 143 in 0ms:
Here's the complete report:
tokens used
63,906
Here's the complete report:

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 5 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 MPL-2.0, 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 7 comparable projects Argusic has measured.

Of the 8 android projects Argusic has installed and timed, streamyfin was the 8th fastest to reach a running state, and 7 of 8 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.07
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

androidiosjellyfinjellyfin-clientstreaming-client

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/streamyfin.svg)](https://argusic.com/subject/streamyfin)

Questions

Does streamyfin run?
Yes. streamyfin runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test streamyfin?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cb00ae36955b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test streamyfin?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does streamyfin 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 streamyfin need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing streamyfin?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does streamyfin compare with the alternatives?
Of the 8 android projects Argusic has installed and timed, streamyfin was the 8th fastest to reach a running state, and 7 of 8 reached one at all.
Where is the evidence for streamyfin?
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.

Discussion