Manet Music Player is for music you already have: a Jellyfin server, a folder of files or the device's Music Library. Its official description covers playback on iPhone, iPad and Mac, with optional Sonos and AirPlay routes. It is not described as a subscription catalogue of songs. This first look is based on the store listing rather than a hands-on test of formats, networking or speaker compatibility.
The practical audience is someone whose library already exists but is awkward to reach from the desired listening place. The important choice is the source and playback route. A phone playing a local file over AirPlay is a different setup from a Sonos speaker fetching music directly from a Jellyfin server.
Based on official store information. We have not tested this app hands-on.
What it does
The Jellyfin route uses the server's address and the user's credentials. Alternatively, choose a folder of music or songs synced or purchased in the device Music Library. A demo library is described for trying the app before setting up a source. That provides a starting point, but a demo cannot establish compatibility with your own files or remote server.
Playback can stay on the device, go over AirPlay or use Sonos on the home network. The listing describes grouped Sonos speakers and a volume control for each. For Jellyfin playback on Sonos, the speaker fetches the music from the server, which means the phone is not acting as the ongoing audio source. The description also mentions a lock-screen Live Activity showing the song and speaker.
Queue controls include playing next, adding an album, reordering and removing items, with shuffle remaining enabled until changed. Jellyfin playlists live on the server. Folder and Music Library playlists can sync through the user's iCloud Drive, while songs absent on another device appear dimmed. Jellyfin downloads provide an offline listening route. These source-specific distinctions matter more than treating every playlist as the same kind of object.
Before you install
Start with one source and one playback destination. Confirm the selected account can reach the library and that a familiar album appears correctly. Then test a queue change and return to the same item later. We have not tested metadata interpretation, file-format support, gapless playback or how the app handles unavailable files, so investigate the properties important to your library.
Direct speaker playback also depends on networking beyond the app. A speaker must be able to reach the server from its own position on the network, not merely through the phone. Do not assume that a server address which works remotely on one device is reachable in the same way by every speaker. Use the official setup information for the services and hardware involved.
Offline playback is another separate state. Downloaded music can support listening without a connection, but the description does not establish that every source or playlist automatically becomes available offline. Check what is actually stored before a trip. A synchronised playlist can describe songs that a device does not possess; the dimmed items are a useful reminder that a list and the audio files are different things.
For a shared speaker, inspect the destination before pressing play. A grouped system may affect more than the room you are in, and independent volume controls need deliberate attention. That is a practical listening concern rather than evidence of an app defect.
Keep library maintenance on the appropriate side of the setup. A server playlist belongs to the server, while local files and iCloud-synchronised lists have different availability rules. Understanding where an item lives makes it easier to explain why it appears on one device but is unavailable on another.
Price and access
The retained App Store listing offers a free download. Confirm current access terms and device requirements on the official page. You still need one of the stated music sources, and Sonos hardware is optional rather than included. Server operation, storage, music purchases and any external service arrangements are separate from downloading the player.
The developer says Manet requires no account with its own service, has no ads or analytics and communicates with the user's server, speakers and Apple services. Those are stated privacy properties, not an independent audit. Using Jellyfin still involves the credentials and security arrangements of your own server.
Our take
Manet's strongest case is a clear set of routes from an existing library to a chosen listening device. The distinction between direct server-to-speaker playback and phone-based AirPlay is particularly useful because it explains what must remain available during a session. Queue tools and source-aware playlists can make that library easier to use without implying a new music catalogue.
We have not tested audio quality, connection reliability, battery use or privacy claims. Our take is to try a known album through the route you actually intend to use, then inspect queue behaviour and an offline example if relevant. Choose it when the relationship between source, playlist and playback destination is clear. A successful demo is encouraging, but the library you own is the meaningful compatibility test.
Sources
App icon from the official store listing.
