Collection before consumption
Streaming interfaces trained music software to behave like a storefront that never closes. The screen always wants to replace what you chose with what it can offer next. That logic is useful for discovery, but it is a poor foundation for living with a collection.
An owned library carries memory: the album you copied years ago, a sequence you repaired by hand, a playlist whose order matters, an artist name you corrected because the file should remain intelligible without a service account.
Continuity is part of the interface
Gapless playback, prepared handoff, crossfade, queue state, and output routing are not buried engine concerns. They determine whether the player feels deliberate. The interface begins before the next screen appears; it begins in the gap, or absence of one, between two pieces of music.
AntiiQ treats the signal path as visible product behavior. The aim is not technical theatre. It is to let the listener understand what is carrying the sound and retain authority over it.
Assistance without surrender
A local player can still suggest, group, schedule, and extend. The difference is hierarchy. Companion behavior should work from the listener's library and intent rather than turning the collection into raw material for an endless engagement loop.