I tried Apple’s Siri Recaps. They’re surprisingly useful — and a little unsettling
- ID
- 43002
- Status
- summarized
- Published
- 05 Nov 2026, 12:51 AM
- Fetched
- 05 Nov 2026, 1:04 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/04/i-tried-apples-siri-recaps-theyre-surprisingly-useful-and-a-little-unsettling/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 5.5
- Created
- 05 Nov 2026, 1:04 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Apple shipped four Audio Intelligence features into the first developer betas of iOS 27.3 and watchOS 27.3 for Apple Watch Series 12: important-sound detection, Shazam-based song ID, Live Rewind (replay the last 15 seconds of what was said), and Siri Recaps, which summarizes audio across your day and saves notes. Apple processes audio on-device where possible, does not label speakers, does not store raw audio, and redacts things like government ID numbers and account details. After one day of testing, the reviewer found Recaps genuinely useful but flagged that it also captures things not worth remembering.
Why it matters
Apple just set the default user expectation for any voice-capture or meeting-recap feature you build: on-device processing, no raw audio retained, no speaker identification, and redaction of IDs and account numbers. If your product stores raw recordings or labels speakers, expect users to ask why. The reviewer's concrete complaint — that Recaps surfaces low-value moments — says the hard engineering problem is deciding what to keep, not transcribing it, so budget your effort on relevance filtering and deletion UX rather than ASR quality.
Discussion angle
If you were shipping a recap/note-taking feature tomorrow, what would your 'don't store raw audio, redact IDs, no speaker labels' implementation actually look like — and where does consent have to be explicit under Malaysia's PDPA-style expectations?