Invitations and discovery
Connect with another Deckamp user, see friend suggestions from eligible provider accounts, and handle incoming invitations.
Deckamp's connected-listening workflows are designed to respect each user's music-server permissions. Some require paired devices or direct provider connections and are under active beta testing.
Connect with another Deckamp user, see friend suggestions from eligible provider accounts, and handle incoming invitations.
Direct server/library connections are separate from social friendships. Access must be independently granted, and Deckamp should not expose server tokens to other users.
No usernames, invite codes, tokens or pairing credentials from private accounts are published in these examples.
Where supported, share playlist metadata and help recipients match tracks against their own authorized libraries. It is not an unrestricted music-file distribution mechanism.
Playlist Lab and transfer workflows aim to create new playlists on supported destinations while keeping the original unchanged, subject to API policies.
Discover compatible Deckamp receiver endpoints on the local network, pair them, and hand over playback state. The destination can resolve an eligible queue directly from a source it is allowed to access.
Choose an authorized receiver and transfer the playing queue and controls.
Expose a paired Deckamp-capable device for local discovery or manual setup. Availability depends on compatible software and connectivity.
Not a claim that arbitrary speakers can run Deckamp. Receiver discovery and long-session stability remain under testing.
Apple's system transports output from the current device to compatible speakers, receivers or TVs. It may involve platform audio processing.
A paired compatible receiver takes over an authorized playback queue instead of merely receiving the sender device's audio.