Swiftfin leads for iOS Picture-in-Picture in self-hosted media clients
This review evaluates the Picture-in-Picture (PIP) performance of seven self-hosted media client applications on iOS, drawing on a user's direct comparison. We assess PIP quality, stability, and…
This review evaluates the Picture-in-Picture (PIP) performance of seven self-hosted media client applications on iOS, drawing on a user's direct comparison. We assess PIP quality, stability, and specific limitations for each.
TL;DR
Best for: iOS users prioritizing stable, good-quality Picture-in-Picture (PIP) for self-hosted Jellyfin content. Skip if: You require instantaneous playback or prefer the in-app player for PIP over the native iOS player. Bottom line: Swiftfin, when configured to use the native iOS player, offers the most reliable and highest-quality Picture-in-Picture experience among the tested self-hosted media clients, despite occasional longer load times.
METHODOLOGY
This v0 review draws on the user's published claims at https://www.reddit.com/r/selfhosted/comments/1tlkvxd/selfhosted_ioslike_media_apps/; independent benchmarks pending. Update cadence: re-tested when claims diverge from observed behavior.
This review covers the reported Picture-in-Picture (PIP) behavior of seven self-hosted media client applications on iOS, specifically: Jellyfin iOS app, Jellyfix, Infuse, Senplayer, Moonfin, Swiftfin, and Streamyfin. The observations were made by Reddit user /u/secnd_frog_fan and published on 2026-05-23. The scope includes reported PIP quality, stability (e.g., progress retention), and specific playback limitations (e.g., skipping forward/backward). What is not covered in this review includes independent performance benchmarks, long-term workflow integration, specific media format compatibility beyond general playback, or edge cases not explicitly mentioned by the user. The user's initial complaint regarding Immich's timeline view is also outside the scope of this review, which focuses on media playback clients.
WHAT IT DOES
Evaluates iOS Picture-in-Picture
The Reddit user conducted a direct comparison of seven self-hosted media client applications, focusing exclusively on their Picture-in-Picture (PIP) functionality on iOS. The primary goal was to identify a client that offers a stable, high-quality PIP experience without losing playback progress when returning to the app.
Identifies player-specific behaviors
Several apps exhibited different PIP behaviors depending on whether they used their internal player or the native iOS player. For instance, the Jellyfin iOS app's internal player provided proper PIP but with low quality, while its native player offered good quality PIP that broke upon returning to the app. Swiftfin showed a similar distinction, with its own player lacking PIP, but the native player providing good PIP.
Highlights functional limitations
Beyond quality, the review details functional limitations. Moonfin, for example, treated PIP content as a live stream, preventing users from skipping forward or backward. Other apps, like Jellyfix and Infuse, were reported to lack PIP functionality entirely at the time of testing.
Pinpoints best-in-class for PIP
After testing, Swiftfin, when utilizing the native iOS player, was identified as the most effective solution for the user's requirements. It delivered good quality PIP and maintained stability, though it came with a caveat of “somewhat long load times.” Streamyfin was also noted for good PIP with its app's player, but Swiftfin was preferred for overall ease of use.
WHAT'S INTERESTING / WHAT'S NOT
What's interesting here is the stark inconsistency in Picture-in-Picture (PIP) implementation across self-hosted media clients on iOS. This isn't just about minor differences; it's a fundamental divergence in whether PIP is supported, its quality, and its stability. The distinction between an app's internal player and the native iOS player is a critical, often overlooked detail that significantly impacts user experience, as highlighted by the Jellyfin and Swiftfin findings. Many clients struggle with basic functionality, such as retaining playback progress or allowing seeking within a PIP window, which are table stakes for a modern media player. The user's systematic approach to testing these specific behaviors provides valuable, concrete data points that are often missing from general product descriptions.
What's not interesting, or rather, what's concerning, is the general state of iOS PIP support in this category. For a feature as standard as PIP on a platform like iOS, the reported issues—low quality, broken progress retention, lack of seeking, or complete absence of the feature—suggest a lack of prioritization or technical challenges in integrating with iOS's media frameworks. The fact that a user had to manually test seven different applications to find a barely satisfactory solution underscores a significant gap in the market. The
Pull quote: “Swiftfin, when configured to use the native iOS player, offers the most reliable and highest-quality Picture-in-Picture experience among the tested self-hosted media clients, despite occasional longer load times.”
Every claim ties to a primary source. See our methodology.