Why this matters
Audio changes the social and physical context of a product. Learning the device layer makes it possible to design interruption, background behavior, permissions, and feedback with the precision a listening product deserves.
Concepts to learn
- AVFoundation and audio sessions
- Background audio and playback interruptions
- Microphone permissions and speech recognition
- Text-to-speech, haptics, and camera access
- Device sensors and Bluetooth fundamentals
Apply It in Casset
Casset is the working environment for this skill—not the curriculum itself.
- Prototype voice notes or artist commentary attached to tracks with a transparent microphone-permission flow.
- Explore track-reactive haptics and waveform navigation as restrained listening feedback.
- Test lock-screen playback and interruption recovery without splitting ownership from Casset's canonical playback system.
- Document the foreground, background, route-change, and interruption states of one native listening mode.
Suggested project
Native listening mode
A focused audio experiment that survives lock screen, interruption, route change, and recovery.
Open project notebookEvidence of completion
These are completion conditions, not claimed achievements. Each stays planned until it links to a real artifact or verification.
- implementationA real-device audio session with predictable interruption behaviorplanned
- testsState and permission tests around playback and captureplanned
- TestFlightA device build with lock-screen and background verificationplanned
- diagramAudio ownership and interruption-state diagramplanned
Open questions
- Which feedback should be heard, felt, seen, or omitted?
- How can a product explain an audio interruption without making the user manage the system?
Related notes
Books, talks, and useful things
- toolAVFoundationApple
- talkDesigning Audio ExperiencesWWDC
Reflection journal
Audio is not a background utility. It is a sequence of permissions, interruptions, expectations, and recovery.