Android Client for Jellyfin
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 43%
jellyfin/jellyfin-android has a recorded first-timer success rate of 42.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jellyfin/jellyfin-android respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 62.4 places jellyfin/jellyfin-android in the A tier.
The external contributor pull request merge rate for jellyfin/jellyfin-android is 73.2%, based on public PR activity from non-core contributors.
jellyfin/jellyfin-android currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in jellyfin/jellyfin-android. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/jellyfin/jellyfin-android?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (91% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
This issue respects the following points: This issue is not already reported on GitHub (I've searched it). I agree to follow Jellyfin's Code of Conduct. This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. Describe the bug Tap on your profile picture Go to Client Settings Change "Video player type" to "External player" Change "External player app" to "VLC Player" Go back and confirm that online video plays on external player Tap on your profile picture Go to Downloads Tap on any downloaded video It plays on ExoPlayer I expect Downloads to follow the "External player app" setting, opening VLC, due to being unable to play them on ExoPlayer(hardware/codec limitations, I guess). Logs 09-19 10:06:03.148 25647 3993 W jellyfin.mobile: AIBinder_linkToDeath is being called with a non-null cookie and no onUnlink callback set. This might not be intended. AIBinder_DeathRecipient_setOnUnlinked should be called first. 09-19
This issue respects the following points: This issue is not already reported on GitHub (I've searched it). I agree to follow Jellyfin's Code of Conduct. This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. Describe the bug Play something Swipe in/out to zoom/change content fit mode Observe the video going forward/back Screen_Recording_20260814_155402_Jellyfin.2.mp4 Logs Application version 2.7.1 Where did you install the app from? Google Play Store Device information Samsung S24 FE Android version OneUI 8.5/Android 16 Jellyfin server version 10.11.11 Other sources No response
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to jellyfin/jellyfin-android, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of jellyfin/jellyfin-android acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.2% were successfully merged into the primary branch.
jellyfin/jellyfin-android has a recorded first-timer success rate of 42.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 62.4 places jellyfin/jellyfin-android in the Welcoming tier.
The external pull request merge rate is 73.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jellyfin/jellyfin-android currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jellyfin/jellyfin-android are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.